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 (13th), Streaming Analytics (11th)
Red Hat AMQ
Ranking in Message Queue (MQ) Software
6th
Average Rating
8.0
Reviews Sentiment
7.3
Number of Reviews
9
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2025, in the Message Queue (MQ) Software category, the mindshare of PubSub+ Platform is 4.7%, down from 4.8% compared to the previous year. The mindshare of Red Hat AMQ is 9.6%, up from 8.2% 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

"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 like the seamless flexibility in protocol exchange offering without writing a code."
"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."
"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."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"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."
"Red Hat AMQ's best feature is its reliability."
"The solution is very lightweight, easy to configure, simple to manage, and robust since it launched."
"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."
"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."
"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."
 

Cons

"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 integrations could improve in PubSub+ Event Broker."
"The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively."
"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."
"I heard that it is quite expensive compared to Kafka."
"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 deployment process is complex."
"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."
"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."
"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."
"The product needs to improve its documentation and training."
 

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

Top Industries

By visitors reading reviews
Financial Services Firm
34%
Computer Software Company
11%
Retailer
8%
Manufacturing Company
7%
Financial Services Firm
26%
Computer Software Company
13%
Government
9%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with PubSub+ Event Broker?
The solution could be improved by enhancing the message pooling size for persistent messages to handle both small and large messages effectively. Additionally, providing a comprehensive dashboard t...
What is your primary use case for PubSub+ Event Broker?
We use PubSub+ primarily for long processing messages. For instance, we generate customer forms, which take a longer time. We place these requests in queues, process them, and return them to the qu...
What advice do you have for others considering PubSub+ Event Broker?
I recommend considering Solace due to its enterprise-level features, high throughput, cloud integration, and security. It is a top competitor among similar products and offers significant benefits ...
What do you like most about Red Hat AMQ?
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.
What needs improvement with Red Hat AMQ?
The product needs to improve its documentation and training.
What is your primary use case for Red Hat AMQ?
We just started working with Red Hat AMQ. We selected it as the ESB (Enterprise Service Bus) platform for a new airport project. I manage the entire Master System Integration (MSI) project for one ...
 

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: June 2025.
856,873 professionals have used our research since 2012.