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

Apache Flink vs Apache Kafka comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 17, 2024

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

Apache Flink
Ranking in Streaming Analytics
4th
Average Rating
7.8
Reviews Sentiment
6.7
Number of Reviews
19
Ranking in other categories
No ranking in other categories
Apache Kafka
Ranking in Streaming Analytics
3rd
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
92
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2026, in the Streaming Analytics category, the mindshare of Apache Flink is 6.9%, down from 14.6% compared to the previous year. The mindshare of Apache Kafka is 3.6%, up from 3.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Kafka3.6%
Apache Flink6.9%
Other89.5%
Streaming Analytics
 

Featured Reviews

Sanjay Srivastava - PeerSpot reviewer
Software Architect at IBM
Streaming workflows have improved data integration and support real-time pipelines across platforms
We are not using Apache Flink in its advanced window capabilities. We are using the Apache Flink job in Apache SeaTunnel, meaning we can write the code inside Apache SeaTunnel. Currently, we are moving; both solutions are there. We are doing it on-premises with the help of Kubernetes and OpenShift. The main reason why Apache Flink is better is that it has more functions, and being open source with easy code in Apache SeaTunnel helps us achieve that. Cost is a major issue. I would rate the stability of the product as an eight. For Apache Flink, the final point can be rated an eight. I can recommend Apache Flink to other users for streaming support, and I am recommending it. I would rate this review an eight overall.
Amandeep Pawar - PeerSpot reviewer
Engineer Technology at Iris Software Technologies Private Limited
Event-driven architecture has improved asynchronous communication and supports high throughput
We can improve the high throughput because there are some limitations. We could add something to improve Apache Kafka. Based on my daily usage and analysis, there is a complex setup and management, which is one area requiring improvement. Apache Kafka does not have built-in message delay or scheduling capabilities. Apache Kafka cannot natively schedule messages. Limited message prioritization is also an area requiring improvement. Ordering is limited to a single partition. Large messages affect performance. Apache Kafka is optimized for many small to medium-sized messages, but large payloads increase network usage, increase disk usage, and slow down producers and consumers. I rate Apache Kafka eight out of ten instead of ten out of ten because operating an Apache Kafka cluster requires expertise in partitioning, application monitoring, and capacity planning. Self-managed deployment can become complex as the cluster grows. Pro-managed Apache Kafka services significantly reduce the operational overhead.

Quotes from Members

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

Pros

"Apache Flink's best feature is its data streaming tool."
"Easy to deploy and manage."
"The main advantage is the turnaround time, which has been reduced drastically because of Apache Flink, and now everything is in almost real time with no waiting or lag of data in the application while machine resources are utilized much more efficiently."
"We are very happy with the product, and we have been able to achieve all of the use cases that we are expected to deliver for our customers."
"Apache Flink provides faster and low-cost investment for me; I find it to have low hardware requirements, and it's faster with low code, meaning it's easy to understand for moving the streaming data."
"Apache Flink is meant for low latency applications. You take one event opposite if you want to maintain a certain state. When another event comes and you want to associate those events together, in-memory state management was a key feature for us."
"Another feature is how Flink handles its radiuses. It has something called the checkpointing concept. You're dealing with billions and billions of requests, so your system is going to fail in large storage systems. Flink handles this by using the concept of checkpointing and savepointing, where they write the aggregated state into some separate storage. So in case of failure, you can basically recall from that state and come back."
"With Flink, it provides out-of-the-box checkpointing and state management. It helps us in that way. When Storm used to restart, sometimes we would lose messages. With Flink, it provides guaranteed message processing, which helped us. It also helped us with maintenance or restarts."
"Apache Kafka is scalable. It is easy to add brokers."
"When we're working with big data, we need a throughput computing panel, which is something that Kafka provides, and something we find extremely valuable."
"Apache Kafka is a good solution with many good features but for large deployments, I would choose IBM MQ over Kafka."
"There are numerous possibilities that can be explored. While it may be challenging to fully comprehend the potential advantages, one key aspect is the ability to establish a proper sequence of events rather than simply dealing with a jumbled group of occurrences. These events possess their own timestamps, even if they were not initially provided with one, and are arranged in a chronological order that allows for a clear understanding of the progression of the events."
"The solution can handle more speed and has horizontal scalability for both messaging, but more specifically stream processing and data enrichment."
"For example, when you want to send a message to inform all your clients about a new feature, you can publish that message to a single topic in Apache Kafka. This allows all clients subscribed to that topic to receive the message. On the other hand, if you need to send billing information to a specific customer, you can publish that message on a topic dedicated to that customer. This message can then be sent as an SMS to the customer, allowing them to view it on their mobile device."
"The most valuable feature is the speed at which the solution can be deployed."
"One of the best features which I have worked with is replay."
 

