We performed a comparison between PubSub+ Event Broker and Red Hat JBoss A-MQ for xPaaS based on real PeerSpot user reviews.
Find out what your peers are saying about Apache, IBM, Amazon Web Services (AWS) and others in Message Queue (MQ) Software."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."
"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."
"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."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"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."
"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."
"JBoss is easy to use, and we have a good partner here in Tunisia to provide local support."
"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."
"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."
"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."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"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."
"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."
"If you create one event in the past, you cannot resend it."
"JBoss could add more automation."
PubSub+ Event Broker is ranked 6th in Message Queue (MQ) Software with 15 reviews while Red Hat JBoss A-MQ for xPaaS is ranked 12th in Message Queue (MQ) Software with 1 review. PubSub+ Event Broker is rated 8.6, while Red Hat JBoss A-MQ for xPaaS is rated 8.0. 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 JBoss A-MQ for xPaaS writes "It's scalable and easy to use, and we have local support here in Tunisia". PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, VMware RabbitMQ, ActiveMQ and Confluent, whereas Red Hat JBoss A-MQ for xPaaS is most compared with IBM MQ and Apache Kafka.
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.