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."The solution is very easy to work with."
"Setting up MQ is easy. We had a "grow as you go" implementation strategy. We started with a single channel and progressed to multiple queues and channels depending on the systems and integrations with other systems. It was a gradual deployment and expansion as we grew the services interacting with the core system using MQ."
"Overall the solution operates well and has good integration."
"Currently, we are not using many advanced features. We are only using point-to-point MQ. I have previously used features like context-based authentication, SSL authentication, and high availability. These are good and pretty cool features. They make your business reliable. For critical business needs, everyone uses only IBM MQ. It is the first choice because of its reliability. There is a one-send-and-one-delivery feature. It also has a no-message-loss feature, and because of that, only IBM MQ is used in banking or financial sectors."
"It also has a backup queue concept and topics, features that I have not seen anywhere else. I like these features very much."
"It offers better reliability and monitoring compared to other tools."
"The most valuable feature is the stability. It's perfect in this way."
"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."
"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."
"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 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."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"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."
"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."
"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."
"IBM HQ's scalability isn't the best."
"We have had scalability issues with some projects in the past."
"The solution should offer a freeware version, free vouchers, or certifications for learning purposes and building knowledge base."
"It is expensive. The cost is high. There should be more improvement in the new age of technologies."
"They have provided a Liberty Profile in the Web Console for administration, and that could be further enhanced. It is not fit for use by an enterprise. They have to get rid of their WebSphere process and develop a front-end on Node.js or the like."
"The worst part is the monitoring or admin, especially in the ACE or Broker. There is always a problem of transparency. In MQ you can observe any process and you know exactly what's going on behind the scenes, but with the ACE or Broker, it's a problem monitoring the HTTP inputs. It's like a black box."
"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."
"A challenge we currently have is Solace's ability to integrate with single sign-on in our Active Directory and other single sign-on tools and platforms that any company would have. It's important for the platforms to work. Typically, they support only LDAP-based connectivity to our SQL Servers."
"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."
"If you create one event in the past, you cannot resend it."
"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."
"The licensing and the cost are the major pitfalls."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"The deployment process is complex."
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.