Apache ActiveMQ 5.14.5 includes several resolved issues and bug fixes.
In this blog post of 2014, Jerry Kuch describes a performance study of RabbitMQ on Google Compute Engine. It demonstrated the ability to receive and deliver more than one million messages per second (a sustained combined ingress/egress of over two million messages per second).
At this high rate of combined ingress (1,345,531 messages per second) and egress (1,413,840 messages per second), RabbitMQ was keeping up with load and that only 2,343 messages are temporarily accumulated in its queues awaiting delivery.
“Newer architectures and the standardized AMQP protocol have led to a flood of message brokers. All brokers take claim to be fast, robust and reliable. But what really distinguish the broker? How do I choose the right broker? Should we continue to use established brokers such as the ActiveMQ or try a more modern one? This article attempts to answer these questions and help the reader in selecting a suitable broker.”
Andy Piper / vFabric Team published an article in 2013 about three popular protocols for message broker client/server communication: Choosing Your Messaging Protocol: AMQP, MQTT, or STOMP. The STOMP specification (currently at 1.2) can be found here. For Delphi and Free Pascal developers, Habarisoft offers STOMP client libraries designed for and tested with popular open source message brokers.
ActiveMQ Apollo is a faster, more reliable, easier to maintain messaging broker built from the foundations of the original ActiveMQ. It accomplishes this using a radically different threading and message dispatching architecture. Like ActiveMQ, Apollo is a multi-protocol broker and supports STOMP, AMQP, MQTT, Openwire, SSL, and WebSockets.
Client libraries are available for many programming languages. Habarisoft offers client libraries for Delphi and Free Pascal.