We performed a comparison between IBM MQ and PubSub+ Event Broker 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."Reliable messaging and throughput are the most valuable."
"Data integrity, reliability and security are valuable features that IBM MQ possesses."
"The high availability and session recovery are the most valuable features because we need the solution live all day."
"The most valuable feature of IBM MQ is it has all the features necessary for contemporary messaging, not only for the financial industry but for any application."
"This solution has improved and influenced the communication between different applications, then standardized that communication."
"Whenever payments are happening, such as incoming payments to the bank, we need to notify the customer. With MQ we can actually do that asynchronously. We don't want to notify the customer for each and every payment but, rather, more like once a day. That kind of thing can be enabled with the help of MQ."
"I like the MQ's simplicity and rock-solid stability. I've never experienced a failure in two decades caused by the product itself. It has only failed due to human error."
"I like the architecture it provides seamlessly for assured delivery."
"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."
"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."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"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."
"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 valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"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 event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"IBM MQ's pricing is higher than its competitors'."
"At a recent conference, I went to a presentation that had the latest version and it has amazing stuff that's coming out. So, I am excited to use those, specifically surrounding the web console and the fact that it's API integrated."
"The initial setup is difficult. Creating your own cluster is difficult. Working with cluster repositories is difficult. Issue management with IBM MQ is difficult."
"There are many complications with IBM MQ servers."
"The licensing fees should be more cost-effective so that we can better pitch the product to our clients. With the pricing as it is, they tend to move away from IBM products."
"IBM MQ is not very user-friendly."
"I don’t like legacy view of MQ."
"The scalability is the one area where IBM has fallen behind. As much as it is used, there is a limit to the number of people who are skilled in MQ. That is definitely an issue. Places have kept their MQ-skilled people and other places have really struggled to get MQ skills. It's not a widely-known skillset."
"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 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."
"If you create one event in the past, you cannot resend it."
"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."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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?"
"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."
IBM MQ is ranked 2nd in Message Queue (MQ) Software with 158 reviews while PubSub+ Event Broker is ranked 6th in Message Queue (MQ) Software with 15 reviews. IBM MQ is rated 8.4, while PubSub+ Event Broker is rated 8.6. The top reviewer of IBM MQ writes "Offers the ability to batch metadata transfers between systems that support MQ as the communication method". On the other hand, 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". IBM MQ is most compared with ActiveMQ, Apache Kafka, VMware Tanzu Data Services, Red Hat AMQ and Amazon SQS, whereas PubSub+ Event Broker is most compared with Apache Kafka, ActiveMQ, VMware Tanzu Data Services, Confluent and Amazon EventBridge. See our IBM MQ vs. PubSub+ Event Broker report.
See our list of best Message Queue (MQ) Software vendors and best Message Oriented Middleware (MOM) 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.