← Back to Homepage

Understanding MQTT Protocol

MQTT is a lightweight messaging protocol designed for M2M (machine-to-machine) communication and IoT applications. It's highly bandwidth-efficient, easy to integrate, and built on top of TCP for reliable communication over unreliable channels. As a binary protocol, it's meant for machines and allows messages as small as 2 bytes, making it ideal for constrained devices.

It supports bi-directional, data-agnostic, push-style communication — where messages are pushed from publishers to subscribers via a broker, without the clients needing to poll for updates. TLS can be enabled for security, and it scales well due to its publish/subscribe (pub/sub) model.

Publish/Subscribe Model

In the pub/sub model, clients publish data to a central broker under specific topics. Other clients subscribe to these topics to receive updates. This architecture offers:

• Space decoupling - no geographical limitations
• Time decoupling - works across timezones
• Synchronization decoupling - asynchronous communication

The broker acts as the message hub. It manages all subscriptions and message routing, making scalability a strong point. However, this also means the broker is a single point of failure (SPOF). Clients typically use MQTT libraries or SDKs to communicate with a broker service.

Packet Types

• CONNECT - Sent by the client with its metadata. Includes a clean session flag:
  • Clean: broker doesn't retain session state after disconnect
  • Persistent: broker saves session info for reconnecting clients
• CONNACK - Broker’s response to a CONNECT packet, indicates if the client is allowed to connect.
• PUBLISH - Contains packet ID, topic name, QoS level, retain flag, and the message payload.
  • Retain flag: if set, the broker stores the message and delivers it immediately to new subscribers of the topic.
• SUBSCRIBE - Client requests subscription to topics with desired QoS levels.
• SUBACK - Acknowledges the subscription request.
• UNSUBSCRIBE - Used when a client no longer wants messages from certain topics.

Topics

Topics are UTF-8 strings used by the broker to route messages. They can have multiple hierarchical levels, separated by slashes (e.g., sensor/temp). Wildcards are supported:

• # - Matches all sub-topics (e.g., sensors/# matches all topics under sensors)
• + - Matches exactly one level (e.g., sensors/+/temp matches sensors/room1/temp)

QoS Levels

MQTT offers three levels of Quality of Service to control delivery guarantees:

• QoS 0 - At most once delivery. Messages may be lost.
• QoS 1 - At least once delivery. Acknowledged with PUBACK.
• QoS 2 - Exactly once delivery. Requires a 4-step handshake:
  1. Client → PUBLISH
  2. Broker → PUBREC
  3. Client → PUBREL
  4. Broker → PUBCOMP