- No configuration needed
- Works out-of-the-box
- Not designed for scalability
- No wildcard topic names
- STOMP/AMQP broker bridging
- Not very well tested
- May or may not work as expected
- Trivial to configure
- 100% AMQP, from the browser to the broker
- Flexibility and power of AMQP queues, exchanges, routing keys, etc.
- Blazing fast. ~100 times faster hub processing
- Distributed. No central broker
- Only moksha-hub and the WSGI stack. No orbited, no broker.
- Uses native WebSockets, not supported on all browsers
- No built in persistance or delivery guarantee
See Message Brokers for more information on configuring various protocols and brokers with Moksha.