- Virtual topics supporting easy scalability of topic consumers
- Simple, yet flexible configuration of dead letter strategies
- The master-slave group with shared storage cluster topology
Loose coupling of components by the use of messaging queues allows for completely separate component life cycles and ownership within the organization.
It also greatly contributes to application maintenance and managing incidents, since no component is synchronously coupled to the other.
These are important considerations in a micro-service environment such as ours.
The included admin web app is not sufficient and we ended up disabling it. Instead, we are instead using hawtio and Jolokia.
However, the audit logging in Jolokia is not detailed enough and we were forced to write our own audit filter.
Even with hawtio, some JMX operations are awkward. A better admin tool would be nice.
I have been using ActiveMQ for approximately two years.
We have not encountered any stability issues.
The documentation is very good. Since this is a widely used product, there are plenty of good examples of how to solve various tasks. We have not used any other technical support.
The strategic architecture in the organization required a more lightweight, yet mature, capable, reliable, and scalable open source alternative.
We looked at Redis and RabbitMQ.