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
17
Ranking in other categories
Message Oriented Middleware (MOM) (2nd), Event Monitoring (12th), Streaming Analytics (13th)
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 September 2025, in the Message Queue (MQ) Software category, the mindshare of PubSub+ Platform is 4.5%, down from 5.0% compared to the previous year. The mindshare of Red Hat AMQ is 9.6%, up from 8.4% 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.6%
PubSub+ Platform4.5%
Other85.9%
Message Queue (MQ) Software
 

Featured Reviews

BhanuChidigam - PeerSpot reviewer
Performs well, high availability, and helpful support
We use approximately four people for the maintenance of the solution. My advice to others is this solution has high throughput and is used for many stock exchanges. For business critical use cases, such as processing financial transactions at a quick speed, I would recommend this solution. I rate PubSub+ Event Broker an eight out of ten.
SachinJain - PeerSpot reviewer
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 event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"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'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."
"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."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"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."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"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."
"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."
"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."
"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."
"Reliability is the main criterion for selecting this tool for one of the busiest airports in Mumbai."
"My impression is that it is average in terms of scalability."
"The most valuable feature is stability."
"The solution is very lightweight, easy to configure, simple to manage, and robust since it launched."
 

Cons

"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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?"
"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 licensing and the cost are the major pitfalls."
"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."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"If you create one event in the past, you cannot resend it."
"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."
"This product needs better visualization capabilities in general."
"There are several areas in this solution that need improvement, including clustering multi-nodes and message ordering."
"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."
"Red Hat AMQ's cost could be improved, and it could have better integration."
"AMQ could be better integrated with Jira and patch management tools."
"There is improvement needed to keep the support libraries updated."
"The product needs to improve its documentation and training."
"The challenge is the multiple components it has. This brings a higher complexity compared to IBM MQ, which is a single complete unit."
 

Pricing and Cost Advice

"It could be cheaper. Its licensing is on a yearly basis."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"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."
"I would rate the product's pricing a ten out of ten."
"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 price of PubSub+ Event Broker is reasonable for the capability it offers. However, when compared to others solutions on the market it is expensive."
"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."
"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."
"I would rate the pricing a six out of ten, with ten being expensive."
"Red Hat AMQ's pricing could be improved."
"The solution is open-source."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
868,229 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
31%
Manufacturing Company
10%
Retailer
9%
Computer Software Company
6%
Financial Services Firm
25%
Computer Software Company
12%
Government
9%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise1
Large Enterprise12
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise4
Large Enterprise2
 

Questions from the Community

What needs improvement with PubSub+ Event Broker?
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 a...
What is your primary use case for PubSub+ Event Broker?
My typical use case for the PubSub+ Platform is as an event-driven solution for communication between two components.
What advice do you have for others considering PubSub+ Event Broker?
I have experience working with Kafka, PubSub+ Platform, and IBM MQ, all three of them. We are customers, meaning my company uses Solace. We use it and customize it based on our needs. Based on my e...
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...
 

Comparisons

 

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: September 2025.
868,229 professionals have used our research since 2012.