VS

REST Architecture

Resource

GET

PUT

POST

DELETE

Client

REST Architecture

• A resource has a scalar value• Last known value is important

Publish/Subscribe Architecture

• Decouple consumption from production• Event stream• Big data analytics

Pub/Sub On CoAP

• GET+Observe• Loses data in high throughput scenarios• Not decoupled

REST On MQTT

• Client– Publisher, subscribes to response topic

• Server– Subscriber

REST On MQTT

• Request– $CTL/<domain>/<app>/<clientId>/POST/resource

• Response– $CTL/<domain>/<app>/<clientId>/resource/

<requestId>

REST On MQTT

• Not simple– Future non-local subscribe could ease the pain

• Not composable or extensible• Requires extra protocol above MQTT• Response is not guaranteed• Mutable state

Thanks!