STOMP, Simple (or Streaming) Text Oriented Message Protocol, is a simple text-based protocol used for transmitting data across applications. It is a much simpler and less complicated protocol than AMQP; it is more similar to HTTP. STOMP clients can communicate with almost every available STOMP message broker. This provides easy and widespread messaging interoperability among many languages, platforms and brokers. It is, for example, possible to connect to a STOMP broker using a telnet client.
RabbitMQ supports STOMP (all current versions) via the Stomp plugin. All CloudAMQP have the Stomp plugin running on port 61613 (TLS: 61614), if enabled. It can be enabled/disabled from the Plugin tab in the control panel.
STOMP does not deal with queues and topics — it uses a SEND semantic with a destination string. RabbitMQ maps the message to topics, queues, or exchanges (other brokers might map onto something else that it understands internally). Consumers then SUBSCRIBE to those destinations.
STOMP is recommended if you are implementing a simple message queuing application without complex demands on a combination of exchanges and queues.