Try our new research platform with insights from 80,000+ expert users

ActiveMQ vs PubSub+ Platform comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 27, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

ActiveMQ
Ranking in Message Queue (MQ) Software
2nd
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
28
Ranking in other categories
No ranking in other categories
PubSub+ Platform
Ranking in Message Queue (MQ) Software
8th
Average Rating
8.6
Reviews Sentiment
7.1
Number of Reviews
18
Ranking in other categories
Message Oriented Middleware (MOM) (2nd), Event Monitoring (12th), Streaming Analytics (15th)
 

Mindshare comparison

As of February 2026, in the Message Queue (MQ) Software category, the mindshare of ActiveMQ is 22.4%, down from 25.7% compared to the previous year. The mindshare of PubSub+ Platform is 4.2%, down from 5.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software Market Share Distribution
ProductMarket Share (%)
ActiveMQ22.4%
PubSub+ Platform4.2%
Other73.4%
Message Queue (MQ) Software
 

Featured Reviews

MD
Software Engineer III at a financial services firm with 10,001+ employees
Integration capabilities enhance message handling without human interaction
With ActiveMQ there should be more options. If you work with other technologies, for example, Java, there are many options. We can integrate the way we want ActiveMQ. We can create partitions and clusters, but AP is not providing such options currently. It only provides time, request response timing, the number of requests that need to be handled, and protocol types. The configuration needs to be broadened inside AP to perform in a better way. Sometimes issues arise in production with ActiveMQ due to the number of requests. For example, if you have configured one thousand requests at a time and it receives one thousand and one messages at a time, it breaks. The configuration aspect is tricky. When configurations are proper, ActiveMQ almost has zero errors.
reviewer2714190 - PeerSpot reviewer
freelancer at a financial services firm with 1,001-5,000 employees
Offers a seamless way to decouple applications, providing impressive performance and flexibility
Regarding improving the PubSub+ Platform, I'm not sure about the pricing aspect, but I heard that it is quite expensive compared to Kafka. That's the only concern I can mention; otherwise, it was as impressive as Kafka, better than Kafka based on my experience working on the Solace and Kafka white paper.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature of this solution is the holding and forwarding."
"The initial setup and first deployment of ActiveMQ is fairly simple."
"ActiveMQ demonstrates excellent stability and sturdiness."
"Most people or many people recommended using ActiveMQ on small and medium-scale applications."
"The ability to store the failed events for some time is valuable."
"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."
"The most important feature is that it's best for JVM-related languages and JMS integration."
"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."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"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 useful features has been the WAN optimization and probably the HybridEdge, which requires some third-party adapters or plugins. The idea that we can position Solace as a protocol-agnostic message transport fabric is key to our company having all manners of asynchronous messaging protocols from MQ, Kafka, JMS, etc. I really like the WAN optimization: Send once over a WAN, then distribute locally as many times as there are subscribers."
"The best features of PubSub+ Platform include being highly scalable, allowing us to handle billions and billions of events, and configuring and managing PubSub+ Platform is straightforward and simple while being highly reliable."
"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."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"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 way we can replicate information and send it to several subscribers is most valuable. It can be used for any kind of business where you've got multiple users who need information. Any company, such as LinkedIn, with a huge number of subscribers and any business, such as publishing, supermarket, airline, or shipping can use it."
 

Cons

"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."
"This solution could improve by providing better documentation."
"One potential area would be the complexity of the initial setup."
"It does not scale out well. It ends up being very complex if you have a lot of mirror queues."
"Message Management: Better management of the messages. Perhaps persist them, or put in another queue with another life cycle."
"For additional functionality, I suggest making it easier to install and monitor the queues, topics, broker status, publisher status, and consumer status. Improved monitoring tools would help avoid needing to manually access the server for monitoring purposes."
"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."
"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 deployment process is complex."
"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."
"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."
"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 heard that it is quite expensive compared to Kafka."
"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."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"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."
 

