NoteVerse

MQTT methods and components

Comprehensive study notes, diagrams, and exam preparation for MQTT methods and components.

MQTT Methods and Components

Definition

MQTT is a publish-subscribe messaging protocol that enables devices, applications, and services to communicate through a broker using topics. It is designed for low-bandwidth, high-latency, or unreliable networks and supports efficient, asynchronous data transfer.

In simpler terms, MQTT works like a post office system: publishers send messages to specific topic addresses, the broker sorts and forwards them, and subscribers receive only the messages they are interested in.

Main Content

1. MQTT Architecture Components

Client

  • Any device or application that connects to the MQTT network. A client can act as a publisher, subscriber, or both. Examples include sensors, mobile apps, dashboards, and microcontrollers.

Broker

  • The central server that receives all published messages and distributes them to the correct subscribers based on topic subscriptions. Popular brokers include Mosquitto, HiveMQ, and EMQX.

The MQTT architecture is the foundation of the protocol. Unlike direct communication models, MQTT separates message senders from receivers. This separation improves scalability and makes the system more flexible because publishers do not need to know who the subscribers are, and subscribers do not need to know who published the message.

The broker also manages important tasks such as authentication, topic matching, message forwarding, retained messages, and session handling. For example, in a smart home system, a temperature sensor may publish readings to the topic home/livingroom/temperature, and multiple clients such as a dashboard and automation service can subscribe to that topic at the same time.

2. Publish-Subscribe Messaging Model

Publisher

  • A client that sends messages to a topic. The publisher does not send messages directly to a specific receiver; instead, it sends them to the broker under a named topic.

Subscriber

  • A client that listens for messages on one or more topics. When the broker receives a matching message, it forwards the data to the subscriber automatically.

The publish-subscribe model is one of MQTT’s most important methods because it decouples communication. This means publishers and subscribers are independent of each other in terms of time and identity. A publisher can send data even if subscribers are not currently online, and subscribers can join later and still receive important data if the broker supports retained messages or persistent sessions.

Topics are organized hierarchically using slash-separated paths such as factory/machine1/status or home/kitchen/light. Subscribers can choose broad or narrow topic filters. For instance, subscribing to home/# receives all messages under the home tree, while home/+/temperature matches temperature data from any single room under home.

This model is ideal for real-world IoT scenarios. For example, multiple monitoring systems can subscribe to the same sensor feed, while the sensor only publishes one message. This reduces network traffic and improves efficiency.

3. MQTT Message Features and Communication Methods

Topic-based routing

  • Messages are delivered according to topics, which act as logical channels for communication.

Quality of Service (QoS)

  • MQTT supports different delivery guarantees so clients can choose how reliable message transmission should be.

MQTT messages contain several important parts: topic, payload, QoS level, retained flag, and packet identifier in some cases. The payload carries the actual data, such as a JSON object, a plain text value, or binary data. For example, a temperature reading may look like { "device_id": "sensor01", "temp": 27.4 }.

MQTT supports three QoS levels:

QoS 0

  • At most once delivery. The message is sent once without acknowledgment. It is fastest but least reliable.

QoS 1

  • At least once delivery. The receiver acknowledges the message, but duplicates may occur.

QoS 2

  • Exactly once delivery. This is the most reliable but has the highest overhead.

Other communication methods include:

Retained messages

  • The broker stores the last message on a topic and sends it immediately to new subscribers.

Persistent sessions

  • Useful when clients disconnect temporarily and need queued messages later.

Keep-alive mechanism

  • The client periodically checks in with the broker to maintain the connection and detect disconnections.

These features make MQTT suitable for both simple telemetry and mission-critical applications. For example, in an industrial factory, a shutdown alert may use QoS 2 to ensure exact delivery, while routine sensor updates may use QoS 0 to save bandwidth.

Working / Process

1. Client connects to the broker

A device or application establishes a connection with the MQTT broker using a network connection, often over TCP/IP. During this step, the client may authenticate using a username, password, certificate, or token.

2. Subscriptions are created and messages are published

Subscribers register interest in specific topics, and publishers send messages to those topics. The broker receives the messages and checks which clients have subscribed to matching topic filters.

3. Broker forwards messages to matching subscribers

The broker delivers the message according to the chosen QoS level, session state, and retained-message rules. If a subscriber is offline and persistent sessions are enabled, the broker may store messages temporarily and deliver them once the client reconnects.

Advantages / Applications

Low bandwidth usage and lightweight design

  • MQTT uses small packet sizes and minimal protocol overhead, making it efficient for constrained devices and poor networks.

Scalable and flexible communication

  • One publisher can serve many subscribers, which simplifies large distributed systems and supports many-to-many communication.

Widely used in IoT and real-time systems

  • MQTT is suitable for smart homes, industrial automation, healthcare monitoring, vehicle telemetry, environmental sensing, and remote control applications.

Summary

  • MQTT is a lightweight publish-subscribe protocol used for efficient device communication.
  • It works through clients, topics, and a broker that routes messages.
  • Its methods include publishing, subscribing, QoS delivery, retained messages, and persistent sessions.
  • MQTT is important because it is fast, scalable, and well suited for IoT and other real-time applications.
  • Important terms to remember: client, broker, publisher, subscriber, topic, payload, QoS, retained message, persistent session, keep-alive
← Prev: MQTT
Next: SMQTT →