We performed a comparison between PubSub+ Event Broker and Red Hat AMQ based on real PeerSpot user reviews.
Find out in this report how the two Message Queue (MQ) Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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 event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"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."
"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."
"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."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"My impression is that it is average in terms of scalability."
"Red Hat AMQ's best feature is its reliability."
"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."
"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."
"The most valuable feature is stability."
"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 would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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."
"If you create one event in the past, you cannot resend it."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"The deployment process is complex."
"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 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."
"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."
"AMQ could be better integrated with Jira and patch management tools."
"This product needs better visualization capabilities in general."
"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."
PubSub+ Event Broker is ranked 6th in Message Queue (MQ) Software with 15 reviews while Red Hat AMQ is ranked 8th in Message Queue (MQ) Software with 7 reviews. PubSub+ Event Broker is rated 8.6, while Red Hat AMQ is rated 8.2. The top reviewer of PubSub+ Event Broker writes "Event life cycle management changes the way a designer or architect will design a topic and discover what is available". On the other hand, the top reviewer of Red Hat AMQ writes "A stable, open-source technology, with a convenient deployment". PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, VMware RabbitMQ and ActiveMQ, whereas Red Hat AMQ is most compared with Apache Kafka, ActiveMQ, IBM MQ and VMware RabbitMQ. See our PubSub+ Event Broker vs. Red Hat AMQ report.
See our list of best Message Queue (MQ) Software vendors.
We monitor all Message Queue (MQ) Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
