Architecture:Protocols:MQTT

• Part of Architecture:Protocols:Main_Page

AI-Generated Content Notice: The following content (full page) was generated using ChatGPT on 2026-04-07.
[Included in accordance with the AOWIS AI Usage Guide (REQ-AI-007, REQ-AI-008) and MAY require verification and/or post-editing.]

MQTT (Message Queuing Telemetry Transport)

MQTT stands for Message Queuing Telemetry Transport. It is a lightweight messaging protocol designed for low-bandwidth, high-latency, or unreliable networks, and is often used in Internet of Things (IoT) applications. It allows devices to communicate efficiently.

How MQTT Works

MQTT uses a publish/subscribe model, unlike traditional request/response networking. There is a central broker (server) that routes messages between devices:

• Publishers: devices that send messages on a topic.
• Subscribers: devices that receive messages from topics they are interested in.
• Broker: manages message delivery, ensuring subscribers get messages they have subscribed to.

Key Features

• Lightweight: Minimal overhead, ideal for small sensors and embedded devices.
• Efficient: Designed for low network bandwidth.
• Reliable: Supports different levels of message delivery:
  • QoS 0: At most once (fire-and-forget)
  • QoS 1: At least once (may duplicate)
  • QoS 2: Exactly once (guaranteed delivery)

Typical Use Cases

• Smart home devices (lights, thermostats)
• Industrial sensors and machinery
• Vehicle telemetry
• Remote monitoring systems

Ports and Transport

• MQTT usually runs over TCP, default port 1883.
• MQTT over TLS/SSL uses port 8883 for secure communication.

Summary

In simple terms, MQTT is like a tiny, super-efficient postal service for devices, letting them send and receive messages without overwhelming the network.