Message Queueing Telemetry Transport

Message Queueing Telemetry Transport
Name	Message Queueing Telemetry Transport
Os	Cross-platform
Genre	Messaging protocol

Contents

Message Queueing Telemetry Transport is a lightweight publish–subscribe network protocol designed for constrained devices and low-bandwidth, high-latency networks. It is widely adopted in industries that include Siemens, General Electric, ABB Group, Bosch, and Schneider Electric for telemetry, remote monitoring, and control. The protocol ecosystem encompasses standards, commercial products from Amazon Web Services, Microsoft Azure, Google Cloud, and open-source projects led by organizations such as the Eclipse Foundation, Apache Software Foundation, Linux Foundation, and companies including IBM.

Overview

The protocol provides a simple client–server architecture where clients communicate via a central broker; major brokers include Mosquitto, Eclipse EMQX, RabbitMQ, HiveMQ, and VerneMQ. Typical deployments integrate with cloud platforms like Amazon Web Services, Microsoft Azure, Google Cloud Platform, and Oracle Cloud and interoperate with platforms from Siemens, Honeywell, Rockwell Automation, and Schneider Electric. It is frequently used alongside protocols and standards such as OpenTelemetry, OPC UA, Modbus, BACnet, and LoRaWAN in sectors represented by companies like Siemens Energy, GE Healthcare, Bosch Rexroth, and Schneider Electric Industries. The protocol’s client libraries exist in languages maintained by foundations and vendors like Eclipse Foundation projects, Apache Software Foundation packages, and commercial offerings by IBM and Microsoft.

Developed in the late 1990s and early 2000s by engineers associated with companies such as Arcom (company), the protocol matured through collaboration with organizations including Eurotech, IBM, Sun Microsystems, and Intel. Standardization and formal specification efforts involved contributors from OASIS, IEEE, and consortiums tied to vendors like Siemens and Honeywell. Commercial adoption expanded through partnerships with cloud providers such as Amazon Web Services and Microsoft Azure, and research groups at universities including Massachusetts Institute of Technology, Stanford University, and Carnegie Mellon University examined its applicability for sensor networks and telemetry. Major events and conferences where the protocol was presented or discussed include CES, Embedded World, Interop, and IoT Solutions World Congress.

The protocol defines a lightweight binary message format, a small fixed header, control packets, and topic-based publish–subscribe semantics implemented in brokers such as Mosquitto and RabbitMQ. Versioning and extensions have been formalized in documents produced by organizations like OASIS and industry groups including Eclipse Foundation projects. Interoperability testing occurs at venues organized by Linux Foundation initiatives and consortia including Open Connectivity Foundation. Implementations often provide transport over Transmission Control Protocol, Transport Layer Security, and message framing compatible with cloud gateways from Amazon Web Services, Microsoft Azure, and Google Cloud Platform.

Design emphasizes small code footprint for devices from vendors such as Texas Instruments, STMicroelectronics, NXP Semiconductors, and Microchip Technology. Principles include publish–subscribe decoupling used by systems from IBM and Red Hat, topic hierarchies comparable to naming in IETF and routing concepts in Cisco Systems equipment, and support for quality-of-service levels adopted by platforms from Siemens, ABB Group, and GE Digital. The protocol complements standards and stacks like OpenFlow, NetConf, and RESTful API ecosystems promoted by companies such as Cisco Systems and Juniper Networks.

Deployments rely on transport security with standards such as Transport Layer Security and authentication mechanisms integrated with identity providers like Okta, Auth0, Microsoft Entra ID, and Google Identity Platform. Enterprise brokers integrate with access control systems from Ping Identity, CA Technologies, and Okta and compliance frameworks from ISO, NIST, and regulators represented by organizations such as European Commission digital policy units. Threat assessments reference advisories from vendors including Cisco Systems, Microsoft, and Amazon Web Services.

Open-source brokers include Eclipse Mosquitto, Eclipse EMQX, RabbitMQ, HiveMQ Community Edition, and VerneMQ; commercial offerings come from IBM, Amazon Web Services, Microsoft, Google, and HPE. Client libraries and SDKs are available in languages supported by organizations such as The Linux Foundation projects and vendor ecosystems including Microsoft (.NET), Oracle (Java), Google (Go), and communities around Python and Node.js. Integrations exist with platforms and tools produced by Splunk, Grafana Labs, Prometheus, Elastic (company), and Datadog for telemetry collection and analytics.

Common applications include industrial telemetry in installations by Siemens, ABB, Schneider Electric, and GE, building automation in projects by Johnson Controls and Honeywell, smart metering with utilities such as Enel and EDF, telematics and fleet management deployed by Daimler, Volvo, and Volkswagen Group, and consumer IoT products from Samsung Electronics and LG Electronics. It is also used in cloud-native architectures by Amazon Web Services, Microsoft Azure, and Google Cloud Platform for event ingestion, integration with serverless platforms like AWS Lambda and Azure Functions, and telemetry pipelines feeding analytics tools from Splunk and Datadog.

Scalability strategies employ clustering and load balancing products from Kubernetes, Red Hat OpenShift, HashiCorp, and NGINX with enterprise brokers supported by vendors including VMware and HPE. Performance tuning references hardware from Intel, AMD, NVIDIA, and specialized edge devices from Dell Technologies and HPE Aruba. Benchmarks and experiments have been reported in venues associated with IEEE and ACM conferences, with academic collaborations involving Carnegie Mellon University, Massachusetts Institute of Technology, and Stanford University exploring latency, throughput, and resource-constrained deployments.

Category:Internet protocols