MQTT: The Tiny Protocol Powering Millions of IoT Devices

In 1999, two engineers needed to monitor oil pipelines stretching across remote desert terrain. Thousands of sensors. Hundreds of kilometres. Satellite links that were slow, expensive, and unreliable.

Every unnecessary byte of data cost real money. Every dropped connection could mean a missed reading on a pipeline carrying millions of dollars worth of oil.

HTTP wasn't going to cut it. So they built something new. Something with a minimum message size of two bytes. Something that assumed the network would fail.

They called it MQTT. Twenty-five years later, it runs your smart home, your hospital monitors, your fleet tracking, and your factory floor. Not bad for a protocol built to watch oil flow through a desert pipe. 🔧

The Short Version

MQTT is a publish/subscribe messaging protocol — and its architecture is its superpower.

Instead of devices talking directly to each other, everything flows through a central broker:

• A publisher (your temperature sensor, your door lock) sends a message tagged with a topic
• The broker receives it and instantly routes it to anyone who subscribed to that topic
• A subscriber (your dashboard, your alert system) gets the message without ever knowing who sent it

Sender and receiver never meet. Add new devices without touching anything else. That decoupling is why MQTT scales to millions of devices while HTTP falls apart. 🔌

What makes it the IoT standard:

• Tiny footprint — minimum 2-byte header; up to 80% less bandwidth than HTTP for the same data
• Built for bad networks — persistent sessions, stored messages, automatic reconnection; designed to assume the connection will drop
• Three QoS levels — fire-and-forget for high-frequency sensor readings, at-least-once for important events, exactly-once for billing and actuation
• Last Will — register a message the broker sends automatically if your device goes silent; your monitoring system knows it went offline without the device being able to tell anyone
• Retained messages — a new subscriber gets the last known state immediately, without waiting for the next reading

---

Where It's Running Right Now

Almost everywhere connected devices send data — whether you know it or not:

• Smart home — Amazon, Google, and Apple's ecosystems all use or support MQTT under the hood
• Industrial IoT — machine health monitoring, SCADA, predictive maintenance; MQTT remains the dominant protocol for IIoT systems in 2026
• Healthcare — biometric data streaming from wearables to monitoring systems
• Fleet & automotive — GPS trackers and vehicle telemetry over cellular; Nipper's original use case alongside the oil pipelines
• Cloud platforms — AWS IoT Core, Azure IoT Hub, and Google Cloud Pub/Sub all support MQTT natively

And here's how simple it is to implement — a working publisher in five lines of Python:

import paho.mqtt.client as mqtt

client = mqtt.Client()
client.connect("broker.hivemq.com", 1883)
client.publish("home/livingroom/temperature", "23.5")
client.disconnect()

That's a real IoT messaging system. The broker is free for testing. Change the topic, change the payload — you're building.

---

💡 Final Thought

MQTT is one of those foundational technologies that's invisible precisely because it works so well. You don't notice it. Your thermostat just responds. Your factory alert just fires. Your fleet tracker just updates.

If you're building anything with IoT — start here. Everything else builds on top of it.

→ Full breakdown: QoS levels, Last Will, broker options, MQTT 5 upgrades, limitations, and a complete code walkthrough: Read the deep dive

---

Follow for more IoT connectivity deep dives — part of my ongoing 101-story series. 🔬