Multi-protocol – CloudAMQP

CloudAMQP offers hosting for two brokers, LavinMQ and RabbitMQ, which both
allow clients to connect with multiple protocols. On both shared and dedicated plans,
RabbitMQ supports
AMQP 0-9-1 and AMQP 1.0,
HTTP,
MQTT,
STOMP,
and
WebSockets.
LavinMQ supports
AMQP 0-9-1,
HTTP,
MQTT,
and WebSockets, but does not implement AMQP 1.0 or STOMP.

When creating a CloudAMQP instance, all the common protocols are available by default
(the Web-STOMP plugin can only be enabled on dedicated
plans.) Most message queuing
protocols share many features in common. However, some are better suited to a particular set
of use cases than others. In the simplest case, a message queue uses an asynchronous protocol
in which the sender and the receiver do not operate on the message simultaneously.

The protocol only defines the communication between the client and the server and doesn’t
impact the message itself. One protocol can be used when publishing, and another protocol
for consuming. With its minimal design, MQTT makes it perfect for built-in systems, mobile
phones, and other memory and bandwidth-sensitive applications. A specific task may as well
be achieved using AMQP, but MQTT might be a more appropriate choice of protocol in this
particular type of scenario.