skip to main content

In a small office at Phillips 66, Andy and Arlen sat down to build something from scratch because existing enterprise systems were too "bloated" for the job. They followed a few "bare bones" principles that still define MQTT today: What is MQTT? - MQTT Protocol Explained - AWS

was incredibly expensive; every single byte literally cost thousands of dollars per year.

The story of (Message Queuing Telemetry Transport) began in 1999 with two engineers, Andy Stanford-Clark of IBM and Arlen Nipper of Arcom (now Eurotech), who were facing a massive technical headache in the middle of a desert . The Problem: Expensive Sand and Satellite Bytes

Phillips 66 needed to monitor in remote areas where the only way to send data was via satellite. At the time:

, and traditional communication methods (like "polling," where a server constantly asks "Do you have data yet?") were battery-draining and saturated the network just to stay connected. Latency was high , and connections were unreliable. The Invention: A Protocol Born in a Desert Office

Mqtt Essentials - A Lightweight Iot Protocol – Authentic & Top-Rated

In a small office at Phillips 66, Andy and Arlen sat down to build something from scratch because existing enterprise systems were too "bloated" for the job. They followed a few "bare bones" principles that still define MQTT today: What is MQTT? - MQTT Protocol Explained - AWS

was incredibly expensive; every single byte literally cost thousands of dollars per year. MQTT Essentials - A Lightweight IoT Protocol

The story of (Message Queuing Telemetry Transport) began in 1999 with two engineers, Andy Stanford-Clark of IBM and Arlen Nipper of Arcom (now Eurotech), who were facing a massive technical headache in the middle of a desert . The Problem: Expensive Sand and Satellite Bytes In a small office at Phillips 66, Andy

Phillips 66 needed to monitor in remote areas where the only way to send data was via satellite. At the time: The story of (Message Queuing Telemetry Transport) began

, and traditional communication methods (like "polling," where a server constantly asks "Do you have data yet?") were battery-draining and saturated the network just to stay connected. Latency was high , and connections were unreliable. The Invention: A Protocol Born in a Desert Office