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

Apache Kafka vs IBM MQ comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 8, 2024
 

Categories and Ranking

Apache Kafka
Average Rating
8.2
Reviews Sentiment
7.0
Number of Reviews
84
Ranking in other categories
Streaming Analytics (7th)
IBM MQ
Average Rating
8.4
Reviews Sentiment
6.7
Number of Reviews
163
Ranking in other categories
Business Activity Monitoring (1st), Message Queue (MQ) Software (1st), Message Oriented Middleware (MOM) (1st)
 

Mindshare comparison

Apache Kafka and IBM MQ aren’t in the same category and serve different purposes. Apache Kafka is designed for Streaming Analytics and holds a mindshare of 0.3%, up 0.0% compared to last year.
IBM MQ, on the other hand, focuses on Message Queue (MQ) Software, holds 29.5% mindshare, up 26.6% since last year.
Streaming Analytics
Message Queue (MQ) Software
 

Q&A Highlights

NC
Sep 04, 2023
 

Featured Reviews

Eyob Alemu - PeerSpot reviewer
Significant cost savings with real-time processing and fast recovery
We use Kafka for a stage event-driven process from a process perspective. Our platform is an ID platform, so after registration data is received, it has to be stored from various registration locations. The process includes stages like quality checking, consistency, format, biometric data checking…
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.

Quotes from Members

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

Pros

"This is a system for email and other small devices. There has been a relay of transactions continuously over the last two years it has been in production."
"A great streaming platform."
"The most valuable feature of Apache Kafka is the clustering which is very easy to scale and we have multiple servers all over our platforms. It has been useful for stability and performance."
"As a software developer, I have found Apache Kafka's support to be the most valuable...The solution is easy to integrate with any of our systems."
"The most valuable feature is the support for a high volume of data."
"We get amazing throughput. We don't get any delay."
"It is a stable solution...A lot of my experience indicates that Apache Kafka is scalable."
"Deployment is speedy."
"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."
"I like the MQ's simplicity and rock-solid stability. I've never experienced a failure in two decades caused by the product itself. It has only failed due to human error."
"I haven't seen any severe issues related to it. Most of the time it's running. That is the advantage of IBM MQ."
"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."
"A stable and reliable software that offers good integration between different systems."
"Combined with IBM MQ, this product is our primary data store."
"The most valuable feature is that it's a very strong integration platform but it is quite a monolithic solution. It's got everything."
"Secure, safe, and very fast."
 

Cons

"Apache Kafka can improve by making the documentation more user-friendly. It would be beneficial if we could explain to customers in more detail how the solution operates but the documentation get highly technical quickly. For example, if they had a simple page where we can show the customers how it works without the need for the customer to have a computer science background."
"One of the things I am mostly looking for is that once the message is picked up from Kafka, it should not be visible or able to be consumed by other applications, or something along those lines. That feature is not present, but it is not a limitation or anything of the sort; rather, it is a desirable feature. The next release should include a feature that prevents messages from being consumed by other applications once they are picked up by Kafka."
"The third party is not very stable and sometimes you have problems with this component. There are some developments in newer versions and we're about to try them out, but I'm not sure if it closes the gap."
"I would like to see an improvement in authentication management."
"One complexity that I faced with the tool stems from the fact that since it is not kind of a stand-alone application, it won't integrate with native cloud, like AWS or Azure."
"Apache Kafka could improve data loss and compatibility with Spark."
"Kafka is a nightmare to administer."
"We struggled a bit with the built-in data transformations because it was a challenge to get them up and running the way we wanted."
"We need to have a better administration console and better monitoring features. Right now, they are not good and could be a lot better."
"I wanted to upgrade Windows Server. It's not that easy to move."
"The installation of product upgrades and patches is very difficult. It requires the use of the IBM Installation Manager (IM)."
"IBM could revamp the interface. The API is huge, but some developers find it limiting because of the cost. They tend to wrap the API course into the JMS, which means they're missing out on some good features. They should work a little bit on the API exposure."
"If they could have some front-end monitoring tool that could be easily available for the team to use, that could be great."
"The solution should offer a freeware version, free vouchers, or certifications for learning purposes and building knowledge base."
"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."
"Presenting and maybe having some different options for different user experiences based on the administrative duties that you have to do as an app manager or configure the server or security would be an improvement."
 

