We performed a comparison between ActiveMQ and PubSub+ Event Broker based on real PeerSpot user reviews.
Find out in this report how the two Message Queue (MQ) Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Most people or many people recommended using ActiveMQ on small and medium-scale applications."
"For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery."
"It’s a JMS broker, so the fact that it can allow for asynchronous communication is valuable."
"The initial setup is straightforward and only takes a few minutes."
"The most important feature is that it's best for JVM-related languages and JMS integration."
"ActiveMQ is very lightweight and quick."
"Reliable message delivery and mirroring."
"ActiveMQ brings the most value to small applications because it will not cost you very much to complete."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"The most valuable feature of PubSub+ Event Broker is the scaling integration. Prior to using the solution, it was done manually with a file, and it can be done instantly live."
"This solution reduces the latency to access changes in real-time and the effort required to onboard a new subscriber. It also reduces the maintenance of each of those interfaces because now the publisher and subscribers are decoupled. Event Broker handles all the communication and engagement. We can just push one update, then we don't have to know who is consuming it and what's happening to that publication downstream. It's all done by the broker, which is a huge benefit of using Event Broker."
"We've built a lot of products into it and it's been quite easy to feed market data onto the systems and put entitlements and controls around that. That was a big win for us when we were consolidating our platforms down. Trying to have one event bus, one messaging bus, for the whole globe, and consolidate everything over time, has been key for us. We've been able to do that through one API, even if it's across the different languages."
"In my assessment of Solace against other products — as I was responsible for evaluating various products and bringing the right tool into companies in the past — I worked with multiple platforms like RabbitMQ, Confluent, Kafka, and various other tools in the market. But I found the event mesh capability to be a very interesting as well as fulfilling capability, towards what we want to achieve from a digital-integration-strategy point of view... It's distributed, yet it is intelligently connected. It can also span and I can plug and play any number of brokers into the event mesh, so it's a great deal. That's a differentiator."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"The topic hierarchy is pretty flexible. Once you have the subject defined just about anybody who knows Java can come onboard. The APIs are all there."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"It would be great if it is included as part of the solution, as Kafka is doing. Even though the use case of Kafka is different, If something like data extraction is possible, or if we can experiment with partition tolerance and other such things, that will be great."
"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."
"Needs to focus on a certain facet and be good at it, instead of handling support for most of the available message brokers."
"The UI. It's both a good thing and a bad thing. The UI is too simple. Sometimes you wanna see the messages coming to the queue, and you have to refresh the dashboard, the console of the product."
"This solution could improve by providing better documentation."
"From the TPS point of view, it's like 100,000 transactions that need to be admitted from different devices and also from the different minor small systems. Those are best fit for Kafka. We have used it on the customer side, and we thought of giving a try to ActiveMQ, but we have to do a lot of performance tests and approval is required before we can use it for this scale."
"The solution can improve the other protocols to equal the AMQ protocol they offer."
"The solution's stability needs improvement."
"For improvements, I would suggest increasing the max payload size to a limit of 100MB or more. The current max payload size is limited to 5MB."
"One of the areas of improvement would be if we could tell the story a bit better about what an event mesh does or why an event mesh is foundational to a large enterprise that has a wide diversity of applications that are homegrown and a small number off the shelf."
"The deployment process is complex."
"The licensing and the cost are the major pitfalls."
"We've pointed out some things with the DMR piece, the event mesh, in edge cases where we could see a problem. Something like 99 percent of users wouldn't ever see this problem, but it has to do with if you get multiple bad clients sending data over a WAN, for example. That could then impact other clients."
"If you create one event in the past, you cannot resend it."
"We have requested to be able to get into the payload to do dynamic topic hierarchy building. A current workaround is using the message's header, where the business data can be put into this header and be used for a dynamic topic lookup. I want to see this in action when there are a couple of hundred cases live. E.g., how does it perform? From an administration perspective, is the ease of use there?"
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
ActiveMQ is ranked 3rd in Message Queue (MQ) Software with 24 reviews while PubSub+ Event Broker is ranked 6th in Message Queue (MQ) Software with 15 reviews. ActiveMQ is rated 7.8, while PubSub+ Event Broker is rated 8.6. The top reviewer of ActiveMQ writes "Allows for asynchronous communication, enabling services to operate independently but issues with stability". On the other hand, the top reviewer of PubSub+ Event Broker writes "Event life cycle management changes the way a designer or architect will design a topic and discover what is available". ActiveMQ is most compared with IBM MQ, Anypoint MQ, Red Hat AMQ, VMware RabbitMQ and EMQX, whereas PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, VMware RabbitMQ, Confluent and Amazon EventBridge. See our ActiveMQ vs. PubSub+ Event Broker report.
See our list of best Message Queue (MQ) Software vendors.
We monitor all Message Queue (MQ) Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.