If you are building cloud-based IoT solutions, you know the importance of machine-to-machine (M2M) connectivity protocols and have probably heard of MQTT. As IoT application development is on the rise, so is the use of MQTT.
MQTT has been around since the late 90s, but it has certainly caught fire in the last decade. You might say it is the de-facto messaging protocol for IoT solutions. There are several reasons for this. It’s open, simple, reliable, and popular.
What makes MQTT so special is that it is a messaging protocol that is ideal for small sensors and mobile devices in high-latency or unreliable networks. That is, it is ideal for IoT solutions.
Although MQTT is not the only protocol in town, it appears to be the most popular…especially now it is officially an ISO standard. Ultimately, standards, like international ISO standards, help ensure the quality and reliability of products and services.
In August 2010, IBM published the MQTT V3.1 protocol specification, which was used in developing future standards. Eclipse, and specifically the Eclipse Paho project, was the first to move MQTT on its standardization path. In October of 2014, MQTT became an OASIS standard, and in January 2016, ISO officially approved it as an ISO standard (ISO/IEC 20922), which the OASIS consortium recently announced.
The MQTT protocol is used and supported by virtually all leading IoT platforms and services available today, including IBM’s Watson IoT Platform. It is also used directly in popular consumer applications, most notably the Facebook Messenger app.
More on MQTT
- IBM Watson IoT Platform MQTT documentation
- developerWorks tutorial: Explore MQTT and the Internet of Things service on IBM Bluemix: Use a sample Java app or the Node-RED editor to learn how it works
- developerWorks article: High availability with IBM MessageSight and MQTT client applications