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."We have implemented business to business transactions over MQ messaging. The guaranteed and once only delivery ensures business integrity."
"We like IBM MQ for our synchronous communications and transactional applications that require a lot of CPS."
"It runs everywhere, from the mainframe in the US to the PCs in the Gobi desert attached to an analog modem."
"The feature I find most effective for ensuring message delivery without loss is the backup threshold. This feature allows for automatic retries of transactional messages within a specified threshold."
"IBM is still adding some features and coding some other systems on the security end. However, it has the most security features I've seen in a communication solution. Security is the most important thing for our purposes."
"The thing that I like about MQ most is its reliability. It's one of those types of products that just works. You don't have to tinker around with it too much."
"The most valuable feature of IBM MQ is transaction processing."
"It's highly scalable. It provides various ways to establish high availability and workloads. E.g., you can spread workloads inside of your clusters."
"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."
"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."
"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."
"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."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"The way we can replicate information and send it to several subscribers is most valuable. It can be used for any kind of business where you've got multiple users who need information. Any company, such as LinkedIn, with a huge number of subscribers and any business, such as publishing, supermarket, airline, or shipping can use it."
"In terms of volume, it is not able to handle a huge volume. We also have limitations of queues related to IBM MQ. We often need to handle a very big volume, but currently we do have limitations. If those kinds of limitations could be relaxed, it would help us to work better."
"It could get a face lift with a modern marketing campaign."
"The memory management is very poor and it consumes too much memory."
"We have had scalability issues with some projects in the past."
"It could provide more monitoring tools and some improvement to the UI. I would also like to see more throughput in future versions."
"Scalability is lacking compared to the cloud native products coming into the market."
"They probably need to virtualize the MQ flow and allow us to design the MQ flow using the UI. It would also help to migrate to the cloud easily and implement AWS Lambda functions with minimum coding. If you have to code, then just with NodeJS or Java."
"We are looking at the latest version, and we hope that resilience, high availability, and monitoring will be improved. It can have some more improvements in the heterogeneous messaging feature. The current solution is on-premises, so good integration with public cloud messaging solutions would be useful."
"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."
"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 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 licensing and the cost are the major pitfalls."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
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 "Reliable and stable solution that includes support from the IBM technical team". 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 Apache Kafka, ActiveMQ, VMware RabbitMQ, Red Hat AMQ and TIBCO Enterprise Message Service, whereas PubSub+ Event Broker is most compared with Apache Kafka, VMware RabbitMQ, ActiveMQ, 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.