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."I am impressed with the tool’s latency. Also, the messages in ActiveMQ wait in a queue. The messages will start to move when the system reopens after getting stuck."
"Most people or many people recommended using ActiveMQ on small and medium-scale applications."
"I'm impressed, I think that Active MQ is great."
"The ability to store the failed events for some time is valuable."
"The initial setup is straightforward and only takes a few minutes."
"It’s a JMS broker, so the fact that it can allow for asynchronous communication is valuable."
"Message broadcasting: There could be a use case sending the same message to all consumers. So as a producer, I broadcast the message to a topic. Then, whichever consumers are subscribed to the topic can consume the same message."
"There is a vibrant community, and it is one of the strongest points of this product. We always get answers to our problems. So, my experience with the community support has been good."
"When we went to add another installation in our private cloud, it was easy. We received support from Solace and the install was seamless with no issues."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"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."
"Going from something where we had outages and capacity issues constantly to a system that was able to scale with the massive market data and messaging spikes that happened during the initial stages of the COVID crisis in March, we were able to scale with 40 plus percent growth in our platform over the course of days."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"The solution's stability needs improvement."
"This solution could improve by providing better documentation."
"I would rate the stability a five out of ten because sometimes it gets stuck, and we have to restart it. We"
"Distributed message processing would be a nice addition."
"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."
"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."
"Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle."
"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."
"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?"
"The section on observability pertains to understanding the functioning of an event crash. Instead of focusing on how the crash occurs, attention is given to the observable aspects, such as a memory pipeline where one person pushes messages and another reads them. However, this pipeline often encounters issues, such as the reader being unavailable, causing the system to become stuck and preventing the messages from moving forward. This can lead to the pipeline being permanently stalled."
"Some of the feature's gaps with some of the open-source vendors have been closed in a lot of ways. Being more agile and addressing those earlier could be an area for improvement."
"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."
"The licensing and the cost are the major pitfalls."
"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."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"The ease of management could be approved. The GUI is very good, but to configure and manage these devices programmatically in the software version is not easy. For example, if I would like to spin up a new software broker, then I could in theory use the API, but it would require a considerable amount of development effort to do so. There should be a tool, or something that Solace supports, that we could use for this, e.g., a platform like Terraform where we could use infrastructure as code to configure our source appliances."
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.
