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 (13th), Streaming Analytics (14th)
Red Hat AMQ
Ranking in Message Queue (MQ) Software
6th
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 January 2026, in the Message Queue (MQ) Software category, the mindshare of PubSub+ Platform is 4.3%, down from 5.3% compared to the previous year. The mindshare of Red Hat AMQ is 9.5%, up from 8.6% 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 AMQ9.5%
PubSub+ Platform4.3%
Other86.2%
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."
"I rate the PubSub+ Platform a 9 out of 10."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"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 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."
"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."
"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."
"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."
"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."
"The solution is very lightweight, easy to configure, simple to manage, and robust since it launched."
"I can organize the tool with microservices, which allows me to use it across different services. It is easy to learn."
"The most valuable feature is stability."
"Red Hat AMQ's best feature is its reliability."
"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."
"My impression is that it is average in terms of scalability."
 

Cons

"I heard that it is quite expensive compared to Kafka."
"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."
"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."
"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?"
"If you create one event in the past, you cannot resend it."
"The integrations could improve in PubSub+ Event Broker."
"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."
"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."
"Red Hat AMQ's cost could be improved, and it could have better integration."
"This product needs better visualization capabilities in general."
"The product needs to improve its documentation and training."
"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."
"There is improvement needed to keep the support libraries updated."
"AMQ could be better integrated with Jira and patch management tools."
 

Pricing and Cost Advice

"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."
"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."
"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."
"The price of PubSub+ Event Broker is reasonable for the capability it offers. However, when compared to others solutions on the market it is expensive."
"I would rate the product's pricing a ten out of ten."
"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."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"Red Hat AMQ's pricing could be improved."
"The solution is open-source."
"There is a subscription needed for this solution and there are support plans available."
"I would rate the pricing a six out of ten, with ten being expensive."
"This is a very cost-effective solution and the pricing is much better than competitors."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
879,422 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
27%
Manufacturing Company
10%
Retailer
10%
Computer Software Company
6%
Financial Services Firm
22%
Computer Software Company
12%
Government
11%
Manufacturing Company
8%
 

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: December 2025.
879,422 professionals have used our research since 2012.