No more typing reviews! Try our Samantha, our new voice AI agent.

IBM MQ vs TIBCO FTL 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 Message Oriented Middleware (MOM)
1st
Average Rating
8.4
Reviews Sentiment
6.7
Number of Reviews
174
Ranking in other categories
Business Activity Monitoring (1st), Message Queue (MQ) Software (1st)
TIBCO FTL
Ranking in Message Oriented Middleware (MOM)
7th
Average Rating
9.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Message Oriented Middleware (MOM) category, the mindshare of IBM MQ is 16.3%, down from 28.0% compared to the previous year. The mindshare of TIBCO FTL is 5.6%, down from 7.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Message Oriented Middleware (MOM) Mindshare Distribution
ProductMindshare (%)
IBM MQ16.3%
TIBCO FTL5.6%
Other78.1%
Message Oriented Middleware (MOM)
 

Featured Reviews

David Pizinger - PeerSpot reviewer
Enterprise Technical Leader at a tech vendor with 10,001+ employees
Has faced unexpected VM restarts but continues to deliver messages reliably
I'm not sure if we've utilized IBM MQ's high availability. Our MQ VMs are set up in clusters, and I think our queue managers are set up in pairs. However, I don't know if we actually use any specific high availability features of IBM MQ that are out of the box. We have it architected with high availability because we use F5 load balancers, and everything about our architecture is highly available. I haven't personally used the management tools with IBM MQ, but we do have them, and our middleware folks leverage them. I can't really comment on them because I don't use them myself. I don't think the management tools help optimize message flows, and I'm not really aware of how they help in this. I'm not familiar with dynamic routing for IBM MQ.
reviewer963342 - PeerSpot reviewer
Senior Architect
Static and dynamic TCP have been the most useful
It's an ESB for both server-side as well as with eFTL, we are exposing messages to clients over web/mobile From the current direct socket architecture, we moved to an FTL based messaging layer which allowed us to not worry about individual functions but work on a single message/framework.…

Quotes from Members

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

Pros

"The best features of IBM MQ were stability and straightforward application functionality; it has vendor support, which was a significant advantage, and in case of any production issues, we definitely get vendor support, whereas with Kafka and others, we have to rely on open community and our research."
"The reliability is a benefit."
"One of the most important features is data persistence."
"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."
"My application may not always be running, yet even if it is off, whenever I stick on my applications, I get all the messages that I'm supposed to get."
"The most valuable features of this solution are its reliability, efficiency, and the capacity to bring value."
"It has improved the way my organization functions by just being less paper, and more efficient with timing; again, going back to the customer service, with clients being able to close their work orders within a shorter time frame."
"The message queue and the integration with any development platform/language, i.e., NET and Java, are the most valuable features."
"It's fast, we are pumping in nearly 5GB of data in a day, and it just works."
 

Cons

"You should be able to increase the message size. It should be dynamic. Each queue has a limitation of 5,000."
"More documentation would be good because some features are not deeply implemented."
"The only bad thing I could ever say about MQ is sometimes finding the right talent to administer it."
"I'm not sure that current version has event-driven mechanism requests that people go for. I would like the latest version to come with both type of event mechanisms: an email server and a POP server. If that is not there, then that would be a great addition."
"I haven’t given it a perfect rating because there's always room for improvement."
"Technical support is average. In terms of efficiency and response time, it's average, comparable to any other vendor."
"IBM MQ has limitations regarding scaling options. The licensing costs associated with scaling up and down were significant, which is why we are moving to Apache-based services such as Kafka."
"It would be nice if we could use the cluster facilities because we are doing active/passive configuration use."
"The UI is clunky for administration, eFTL at times is not fully stable and have observed a few crashes, and the content matcher could be improved for or conditions."
 

Pricing and Cost Advice

"IBM MQ is expensive and they charge based on the CPU."
"I think IBM needs to look at its pricing. The prices of IBM products should be simple. The old way of pricing should now be moving on to the cloud to be pay as you go, a plan-based kind of pricing."
"IBM MQ has a flexible license model based on the Processor Value Unit (PVU) and I recommend it."
"I think it's pretty reasonable, but I'm not so too sure of the current pricing strategy from IBM. We use many bundled services, and most often, we go through a service provided by some other third-party implementation. So, I can't really give an honest opinion about that."
"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."
"The price of IBM MQ could improve by being less expensive."
"To implement such an IBM solution, a company has to pay a lot in term of licensing and consultancy. A pricing model might be a better option."
"If one is cheap and ten is expensive, I rate the tool's price a seven. The product is expensive."
Information not available
report
Use our free recommendation engine to learn which Message Oriented Middleware (MOM) solutions are best for your needs.
902,417 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Manufacturing Company
9%
Construction Company
8%
Computer Software Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business20
Midsize Enterprise19
Large Enterprise147
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...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

WebSphere MQ
No data available
 

Overview

 

Sample Customers

Deutsche Bahn, Bon-Ton, WestJet, ARBURG, Northern Territory Government, Tata Steel Europe, Sharp Corporation
Information Not Available
Find out what your peers are saying about IBM, Solace, TIBCO and others in Message Oriented Middleware (MOM). Updated: May 2026.
902,417 professionals have used our research since 2012.