Moksha supports configurable message flows, allowing you to utilize various message brokers, depending on your environment.
Since Moksha employs a high-level “Topic” concept, applications can easily communicate with them without having to worry about the underlying message protocol.
By default, Moksha will utilize the STOMP message broker, MorbidQ, which is built-in to Orbited. You can change the stomp_broker in the Moksha configuration file to point to a different STOMP broker – RabbitMQ with the STOMP-adapter has been tested as well.
Plugging an AMQP broker into Moksha is trivial. Simply add an amqp_broker to your configuration, and change the live socket backend:
amqp_broker = guest/guest@localhost
moksha.livesocket.backend = amqp
Note
It’s probably best to comment out the stomp_broker when you enable AMQP support. You can have both, but Moksha will enter a bridged mode that may or may not work as expected.
The MokshaHub will then automatically connect up to your AMQP broker and proxy messages to the STOMP broker and Moksha Consumers.
AMQP support in Moksha has been tested with Qpid.
RabbitMQ support is under development. See the Using RabbitMQ with Moksha documentation for details on testing it.