IoT glossary
operacion

What is MQTT

Quick definition

MQTT (Message Queuing Telemetry Transport) is a very lightweight publish/subscribe protocol designed for devices with little CPU, little RAM, and flaky links. It works against a central broker (Mosquitto, HiveMQ, EMQX, AWS IoT Core) and carries most modern industrial IoT traffic.

Why MQTT and not HTTP

Each HTTP request opens TCP, runs a TLS handshake, and ships hundreds of bytes of headers. On NB-IoT or metered IoT, that is expensive. MQTT holds a single TCP connection and messages are binary, not text.

QoS: three levels

QoS 0 (best effort, no ack), QoS 1 (at least once, ack with possible duplicate), QoS 2 (exactly once, double handshake). In industrial IoT, QoS 1 is the norm; QoS 2 only when duplicating a message is unacceptable (billing, critical commands).

FAQ

MQTT 3.1.1 or MQTT 5?+

MQTT 5 if your broker and SDK support it: clear error codes, message properties, better expiry. MQTT 3.1.1 remains the most universally compatible.

Do I need my own broker?+

Not always. AWS IoT Core, Azure IoT Hub, or HiveMQ Cloud handle it for you. For large fleets with private APN, a self-hosted broker on your DC gives more control.

Related terms