Try our new research platform with insights from 80,000+ expert users

IBM MQ vs TIBCO Enterprise Message Service comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM MQ
Ranking in Business Activity Monitoring
1st
Ranking in Message Oriented Middleware (MOM)
1st
Average Rating
8.4
Reviews Sentiment
6.9
Number of Reviews
163
Ranking in other categories
Message Queue (MQ) Software (1st)
TIBCO Enterprise Message Se...
Ranking in Business Activity Monitoring
2nd
Ranking in Message Oriented Middleware (MOM)
3rd
Average Rating
8.0
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of February 2025, in the Business Activity Monitoring category, the mindshare of IBM MQ is 42.2%, down from 43.7% compared to the previous year. The mindshare of TIBCO Enterprise Message Service is 21.7%, down from 27.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Business Activity Monitoring
 

Featured Reviews

SelvaKumar4 - PeerSpot reviewer
Offers the ability to batch metadata transfers between systems that support MQ as the communication method
We find it scalable for internal applications, but not so much for external integrations. It should support a wider range of protocols, not just a few specific ones. Many other products have broader protocol support, and IBM MQ is lagging in that area. IBM MQ needs to improve the UI for quicker logging. Users should also have a lot more control over logging, with a dashboard-like interface. That's something they should definitely work on.
Ray Ochieng - PeerSpot reviewer
A value-for-money solution with the requisite features to facilitate efficient communication within an organization
We have been struggling with the stability of TIBCO Enterprise Message Service (EMS), but now I don't know how to differentiate whether the issues are caused by the infrastructure or the product itself. So, I am hesitant to provide a rating because I suspect that it might be due to my setup or environment. I really don't know how to evaluate the product independently. We have faced challenges with EMS, but I am unsure if it is related to infrastructure or the product itself. Even if I reach out for support, I am uncertain if the issue will be resolved since it could be partly related to the product. It's a tough situation.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"I have found the solution to be very robust. It has a strong reputation, easy to use, simple to configure in our enterprise software, and supports all the protocols that we use."
"Integrates between distributed systems: For example, it can help integrate processing between mainframe, client-server, web-based applications by integrating the messages, supporting Service Oriented Architecture."
"We use our routing feature when the request is coming from the business application. The request goes to the distributive side and it is routed to the right claim instance."
"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."
"It also has a backup queue concept and topics, features that I have not seen anywhere else. I like these features very much."
"I appreciate the level of control we have over queue managers, queues, and the messaging itself. That provides good security. So, the control and scalability of messaging are important to me."
"The product helps us monitor messages with other queues, view duplicated messages and control undelivered messages."
"I think the whole product is useful. Their database and all is very good, and the product is fine. The fact that it ensures message delivery is probably the most important thing. I also like that you're able to trace and track everything. If it doesn't arrive at the destination, it will go back to the queue, and no message will be lost."
"The Enterprise Messaging Server will store the message and wait for other subscribers to come onto the network."
"​The initial setup is straightforward and the product documentation is very good.​"
"It allows us to achieve synchronous as well as asynchronous communication with the added advantage of making the communication reliable."
"It is very useful tool. It is also very easy to learn and implement.​"
"We have implanted the core middleware solution for the organization using this product and it is responsible for communication between different applications."
"TIBCO Enterprise Message Service's most valuable features are rapid zero-code integration and its large number of adapters and plugins."
"The setup was done by TIBCO. It has been stable and has a server."
"I like TIBCO's ability to create versioned queues and persistent messages."
 

Cons