Pricing and Cost Advice

"Apache Kafka is free."
"I was using the product's free version."
"This is an open-source version."
"When starting to look at a distributed message system, look for a cloud solution first. It is an easier entry point than an on-premises hardware solution."
"The price for the enterprise version is quite high. For on-premise, there is an annual fee, which starts at 60,000 euros, but it is usually higher than 100,000 euros. The cost for a project including the subscription is usually between 100,000 to 200,000 euros. The cost also depends on the level of support. There are two different levels of support."
"The solution is open source."
"Licensing issues are not applicable. Apache licensing makes it simple with almost zero cost for the software itself."
"Running a Kafka cluster can be expensive, especially if you need to scale it up to handle large amounts of data."
"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."
"Use the new and lightweight version (Liberty) to lower licensing costs. It is also easier to upgrade/maintain."
"I think the pricing is reasonable, especially with IIB as a part of it."
"The problem with this product is that it's a little bit expensive."
"IBM MQ is an expensive solution compared to other solutions. However, if you pay less you will not receive the same experience or features."
"It's super expensive, so ask them if they can consolidate some other licensing costs. But, IBM is IBM, so I guess we'll pay for it."
"We have a special contract with IBM MQ that give us a certain price."
"IBM products, in general, have high licensing costs and support costs are too high."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Answers from the Community

NC
Sep 4, 2023
Sep 4, 2023
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 users. This tool has great scalability with high throughput and a very helpful supportive online community. However, Kafka does not provide control over the message queue, so it is difficult to know wheth...
2 out of 3 answers
Oct 31, 2021
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 users. This tool has great scalability with high throughput and a very helpful supportive online community. However, Kafka does not provide control over the message queue, so it is difficult to know whether messages are being delivered, lost, or duplicated. We would like to see more adapters for connecting to different systems made available. I think this would be a better product if the graphical user interface was easier. The manual calculations needed for this solution can be difficult. If the process was automated, it would be a much better product. IBM MQ has a very strong reputation and is very robust with great stability. This solution is easy to use, simple to configure, and integrates well with our enterprise ecosystem and protocols. IBM ensures message delivery. You can track and trace everything. If a message doesn’t arrive at its destination, it will go back to the queue; this ensures no message is ever lost. This is a huge selling point for us. IBM MQ does not handle huge volume very well, though. There are some limitations to the queues. If these limitations could be relaxed, it would be a better product for us. You have to license per application and installation, so scaling up can get very costly very quickly. Conclusion Apache Kafka is a cost-effective solution for high-volume, multi-source data collection. If you are in a high-growth trajectory and if total message accountability and tracking is not a huge issue for you, this solution may work well for you. IBM MQ is a licensed product and can be very expensive, it also does not scale easily, which can be very problematic. IBM MQ requires a definite skillset that not many people have, which can be an issue for some and it affects the fast responsive support of this solution.
GT
Sep 14, 2022
The choice depends on your use case.
 

Top Industries

By visitors reading reviews
Financial Services Firm
31%
Computer Software Company
13%
Manufacturing Company
6%
Retailer
5%
Financial Services Firm
38%
Computer Software Company
13%
Manufacturing Company
6%
Government
4%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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...
What do you like most about Apache Kafka?
Apache Kafka is an open-source solution that can be used for messaging or event processing.
What is your experience regarding pricing and costs for Apache Kafka?
We use Apache Kafka, which is open-source, so we don't have fees. I can't comment on ownership costs as I am not responsible for that domain.
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...
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 IBM MQ?
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.
 

Comparisons

 

Also Known As

No data available
WebSphere MQ
 

Learn More

 

Overview

 

Sample Customers

Uber, Netflix, Activision, Spotify, Slack, Pinterest
Deutsche Bahn, Bon-Ton, WestJet, ARBURG, Northern Territory Government, Tata Steel Europe, Sharp Corporation
Find out what your peers are saying about Apache Kafka vs. IBM MQ and other solutions. Updated: May 2024.
824,053 professionals have used our research since 2012.