Sunil SahooManager at a financial services firm
Sachar De VriesHead of Infrastructure at Grasshopper
We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"The most valuable features are the point to point messaging and the MQ API."
"The high availability and session recovery are the most valuable features because we need the solution live all day."
"It is stable, reliable, and scalable."
"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."
"It's highly scalable. It provides various ways to establish high availability and workloads. E.g., you can spread workloads inside of your clusters."
"IBM MQ is the right choice because of the stability and the performance. And from the support perspective, it's enough to have a really small team."
"The MQ protocol is widely used across multiple applications and it's so simple for connectivity."
"What is quite useful is the asynchronous function which means we don't lose everything in the bank. Although we use a lot of things synchronously, asynch is the best thing so that no banking information is ever lost, even when the network goes down and comes up."
"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."
"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."
"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 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."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"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."
"I would like to see faster monitoring tools for this solution."
"If they could come up with monitoring dashboards that would be good. We are using external monitoring tools, apart from our IBM MQ, to monitor IBM MQ. If we could get monitoring tools or dashboards to keep everything simple for the user to understand, that would be good."
"I would like to see it integrate with the newer ways of messaging, such as Kafka. They might say that you have IBM Integration Bus to do that stuff, but it would be great if MQ could, out-of-the-box, listen to public Kafka."
"They could integrate monitoring into the solution, a bit more than they do now. Currently, they have opened the REST API so you can get statistic and accounting information and details from MQ and build your own monitoring, if you want. IBM can improve the solution in this direction."
"What could be improved is the high-availability. The way MQ works is that it separates the high-availability from the workload balance. The scalability should be easier. If something happens so that the messages are not available on each node, scalability is only possible for the workload balance."
"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."
"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."
"You should be able to increase the message size. It should be dynamic. Each queue has a limitation of 5,000."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"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."
"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."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"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."
"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."
"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 price is high."
"There is a different platform price between Windows, z/OS, and iSeries."
"IBM products, in general, have high licensing costs and support costs are too high."
"Most of our customers are quite happy with the solution but they have an issue with the cost. They want to move to cheaper solutions."
"It is a very expensive product compared to the open source products in the market."
"It would be a 10 out of 10 if it wasn't so expensive."
"It's a very expensive product."
"IBM MQ is expensive and they charge based on the CPU."
"There are different tiers where you can choose what would work for you. As a customer, you need to know roughly how many messages a month you will use."
"We have been really happy with the product licensing rates. It has been free for us, up to a 100,000 transactions per second, and all we have to do is pay for support. Making their product available and accessible to us has not been a problem at all."
"Having a free version is critical for our technology operations use case. This is primarily because our technology operations team is a cost center in our company. They are not profit drivers and having a free version for installation will probably meet our needs. Even for production, it'll support up to a 100,000 messages per second. I don't think in technology operations that we have that many events and alerts from our detection tools. Even if I have 20 or 30 event detection products out there, they're only going to publish the things which are critical or warnings. I don't think we'll ever reach a 100,000 messages per second."
"Having a free version of the solution was a big, important part of our decision to go with it. This was the big driver for us to evaluate Solace. We started using it as the free version. When we felt comfortable with the free version, that is when we bought the enterprise version."
"The pricing and licensing were very transparent and well-communicated by our account manager."
"We are looking for something that will add value and fit for purpose. Freeware is good if you want to try something quickly without putting in much money. However, as far as our decision is concerned, I don't think it helps. At the end of the day, if we are convinced that a capability is required, we will ask for the funding. Then, when the funding is available, we will go for an enterprise solution only."
"The licensing is dependent on the volume that is flowing. If you go for their support services, it will cost some more money, but I think it is worth it, especially if you are just starting your journey."
"It could be cheaper. Its licensing is on a yearly basis."
IBM MQ provides the universal messaging backbone for service-oriented architecture (SOA) connectivity. It connects virtually any commercial IT system, whether on premise, in the cloud, or a mixture. For more than 20 years IBM has led the market in messaging middleware and more than 10,000 businesses across all geographies and industries rely on IBM MQ.
Visit for your trial here.
PubSub+ is a complete event streaming and management platform for the real-time enterprise.
PubSub+ helps enterprises design, deploy and manage event-driven architectures across hybrid cloud, multi-cloud and IoT environments, so they can be more integrated and event-driven.
The "+" in PubSub+ means it supports a wide range of message exchange patterns beyond publish/subscribe, including request/reply, streaming and replay, as well as different qualities of service, such as best effort and guaranteed delivery. It's available as an appliance, software, and as-a-service. All options offer the same functionality and management experience.
PubSub+ lets users connect event brokers to form an event mesh - an architectural layer that supports dynamically routing events from one application to any other application no matter where those applications are deployed (no cloud, private cloud, public cloud) - so users can connect and orchestrate microservices, push events from on-premesis systems of record to cloud services, and enable digital transformation across LoBs and IoT.
Its APIs supports popular programming languages, with open APIs and protocols to connect to any application, providing a best-in-class approach to messaging to never get locked in to any technology — including the vendor's own.
IBM MQ is ranked 1st in Message Queue (MQ) Software with 34 reviews while PubSub+ Event Broker is ranked 3rd in Message Queue (MQ) Software with 9 reviews. IBM MQ is rated 8.2, while PubSub+ Event Broker is rated 8.8. The top reviewer of IBM MQ writes "We don't lose messages in transit and we can store messages and forward them when required". On the other hand, the top reviewer of PubSub+ Event Broker writes "We can add an application or users in the middle of the day, with no disruption to anyone". IBM MQ is most compared with Apache Kafka, VMware RabbitMQ, ActiveMQ, Anypoint MQ and TIBCO Enterprise Message Service, whereas PubSub+ Event Broker is most compared with Apache Kafka, VMware RabbitMQ, Amazon EventBridge, ActiveMQ and TIBCO Enterprise Message Service. See our IBM MQ vs. PubSub+ Event Broker report.
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.