Lesson 4
Lesson 4
Use Case - Ideal for IoT applications with - Best for enterprise applications
constrained resources, such as requiring reliable message queuing and
sensor networks and smart homes. advanced routing, such as financial
transactions.
Key Insights: AMQP vs MQTT
1. Power Usage:
○ MQTT is lightweight and efficient, ideal for IoT devices.
○ AMQP is resource-intensive and better suited for enterprise environments.
2. Security:
○ MQTT provides sufficient security for IoT use cases but lacks advanced
authentication mechanisms.
○ AMQP offers enterprise-grade security with options like SASL.
3. Message Persistence:
○ MQTT’s retained messages and QoS ensure reliability for disconnected clients.
○ AMQP provides more advanced message durability and acknowledgment
features.
Use Case - Designed for IoT applications - Best suited for web applications,
requiring real-time communication APIs, and general internet browsing.
and efficient bandwidth usage.
1. Power Usage:
○ MQTT is more efficient for IoT use cases due to its lightweight persistent
connections.
○ HTTP/HTTPS consumes more power because of its stateless design, making it
less suitable for low-power devices.
2. Security:
○ Both protocols support SSL/TLS, but HTTPS is more universally trusted for web
communication.
○ MQTT is sufficient for IoT but lacks the widespread adoption and familiarity of
HTTPS.
3. Message Persistence:
○ MQTT excels with features like retained messages and QoS for reliable offline
message delivery.
○ HTTP/HTTPS requires external systems for message storage and reliability.
Work Cited
https://www.spiceworks.com/tech/networking/articles/amqp-vs-mqtt/
https://www.hivemq.com/blog/mqtt-vs-http-protocols-in-iot-iiot/