=============== 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: .. code-block:: none amqp_broker = guest/guest@localhost The :class:`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 `_.