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 (12th)
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 August 2025, in the Message Queue (MQ) Software category, the mindshare of PubSub+ Platform is 4.6%, down from 4.9% compared to the previous year. The mindshare of Red Hat AMQ is 9.4%, up from 8.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
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.
Sther Martins - PeerSpot reviewer
An easy-to-learn solution that can be used with microservices
We have done around 20 projects in Red Hat AMQ. I have two projects using Red Hat AMQ, and I can share how its scalability has impacted them. In one project, we have a solution for authentication and authorization using SSO. We need to integrate with other systems in two ways. We use Red Hat AMQ for social data, sending messages to other queues, and integrating with business. We have two databases with the same information. The solution is good because it helps us solve problems with messaging. For instance, when messaging doesn't change, we still check the cloud and verify the information. In another project, we have a large banking solution for the Amazon region using Red Hat AMQ for financial transactions. In this solution, business messages are sent, and another system processes them.

Quotes from Members

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

Pros

"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."
"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."
"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 event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"The topic hierarchy is pretty flexible. Once you have the subject defined just about anybody who knows Java can come onboard. The APIs are all there."
"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."
"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."
"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 solution is very lightweight, easy to configure, simple to manage, and robust since it launched."
"The most valuable feature is stability."
"Reliability is the main criterion for selecting this tool for one of the busiest airports in Mumbai."
"I can organize the tool with microservices, which allows me to use it across different services. It is easy to learn."
"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."
"My impression is that it is average in terms of scalability."
 

Cons

"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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."
"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 solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively."
"The integrations could improve in PubSub+ Event Broker."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"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."
"The deployment process is complex."
"The turnaround of adopting new versions of underlying technologies sometimes is too slow."
"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."
"There are several areas in this solution that need improvement, including clustering multi-nodes and message ordering."
"AMQ could be better integrated with Jira and patch management tools."
"The challenge is the multiple components it has. This brings a higher complexity compared to IBM MQ, which is a single complete unit."
"Red Hat AMQ's cost could be improved, and it could have better integration."
 

Pricing and Cost Advice

"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."
"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 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."
"I would rate the product's pricing a ten out of ten."
"It could be cheaper. Its licensing is on a yearly basis."
"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."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"There is a subscription needed for this solution and there are support plans available."
"Red Hat AMQ's pricing could be improved."
"The solution is open-source."
"This is a very cost-effective solution and the pricing is much better than competitors."
"I would rate the pricing a six out of ten, with ten being expensive."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
865,295 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
31%
Manufacturing Company
9%
Computer Software Company
8%
Retailer
8%
Financial Services Firm
24%
Computer Software Company
13%
Government
10%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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...
 

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: July 2025.
865,295 professionals have used our research since 2012.