ApacheCon NA 2015

ActiveMQ clustering with a network of brokers is susceptible to race conditions, significant overhead for consumer creation and removal, lack of consolidated reporting, messages becoming stuck and more. Configuring and standing up broker topologies requires a fair amount of effort, knowledge, and tooling.

A new effort is under way to address these concerns and more, in order to provide the ActiveMQ community with truly scalable, reliable, and maintainable cluster topologies. We'll review these concerns, discuss ideas for addressing them, and demonstrate some of the work in progress. The long-term vision is clustered ActiveMQ as a unified, complete, and reliable JMS solution for the enterprise. Having a topology of brokers operate no different than a single broker to individual client applications enables true horizontal scaling and enterprise management of messaging load.