No more typing reviews! Try our Samantha, our new voice AI agent.

PubSub+ Platform vs Red Hat AMQ comparison

Why PeerSpot?
 

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
10th
Average Rating
8.6
Reviews Sentiment
6.9
Number of Reviews
20
Ranking in other categories
Message Oriented Middleware (MOM) (2nd), Event Monitoring (13th), Streaming Analytics (14th)
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 November 2026, in the Message Queue (MQ) Software category, the mindshare of PubSub+ Platform is 5.7%, up from 4.4% compared to the previous year. The mindshare of Red Hat AMQ is 5.2%, down from 9.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Queue (MQ) Software Mindshare Distribution
ProductMindshare (%)
Red Hat AMQ5.2%
PubSub+ Platform5.7%
Other89.1%
Message Queue (MQ) Software
 

Featured Reviews

Parth Mehta - PeerSpot reviewer
Senior Software Engineer at Luxoft
Event platform has transformed real-time trading data processing and accelerates client onboarding
There is one important thing about how Solace Platform can be improved, and the pain points are part of that. In my seven months of experience, I understand that it should have a better Standard Edition. It has two editions, Standard and Enterprise, and in production they should offer better free services in the Standard Edition at least, so it can help smaller organizations onboard and then move to the Enterprise Edition. I expect them to increase the availability of free editions and more services, so they can get better coverage from different clients, starting from smaller ones. Compared to Kafka, message replay was not available, but they are going to announce it very soon with a better approach for replaying failure cases, which Kafka supports very well. They have this issue right now. Solace Platform is generally evolving day to day, from a single broker to event mesh, which I mentioned, but it still has a limitation that has to be improved. I also expect more insightful observability integrations, such as OpenTelemetry-enabled distributed tracing. I can see they are working on this, but it does not look better right now, and they need to work more in that area. They should also have their own dedicated portal where I can configure everything and monitor everything per my customization. That is what I expect. There are other areas Solace Platform should focus on next. In seven months, I would say it has a lot to offer us, but I have a lot of Kafka experience from before I moved over in the last seven months. I think they need to improve pricing transparency, because their pricing is not publicly available. They should clarify their pricing. They also have the problem of being a single vendor commercial platform, which should not be the case. They should have more long-term event storage and retention capability, which I found to be the biggest gap since we are leveraging a real-time distribution broker. It is not durable right now compared to Kafka, which has indefinite event processing commit logs. It does not have that much compared to its rival Kafka. As I mentioned, they should support more of an open-source ecosystem instead of being tied to their own localized products, which Kafka does very well, so they can gain more popularity. In stream processing, it also lacks a native, first-class stream processing layer equivalent to Kafka Streams. They are not strong in stream analytics, so they have to improve in that area as well. Beyond what we already discussed, Solace Platform needs good long-term event support, since if something fails, it needs better long-term availability for replay. I would also request that they improve their version release timeline. They have to fix some smaller issues that we already raised from our side, such as not having indefinite commit logs or replay of failed events. That is why I introduced Kafka, where I can put all of this, and they should support more here. They should also support more AI offerings. I can see they provide Google ADK support in development and LangGraph, but they should support Claude or other more efficient LLMs. As I mentioned, they have a single vendor commercial platform, and the vendor lock-in perception has to be removed compared to their open-source rival Kafka. This is what I can see. Anyway, they are maturing, so I would say they can definitely improve day to day.
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

"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"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."
"If we talk about Solace, you see the value-add layer; I can say that Solace is a basic Kafka, but on top of that Kafka layer, they have added their own layer that is really good, as this is where it adds value and why we went for it."
"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."
"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."
"It is a product that is more like a switch or router, where you install it, then it keeps on working."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"Solace Platform is particularly engineered for ultra-low latency and high-throughput data processing with inbuilt high availability and disaster recovery, which is quite a bit better in our use case compared to Kafka."
"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."
"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."
"My impression is that it is average in terms of scalability."
"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 self-service aspect is very important for us, and AMQ Streams has enabled us to deliver new services faster, going from days to hours."
"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."
"The solution is very lightweight, easy to configure, simple to manage, and robust since it launched."
 

Cons

"I heard that it is quite expensive compared to Kafka."
"They should have more long-term event storage and retention capability, which I found to be the biggest gap since we are leveraging a real-time distribution broker."
"Make it open source :-) with limited features so that this is not a barrier for using the technology in some places where they will only use open source technology despite then just paying for support (and paid features) on any used open source technology in the organization, as its a misnomer in my view the amount of large companies claiming to only use open source but then using products that are paid versions with additional features included."
"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?"
"The deployment process is complex."
"Potential areas for improvement in PubSub+ Platform are its authentication mechanisms, which could be slightly better."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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 challenge is the multiple components it has. This brings a higher complexity compared to IBM MQ, which is a single complete unit."
"This solution is completely unstable. We lose messages."
"The product needs to improve its documentation and training."
"The areas for improvement include cost, which is a primary concern."
"Red Hat AMQ's cost could be improved, and it could have better integration."
"There are several areas in this solution that need improvement, including clustering multi-nodes and message ordering."
"The turnaround of adopting new versions of underlying technologies sometimes is too slow."
"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."
 

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."
"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 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."
"It could be cheaper. Its licensing is on a yearly basis."
"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."
"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."
"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."
"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."
report
Use our free recommendation engine to learn which Message Queue (MQ) Software solutions are best for your needs.
922,528 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Manufacturing Company
11%
Outsourcing Company
10%
Construction Company
8%
Financial Services Firm
15%
Outsourcing Company
11%
Manufacturing Company
9%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise1
Large Enterprise16
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?
The pricing and setup cost of PubSub+ Platform is very seamless and reliable for medium and large-scale enterprises. For small-sized enterprises, it may be a higher cost, or they may be looking for...
What needs improvement with PubSub+ Event Broker?
PubSub+ Platform could improve by simplifying some advanced configurations and providing better visualization for event flow. Some advanced configurations in PubSub+ Platform could be made simpler ...
What is your primary use case for PubSub+ Event Broker?
PubSub+ Platform's main use case in our company is real-time data streaming using applications and API integrations. We are working on an IoT-based application, and our company handles most of ...
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 cus...
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: November 2026.
922,528 professionals have used our research since 2012.