Cons

"Apache Flink should improve its data capability and data migration."
"The technical support from Apache is not good; support needs to be improved. I would rate them from one to ten as not good."
"In a future release, they could improve on making the error descriptions more clear."
"Apache should provide more examples and sample code related to streaming to help me better adapt and utilize the tool."
"In terms of stability with Flink, it is something that you have to deal with every time. Stability is the number one problem that we have seen with Flink, and it really depends on the kind of problem that you're trying to solve."
"Flink has become a lot more stable but the machine learning library is still not very flexible."
"We have a machine learning team that works with Python, but Apache Flink does not have full support for the language."
"In terms of improvement, there should be better reporting. You can integrate with reporting solutions but Flink doesn't offer it themselves."
"The manageability should be improved. There are lots of things we need to manage and it should have a function that enables us to manage them all cohesively."
"Apache Kafka can improve by providing a UI for monitoring."
"GUI for Kafka infrastructure monitoring and deployment"
"There is a lot of information available for the solution and it can be overwhelming to sort through."
"They need to have a proper portal to do everything because, at this moment, Kafka is lagging in this regard."
"Kafka does not provide control over the message queue, so we do not know whether we are experiencing lost or duplicate messages."
"There have been some challenges with monitoring Apache Kafka, as there are currently only a few production-grade solutions available, which are all under enterprise license and therefore not easily accessible. The speaker has not had access to any of these solutions and has instead relied on tools, such as Dynatrace, which do not provide sufficient insight into the Apache Kafka system. While there are other tools available, they do not offer the same level of real-time data as enterprise solutions."
"The only reason I give Kafka as product a low rating is because there are far superior and cheaper alternatives in cloud-based solutions, where we save money on manpower, electricity, servers, datacenters, networking, etc."
 

Pricing and Cost Advice

"It's an open-source solution."
"The solution is open-source, which is free."
"Apache Flink is open source so we pay no licensing for the use of the software."
"This is an open-source platform that can be used free of charge."
"It's an open source."
"Apache Kafka is an open-source solution."
"It's a bit cheaper compared to other Q applications."
"The price of the solution is low."
"It's a premium product, so it is not price-effective for us."
"Apache Kafka is an open-sourced solution. There are fees if you want the support, and I would recommend it for enterprises. There are annual subscriptions available."
"I was using the product's free version."
"Apache Kafka is open-source and can be used free of charge."
"Apache Kafka has an open-source pricing."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Retailer
14%
Computer Software Company
8%
Manufacturing Company
5%
Financial Services Firm
16%
Outsourcing Company
13%
Manufacturing Company
10%
Computer Software Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise3
Large Enterprise12
By reviewers
Company SizeCount
Small Business33
Midsize Enterprise20
Large Enterprise51
 

Questions from the Community

What needs improvement with Apache Flink?
Apache could improve Apache Flink by providing more functionality, as they need to fully support data integration. The connectors are still very few for Apache Flink. There is a lack of functionali...
What is your primary use case for Apache Flink?
I am working with Apache Flink, which is the tool we use for data integration. Apache Flink is for data, and we are working on the data integration project, not big data, using Apache Flink and Apa...
What advice do you have for others considering Apache Flink?
We are not using Apache Flink in its advanced window capabilities. We are using the Apache Flink job in Apache SeaTunnel, meaning we can write the code inside Apache SeaTunnel. Currently, we are mo...
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 is your experience regarding pricing and costs for Apache Kafka?
Based on my understanding for the setup and cost to set up Apache Kafka, I was not responsible for the pricing or licensing decisions. Apache Kafka itself is open source and free to use. Infrastruc...
What needs improvement with Apache Kafka?
We can improve the high throughput because there are some limitations. We could add something to improve Apache Kafka. Based on my daily usage and analysis, there is a complex setup and management,...
 

Also Known As

Flink
No data available
 

Overview

 

Sample Customers

LogRhythm, Inc., Inter-American Development Bank, Scientific Technologies Corporation, LotLinx, Inc., Benevity, Inc.
Uber, Netflix, Activision, Spotify, Slack, Pinterest
Find out what your peers are saying about Apache Flink vs. Apache Kafka and other solutions. Updated: September 2026.
915,341 professionals have used our research since 2012.