"Everything in the solution could be simplified a little. We have trouble with the configuration and cost which is mostly an internal issue, but nevertheless, the errors do come up when there are configuration changes across a specific version. We have slightly different versions, which may have slightly different configurations which cause issues."
"The monitoring could be improved. It's a pain to monitor the throughput through the MQ. The maximum throughput for a queue or single channel isn't clear. We could also use some professional services by IBM to assess and tune the performance."
"I can't say pricing is good."
"There are things within the actual product itself that can be improved, such as limitations on message length, size, etc. There is no standardized message length outside of IBM. Each of the implementations of the MQ series or support of that functionality varies between various suppliers, and because of that, it is very difficult to move from one to the other. We have IBM MQ, but we couldn't use it because the platform that was speaking to MQ didn't support the message length that was standard within IBM MQ. So, we had to use a different product to do exactly the same thing. So, perhaps, there could be more flexibility in the standards around the message queue. If we had been able to increase the message queue size within the IBM MQ implementation, we wouldn't have had to go over to another competing product because the system that was using MQ messaging required the ability to hold messages that were far larger than the IBM MQ standard. So, there could be a bit more flexibility in the structuring. It has as such nothing to do with the IBM implementation of MQ. It is just that the standard that is being put out onto the market doesn't actually stipulate those types of things."
"There are no improvements needed at this time."
"It's hard to put in a nutshell, but it's sort of developed as more of an on-premise solution. It hasn't moved much away from that."
"The integration capabilities could be even easier."
"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."
"TIBCO also has its proprietary line of cloud-based applications, but specifically, these two products are not cloud compatible."
"Overall, my experience with the support team has been disappointing."
"​Since all the communications goes through this product, it acts as a single point of failure."
"An area for improvement would be integration with the API layer."
"I would like to see better integration with Java and Apache Kafka."
 

Pricing and Cost Advice

"The price of IBM MQ could improve by being less expensive."
"The problem with this product is that it's a little bit expensive."
"Pricing could be better, as with all IBM products. But their performance in production, along with security and scalability, will pay returns in the long run."
"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's a very expensive product."
"IBM's licensing model seems more reasonable than some competitors. They charge based on usage, which is good."
"Small-scale companies may not want to buy IBM MQ because of its high cost."
"It is a licensed product. As compared to an open-source solution, such as RabbitMQ, it is obviously costly. If you're using IBM Message Broker, which is a licensed product, IBM MQ is included in the same license. You don't have to pay separately for IBM MQ. The license cost of IBM MQ is lesser than IBM Message Broker."
"In our case, we didn't pay for each product separately. We simply paid for all those companies that provided the components."
"​The cost of licensing is very high. One should go for the product only if they need to ensure message reliability and they cannot afford to lose messages.​"
report
Use our free recommendation engine to learn which Business Activity Monitoring solutions are best for your needs.
838,713 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
38%
Computer Software Company
12%
Manufacturing Company
6%
Government
4%
Financial Services Firm
45%
Computer Software Company
13%
Transportation Company
5%
Manufacturing Company
4%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What is MQ software?
Hi As someone with 45+ years of experience in the Transaction and Message Processing world, I have seen many "MQ" solutions that have come into the market place. From my perspective, while each pro...
What are the differences between Apache Kafka and IBM MQ?
Apache Kafka is open source and can be used for free. It has very good log management and has a way to store the data used for analytics. Apache Kafka is very good if you have a high number of user...
How does IBM MQ compare with VMware RabbitMQ?
IBM MQ has a great reputation behind it, and this solution is very robust with great stability. It is easy to use, simple to configure and integrates well with our enterprise ecosystem and protocol...
What do you like most about TIBCO Enterprise Message Service?
The setup was done by TIBCO. It has been stable and has a server.
What needs improvement with TIBCO Enterprise Message Service?
Maybe the capability to undergo training for specific functionalities, such as implementing Kaspersky for handling high volume transactions in TIBCO Enterprises Message Service. Occasionally, we su...
What is your primary use case for TIBCO Enterprise Message Service?
I use TIBCO Enterprise Message Service for some of my internal communications. For instance, if there is an API called A that needs to communicate with an API referred to as B, we prefer to use mes...
 

Also Known As

WebSphere MQ
Enterprise Message Service
 

Overview

 

Sample Customers

Deutsche Bahn, Bon-Ton, WestJet, ARBURG, Northern Territory Government, Tata Steel Europe, Sharp Corporation
BNL, SunGard, TUI Group, UTi Worldwide, Yellow Pages Group
Find out what your peers are saying about IBM MQ vs. TIBCO Enterprise Message Service and other solutions. Updated: January 2025.
838,713 professionals have used our research since 2012.