Pricing and Cost Advice

"I use open source with standard Apache licensing."
"There are no fees because it is open-source."
"The solution is less expensive than its competitors."
"The tool's pricing is reasonable and competitive compared to other solutions."
"ActiveMQ is open source, so it is free to use."
"It’s open source, ergo free."
"We are using the open-source version, so we have not looked at any pricing."
"We use the open-source version."
"The price of the solution is expensive."
"We have been really happy with the product licensing rates. It has been free for us, up to a 100,000 transactions per second, and all we have to do is pay for support. Making their product available and accessible to us has not been a problem at all."
"The licensing is dependent on the volume that is flowing. If you go for their support services, it will cost some more money, but I think it is worth it, especially if you are just starting your journey."
"We are looking for something that will add value and fit for purpose. Freeware is good if you want to try something quickly without putting in much money. However, as far as our decision is concerned, I don't think it helps. At the end of the day, if we are convinced that a capability is required, we will ask for the funding. Then, when the funding is available, we will go for an enterprise solution only."
"I would rate the product's pricing a ten out of ten."
"Having a free version of the solution was a big, important part of our decision to go with it. This was the big driver for us to evaluate Solace. We started using it as the free version. When we felt comfortable with the free version, that is when we bought the enterprise version."
"Having a free version is critical for our technology operations use case. This is primarily because our technology operations team is a cost center in our company. They are not profit drivers and having a free version for installation will probably meet our needs. Even for production, it'll support up to a 100,000 messages per second. I don't think in technology operations that we have that many events and alerts from our detection tools. Even if I have 20 or 30 event detection products out there, they're only going to publish the things which are critical or warnings. I don't think we'll ever reach a 100,000 messages per second."
"It could be cheaper. Its licensing is on a yearly basis."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
882,813 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
30%
Computer Software Company
10%
Manufacturing Company
8%
Government
7%
Financial Services Firm
26%
Manufacturing Company
10%
Retailer
9%
Computer Software Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise17
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise14
 

Questions from the Community

What do you like most about ActiveMQ?
For reliable messaging, the most valuable feature of ActiveMQ for us is ensuring prompt message delivery.
What needs improvement with ActiveMQ?
Pricing is something to consider with ActiveMQ, though cloud pricing is not costly and depends upon the compute selection. Focusing on AI is essential nowadays. AI capabilities require improvement ...
What is your primary use case for ActiveMQ?
In my current organization, I'm only working with ActiveMQ. I previously worked with IBM WebSphere MQ.
What is your experience regarding pricing and costs for PubSub+ Event Broker?
I do not know about the pricing of PubSub+ Platform because I did not manage the instance.
What needs improvement with PubSub+ Event Broker?
Additional in-line information about certain things on PubSub+ Platform could be more beneficial for new users who are just starting to use this technology. The analytics tools integrated within Pu...
What is your primary use case for PubSub+ Event Broker?
I describe the main use cases for PubSub+ Platform as wanting to use it as a messaging queue pipeline for managing the data stream events in our IoT platform while I was working at an IoT-based com...
 

Comparisons

 

Also Known As

AMQ
PubSub+ Event Broker, PubSub+ Event Portal
 

Overview

 

Sample Customers

University of Washington, Daugherty Systems, CSC, STG Technologies, Inc. 
FxPro, TP ICAP, Barclays, Airtel, American Express, Cobalt, Legal & General, LSE Group, Akuna Capital, Azure Information Technology, Brand.net, Canadian Securities Exchange, Core Transport Technologies, Crédit Agricole, Fluent Trade Technologies, Harris Corporation, Korea Exchange, Live E!, Mercuria Energy, Myspace, NYSE Technologies, Pico, RBC Capital Markets, Standard Chartered Bank, Unibet 
Find out what your peers are saying about ActiveMQ vs. PubSub+ Platform and other solutions. Updated: February 2026.
882,813 professionals have used our research since 2012.