MQTT

MQTT^[1] (formerly MQ Telemetry Transport) is an ISO standard (ISO/IEC PRF 20922)^[2] publish-subscribe based "light weight" messaging protocol for use on top of the TCP/IP protocol. It is designed for connections with remote locations where a "small code footprint" is required or the network bandwidth is limited. The publish-subscribe messaging pattern requires a message broker. The broker is responsible for distributing messages to interested clients based on the topic of a message. Andy Stanford-Clark and Arlen Nipper of Cirrus Link Solutions authored the first version of the protocol in 1999.

The specification does not specify the meaning of "small code foot print" or the meaning of "limited network bandwidth". Thus, the protocol's availability for use depends on the context. In 2013, IBM submitted MQTT v3.1 to the OASIS specification body with a charter that ensured only minor changes to the specification could be accepted.^[3] MQTT-SN ^[4] is a variation of the main protocol aimed at embedded devices on non-TCP/IP networks, such as ZigBee.

Historically, the 'MQ' in 'MQTT' came from IBM's MQ message queuing product line.^[5] However, queuing per se is not required to be supported as a standard feature in all situations.^[6]

Alternative protocols include the Advanced Message Queuing Protocol, the IETF Constrained Application Protocol^[7] and XMPP.^[8][9]

MQTT Broker

There are several MQTT brokers available such as ActiveMQ, Apollo, HiveMQ, IBM MessageSight, JoramMQ, Mosquitto, RabbitMQ, Solace Message Routers, and VerneMQ. They vary in their feature set and some of them implement additional features on top of the standard MQTT functionality. See MQTT.org for more information.^[10]

A comparative study of the performance of these different brokers (ActiveMQ, Apollo, JoramMQ, mosquitto and RabbitMQ) can be found here.

MQTT methods

MQTT defines methods (sometimes referred to as verbs) to indicate the desired action to be performed on the identified resource. What this resource represents, whether pre-existing data or data that is generated dynamically, depends on the implementation of the server. Often, the resource corresponds to a file or the output of an executable residing on the server.

Connect

Waits for a connection to be established with the server.

Disconnect

Waits for the MQTT client to finish any work it must do, and for the TCP/IP session to disconnect.

Subscribe

Waits for completion of the Subscribe or UnSubscribe method.

UnSubscribe

Requests the server unsubscribe the client from one or more topics.

Publish

Returns immediately to the application thread after passing the request to the MQTT client.

Real world applications

In the real world, there are a number of projects that implement MQTT.

• Facebook Messenger. Facebook has used aspects of MQTT in Facebook Messenger.^[11] However, it is unclear how much of MQTT is used or for what; Moreover, it is to be noted that this is a phone application, not a sensor application.
• IECC Scalable DeltaRail's latest version of their IECC Signaling Control System uses MQTT for communications within the various parts of the system and other components of the signaling system. It provides the underlying communications framework for a system that is compliant with the CENELEC standards for safety-critical communications.
• The EVRYTHNG IoT platform uses MQTT as an M2M protocol for millions of connected products.
• On October 8, 2015 Amazon Web Services announced Amazon IoT is based on MQTT.^[12]

References

External links

• MQTT homepage
• Is Exactly-Once Delivery Possible with MQTT