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

Amazon MSK vs Apache Flink 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

Amazon MSK
Ranking in Streaming Analytics
13th
Average Rating
7.2
Reviews Sentiment
6.5
Number of Reviews
14
Ranking in other categories
No ranking in other categories
Apache Flink
Ranking in Streaming Analytics
3rd
Average Rating
7.8
Reviews Sentiment
6.7
Number of Reviews
19
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Streaming Analytics category, the mindshare of Amazon MSK is 3.8%, down from 5.5% compared to the previous year. The mindshare of Apache Flink is 6.7%, down from 14.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Flink6.7%
Amazon MSK3.8%
Other89.5%
Streaming Analytics
 

Featured Reviews

SYED SHAAZ - PeerSpot reviewer
Co-Founder & CTO at Photios AI
Improved data streaming and integration challenges prompt search for alternatives
The integration capabilities of Amazon MSK are not very flexible. If you have your own self-managed Kafka, that helps significantly because you can set up configurations. We are considering self-managed Kafka since our product is only one year old. The Kafka integrations are fine, but the configurations are an issue. The only issue with Amazon MSK that we are facing is the configurations. There are preset configurations and limited configurations that we can set for our unique use case. The product could improve by allowing us to set different configurations. I would also like to see Amazon MSK improve in the area of connectors. We are considering Confluent Cloud because they have many more connectors. They have KSQL DB and governance features. It is slightly costlier, but Confluent offers more flexibility with their connectors.
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.

Quotes from Members

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

Pros

"The solution's technical support was helpful."
"It offers good stability."
"It provides installations, scaling, and other functionalities straight out of the box."
"MSK has already launched ZooKeeper and the cluster, and this is included as an out-of-the-box feature, which is very convenient."
"MSK has a private network that's an out-of-box feature."
"Amazon MSK has contributed positively to our real-time analytics capabilities because Fortis's dashboards have dashboard health that needs to be maintained, user logs that need to be maintained, and usage tracking."
"Amazon MSK has significantly improved our organization by building seamless integration between systems."
"The scalability and usability are quite remarkable."
"Apache Flink allows you to reduce latency and process data in real-time, making it ideal for such scenarios."
"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."
"The documentation is very good."
"The setup was not too difficult."
"It is user-friendly and the reporting is good."
"The end-to-end latency was drastically reduced, and our capability of handling high throughput has increased by using Flink."
"The ease of usage, even for complex tasks, stands out."
"Flink moved on to becoming a standard technology for location platform."
 

Cons

"Horizontal scale-out is actually not easy, making it an area where improvements are required."
"We need to create connectors in Amazon MSK, but there are no default connectors in AWS for that purpose."
"The downside of Amazon MSK is that when I needed to make a small change in the MSK configuration, it wasn't possible. I had to remove and drop all the clusters and recreate them again, which is complicated in a production environment."
"It would be really helpful if Amazon MSK could provide a single installation that covers all the servers."
"The only issue with Amazon MSK that we are facing is the configurations. There are preset configurations and limited configurations that we can set for our unique use case."
"One of the reasons why we prefer Kafka is because the support is a little bit difficult to manage with Amazon MSK."
"MSK should be easier to integrate with other solutions. It should be more flexible, integration-wise."
"The product's schema support needs enhancement. It will help enhance integration with many kinds of languages of programming languages, especially for environments using languages like .NET."
"Apache Flink's documentation should be available in more languages."
"We have a machine learning team that works with Python, but Apache Flink does not have full support for the language."
"Failure is another area where it is a bit rigid or not that flexible."
"Flink has become a lot more stable but the machine learning library is still not very flexible."
"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."
"Apache should provide more examples and sample code related to streaming to help me better adapt and utilize the tool."
"In a future release, they could improve on making the error descriptions more clear."
"Amazon's CloudFormation templates don't allow for direct deployment in the private subnet."
 

Pricing and Cost Advice

"The price of Amazon MSK is less than some competitor solutions, such as Confluence."
"The platform has better pricing than one of its competitors."
"When you create a complete enterprise-driven architecture that is deployable on an enterprise scale, I would say that the prices of Amazon MSK and Confluent Platform become comparable."
"The solution is open-source, which is free."
"It's an open source."
"This is an open-source platform that can be used free of charge."
"It's an open-source solution."
"Apache Flink is open source so we pay no licensing for the use of the software."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
921,028 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Manufacturing Company
12%
Construction Company
9%
Comms Service Provider
9%
Financial Services Firm
16%
Retailer
15%
Computer Software Company
7%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise8
Large Enterprise5
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise3
Large Enterprise12
 

Questions from the Community

What needs improvement with Amazon MSK?
The integration capabilities of Amazon MSK are not very flexible. If you have your own self-managed Kafka, that helps significantly because you can set up configurations. We are considering self-ma...
What is your primary use case for Amazon MSK?
We are recently working with Amazon MSK at Fortis, where we have multiple dashboards in our revenue intelligence platform. We are streaming data from different apps into those dashboards. The data ...
What advice do you have for others considering Amazon MSK?
We are working with Amazon MSK product, Managed Streaming for Apache Kafka. The main benefits I have seen from using Amazon MSK is that as a B2B enterprise client, we have many SLAs to fulfill. Tra...
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...
 

Also Known As

Amazon Managed Streaming for Apache Kafka
Flink
 

Overview

 

Sample Customers

Expedia, Intuit, Royal Dutch Shell, Brooks Brothers
LogRhythm, Inc., Inter-American Development Bank, Scientific Technologies Corporation, LotLinx, Inc., Benevity, Inc.
Find out what your peers are saying about Amazon MSK vs. Apache Flink and other solutions. Updated: September 2026.
921,028 professionals have used our research since 2012.