ActiveMQ Review

It allows for asynchronous communication.


What is most valuable?

It’s a JMS broker, so the fact that it can allow for asynchronous communication is valuable.

What needs improvement?

The clustering for sure needs improvement. When we were using it, the only thing available was an active/passive relationship that had to be maintained via shared file storage. That model includes a single point of failure in that storage medium.

What do I think about the stability of the solution?

We didn’t encounter anything that wasn't a result of our own misguided uses.

What do I think about the scalability of the solution?

We did have scalability issues.

How is customer service and technical support?

It's open source.

Which solutions did we use previously?

We didn’t have a previous solution.

How was the initial setup?

The initial setup was straightforward. Whatever you don’t know, you can find via Google pretty easily.

What's my experience with pricing, setup cost, and licensing?

It’s open source, ergo free.

Which other solutions did I evaluate?

We didn’t seek alternatives. We were told to use this.

What other advice do I have?

Check out RabbitMQ. Run it in a Docker container out of Kubernetes with a persistent volume. You could probably do that with ActiveMQ, but it would require working with KahaDB, or establishing some other backend database pod.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment
Guest
Sign Up with Email