Common IoT Protocols (MQTT, CoAP)

Addressing the Constraints Covered in the Previous Note

Given IoT devices' severe power, processing, and scale constraints, standard protocols like plain HTTP (covered earlier in this project) are often too heavyweight - MQTT and CoAP were both specifically designed to be far lighter and more efficient.

MQTT: Publish-Subscribe Messaging

Sensor  ---- publishes to topic "home/livingroom/temperature" ---->  [ MQTT Broker ]
                                                                            |
                                                                            v
                                            Any subscribed device automatically receives the update

MQTT uses a publish-subscribe pattern: devices publish updates to named "topics," and any other device that has subscribed to that topic automatically receives them - devices never need to know about each other directly, only about the shared central broker relaying messages between them.

Why This Pattern Suits IoT So Well

A single sensor can publish its readings once, and any number of interested devices (a dashboard, a logging system, an alert system) can subscribe and receive that same update - without the sensor itself needing to know anything about who's actually listening, keeping the sensor's own logic and resource usage extremely minimal.

CoAP: A Lightweight Alternative to HTTP

CoAP (Constrained Application Protocol) mirrors HTTP's familiar request/response style (GET, POST, and similar concepts), but is deliberately designed to be far lighter weight, and runs over UDP (covered earlier in this project) rather than TCP - trading some of TCP's reliability guarantees for significantly lower overhead, better suited to constrained devices.

Comparing the Two