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

PubSub+ Platform vs Red Hat AMQ 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

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)
Red Hat AMQ
Ranking in Message Queue (MQ) Software
7th
Average Rating
8.2
Reviews Sentiment
6.7
Number of Reviews
10
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2026, in the Message Queue (MQ) Software category, the mindshare of PubSub+ Platform is 4.2%, down from 5.2% compared to the previous year. The mindshare of Red Hat AMQ is 8.9%, up from 8.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software Market Share Distribution
ProductMarket Share (%)
Red Hat AMQ8.9%
PubSub+ Platform4.2%
Other86.9%
Message Queue (MQ) Software
 

Featured Reviews

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.
SachinJain - PeerSpot reviewer
Senior Technical Specialist at Intuitive Technology Partners
Efficiently manages high availability and fault tolerance for critical systems with user-friendly management features
I have experience with features such as message persistence and fault tolerance because I configured high availability and fault tolerance for the client environment, including active-active and active-passive configurations. I mainly prefer active-active. I created a security feature for user authentication and authorization in Red Hat AMQ using vault. When you enable the vault, then your whole Red Hat AMQ becomes more secure. Management is straightforward. I configured it and created documentation. The operations team takes care of the operation part. I educate them on how to manage access, so they can easily add new people who join the company or manage the people who leave. The benefits of using Red Hat AMQ include easy configuration and monitoring. On the portal, I can monitor how many packets or alerts have been generated or sent to the end user via Red Hat AMQ along with messages or emails. It also shows utilization in the tool. These features also come with other AMQs such as Amazon and IBM.

Quotes from Members

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

Pros

"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."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"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."
"Some valuable features include reconnecting topics, placing queues, and direct connections to MongoDB. The platform provides a dashboard to monitor the status of messages, such as how many have been processed or delivered, which is helpful for tracking performance."
"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."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"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."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"I can organize the tool with microservices, which allows me to use it across different services. It is easy to learn."
"Reliability is the main criterion for selecting this tool for one of the busiest airports in Mumbai."
"Red Hat AMQ's best feature is its reliability."
"The benefits of using Red Hat AMQ include easy configuration and monitoring; on the portal, I can monitor how many packets or alerts have been generated or sent to the end user via Red Hat AMQ along with messages or emails, and it also shows utilization in the tool."
"AMQ is highly scalable and performs well. It can process a large volume of messages in one second. AMQ and OpenShift are a good combination."
"The most valuable feature for us is the operator-based automation that is provided by Streams for infrastructure as well as user and topic management. This saves a lot of time and effort on our part to provide infrastructure. For example, the deployment of infrastructure is reduced from approximately a week to a day."
"This product is well adopted on the OpenShift platform. For organizations like ours that use OpenShift for many of our products, this is a good feature."
"My impression is that it is average in terms of scalability."
 

Cons

"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 integrations could improve in PubSub+ Event Broker."
"A challenge we currently have is Solace's ability to integrate with single sign-on in our Active Directory and other single sign-on tools and platforms that any company would have. It's important for the platforms to work. Typically, they support only LDAP-based connectivity to our SQL Servers."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"The licensing and the cost are the major pitfalls."
"If you create one event in the past, you cannot resend it."
"The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively."
"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."
"AMQ could be better integrated with Jira and patch management tools."
"The product needs to improve its documentation and training."
"There is improvement needed to keep the support libraries updated."
"There are some aspects of the monitoring that could be improved on. There is a tool that is somewhat connected to Kafka called Service Registry. This is a product by Red Hat that I would like to see integrated more tightly."
"This product needs better visualization capabilities in general."
"The turnaround of adopting new versions of underlying technologies sometimes is too slow."
"The challenge is the multiple components it has. This brings a higher complexity compared to IBM MQ, which is a single complete unit."
"There are several areas in this solution that need improvement, including clustering multi-nodes and message ordering."
 

Pricing and Cost Advice

"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."
"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."
"It could be cheaper. Its licensing is on a yearly basis."
"There are different tiers where you can choose what would work for you. As a customer, you need to know roughly how many messages a month you will use."
"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."
"The price of the solution is expensive."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"The solution is open-source."
"I would rate the pricing a six out of ten, with ten being expensive."
"Red Hat AMQ's pricing could be improved."
"This is a very cost-effective solution and the pricing is much better than competitors."
"There is a subscription needed for this solution and there are support plans available."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
882,260 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise14
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise4
Large Enterprise2
 

Questions from the Community

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...
What needs improvement with Red Hat AMQ?
The areas for improvement include cost, which is a primary concern. The deployment process is simple, but the cost is very important. Additionally, the management portal should be more user-friendl...
What is your primary use case for Red Hat AMQ?
For use cases for Red Hat AMQ, let's take banking purposes. This depends upon the firm or the service or product company. For example, let's take HDFC Bank or any other bank. Whenever a customer de...
What advice do you have for others considering Red Hat AMQ?
I work primarily with Red Hat. For IBM, I have worked with their channel partner, not directly with IBM. For Amazon, I work with partners only. I am working with one company as a consultant. I also...
 

Also Known As

PubSub+ Event Broker, PubSub+ Event Portal
Red Hat JBoss A-MQ, Red Hat JBoss AMQ
 

Overview

 

Sample Customers

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 
E*TRADE, CERN, CenturyLink, AECOM, Sabre Holdings
Find out what your peers are saying about PubSub+ Platform vs. Red Hat AMQ and other solutions. Updated: February 2026.
882,260 professionals have used our research since 2012.