Message Brokers

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.

STOMP

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.

AMQP

Plugging an AMQP broker into Moksha is trivial. Simply add an amqp_broker to your configuration:

amqp_broker = guest/guest@localhost

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.