Overview of the architectures of MQTT vs CoAP, plus ways to make MQTT act like CoAP and vice versa. Also contains fun graphics to liven the mood

1. VS

2. REST Architecture
Resource
GET
PUT
POST
DELETE
Client

3. REST Architecture
• A resource has a scalar value
• Last known value is important

4. Publish/Subscribe Architecture
• Decouple consumption from production
• Event stream
• Big data analytics

5. Pub/Sub On CoAP
• GET+Observe
• Loses data in high throughput scenarios
• Not decoupled

6. REST On MQTT
• Client
– Publisher, subscribes to response topic
• Server
– Subscriber

7. REST On MQTT
• Request
– $CTL/<domain>/<app>/<clientId>/POST/resource
• Response
– $CTL/<domain>/<app>/<clientId>/resource/<requ
estId>

8. 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

9. Thanks!