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
14th
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
4th
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 September 2026, in the Streaming Analytics category, the mindshare of Amazon MSK is 3.9%, down from 6.0% compared to the previous year. The mindshare of Apache Flink is 7.0%, down from 14.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Flink7.0%
Amazon MSK3.9%
Other89.1%
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

"It offers good stability."
"The scalability and usability are quite remarkable."
"It provides installations, scaling, and other functionalities straight out of the box."
"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."
"It is a stable product."
"MSK has a private network that's an out-of-box feature."
"The most valuable feature of Amazon MSK is the integration."
"Amazon MSK's scalability is very good."
"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."
"The top feature of Apache Flink is its low latency for fast, real-time data. Another great feature is the real-time indicators and alerts which make a big difference when it comes to data processing and analysis."
"The event processing function is the most useful or the most used function. The filter function and the mapping function are also very useful because we have a lot of data to transform. For example, we store a lot of information about a person, and when we want to retrieve this person's details, we need all the details. In the map function, we can actually map all persons based on their age group. That's why the mapping function is very useful. We can really get a lot of events, and then we keep on doing what we need to do."
"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."
"What I appreciate best about Apache Flink is that it's open source and geared towards a distributed stream processing framework."
"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."
"We value this solution's intricate system because it comes with a state inside the mechanism and product, allowing us to process batch data, stream to real-time and build pipelines, and we do not need to process data from the beginning when we pause as we can continue from the same point where we stopped, helping us save time as 95% of our pipelines will now be on Amazon and we'll save money by saving time."
 

Cons

"It would be really helpful if Amazon MSK could provide a single installation that covers all the servers."
"MSK should be easier to integrate with other solutions. It should be more flexible, integration-wise."
"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."
"In my opinion, there are areas in Amazon MSK that could be improved, particularly in terms of configuration. Initially setting it up and getting it connected was quite challenging. The naming conventions for policies were updated by AWS, and some were undocumented, leading to confusion with outdated materials. It took us weeks of trial and error before discovering new methods through hidden tutorials and official documentation."
"One of the reasons why we prefer Kafka is because the support is a little bit difficult to manage with Amazon MSK."
"Amazon MSK could improve on the features they offer. They are still lagging behind Confluence."
"The configuration seems a little complex and the documentation on the product is not available."
"The cost of using Amazon MSK is high, which is a significant disadvantage, as the increase in cloud costs by 50% to 60% does not justify the savings."
"One way to improve Flink would be to enhance integration between different ecosystems."
"There is room for improvement in the initial setup process."
"In a future release, they could improve on making the error descriptions more clear."
"Apache Flink should improve its data capability and data migration."
"Flink has become a lot more stable but the machine learning library is still not very flexible."
"Amazon's CloudFormation templates don't allow for direct deployment in the private subnet."
"Apache Flink is very powerful, but it can be challenging for beginners because it requires prior experience with similar tools and technologies, such as Kafka and batch processing."
"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."
 

Pricing and Cost Advice

"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 price of Amazon MSK is less than some competitor solutions, such as Confluence."
"This is an open-source platform that can be used free of charge."
"It's an open source."
"It's an open-source solution."
"Apache Flink is open source so we pay no licensing for the use of the software."
"The solution is open-source, which is free."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
913,806 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
16%
Manufacturing Company
10%
Comms Service Provider
9%
Construction Company
9%
Financial Services Firm
17%
Retailer
14%
Computer Software Company
8%
Manufacturing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise7
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.
913,806 professionals have used our research since 2012.