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

Amazon MSK vs Apache Flink comparison

 

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
7th
Average Rating
7.4
Reviews Sentiment
7.1
Number of Reviews
11
Ranking in other categories
No ranking in other categories
Apache Flink
Ranking in Streaming Analytics
5th
Average Rating
7.8
Reviews Sentiment
6.9
Number of Reviews
18
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the Streaming Analytics category, the mindshare of Amazon MSK is 7.3%, down from 9.6% compared to the previous year. The mindshare of Apache Flink is 13.8%, up from 9.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics
 

Featured Reviews

FNU AKSHANSH - PeerSpot reviewer
Streamlines our processes, and we don't need to configure any VPCs; it's automatic
We don't have many use cases involving ingesting large amounts of data and scaling up and down. We have a clear understanding of our data volume, which remains relatively constant throughout the week. While we're aware of other features Amazon MSK offers, we feel confident in our current setup. If our requirements change significantly in the future, we'll reassess our needs and consider adopting Amazon MSK.
Aswini Atibudhi - PeerSpot reviewer
Enables robust real-time data processing but documentation needs refinement
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. It's essential to have a clear foundation; hence, it can be tough for beginners. However, once they grasp the concepts and have examples or references, it becomes easier. Intermediate users who are integrating with Kafka or other sources may find it smoother. After setting up and understanding the concepts, it becomes quite stable and scalable, allowing for customization of jobs. Every ( /products/every-reviews ) software, including Apache Flink, has room for improvement as it evolves. One key area for enhancement is user-friendliness and the developer experience; improving documentation and API specifications is essential, as they can currently be verbose and complex. Debugging ( /categories/debugging ) and local testing pose challenges for newcomers, particularly when learning about concepts such as time semantics and state handling. Although the APIs exist, they aren't intuitive enough. We also need to simplify operational procedures, such as developing tools and tuning Flink clusters, as these processes can be quite complex. Additionally, implementing one-click rollback for failures and improving state management during dynamic scaling while retaining the last states is vital, as the current large states pose scaling challenges.

Quotes from Members

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

Pros

"Amazon MSK's separation of concerns and ease of creating and deploying new features are highly valuable. It just requires to assign them to the topic, and then anyone who needs to consume these messages can do so directly from Amazon MSK. This separation of concerns makes it very convenient, especially for new feature development, as developers can easily access the messages they need without having to deal with complex server communications or protocol setups."
"The most valuable feature of Amazon MSK is the integration."
"It offers good stability."
"Amazon MSK has good integration because our team has been undergoing significant changes. Coupling it with MSK within AWS is helpful. We don't have to set up additionals or monitor external environments. This"
"It is a stable product."
"MSK has a private network that's an out-of-box feature."
"It provides installations, scaling, and other functionalities straight out of the box."
"The scalability and usability are quite remarkable."
"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."
"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 ease of usage, even for complex tasks, stands out."
"It is user-friendly and the reporting is good."
"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."
"Apache Flink's best feature is its data streaming tool."
"The setup was not too difficult."
 

Cons

"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."
"It does not autoscale. Because if you do keep it manually when you add a note to the cluster and then you register it, then it is scalable, but the fact that you have to go and do it, I think, makes it, again, a bit of some operational overhead when managing the cluster."
"It would be really helpful if Amazon MSK could provide a single installation that covers all the servers."
"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."
"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."
"The configuration seems a little complex and the documentation on the product is not available."
"Horizontal scale-out is actually not easy, making it an area where improvements are required."
"In terms of improvement, there should be better reporting. You can integrate with reporting solutions but Flink doesn't offer it themselves."
"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."
"There is a learning curve. It takes time to learn."
"One way to improve Flink would be to enhance integration between different ecosystems. For example, there could be more integration with other big data vendors and platforms similar in scope to how Apache Flink works with Cloudera. Apache Flink is a part of the same ecosystem as Cloudera, and for batch processing it's actually very useful but for real-time processing there could be more development with regards to the big data capabilities amongst the various ecosystems out there."
"Apache should provide more examples and sample code related to streaming to help me better adapt and utilize the tool."
"There are more libraries that are missing and also maybe more capabilities for machine learning."
"PyFlink is not as fully featured as Python itself, so there are some limitations to what you can do with it."
"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."
 

Pricing and Cost Advice

"The platform has better pricing than one of its competitors."
"The price of Amazon MSK is less than some competitor solutions, such as Confluence."
"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."
"It's an open source."
"This is an open-source platform that can be used free of charge."
"The solution is open-source, which is free."
"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.
851,371 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
23%
Computer Software Company
18%
Manufacturing Company
6%
Healthcare Company
4%
Financial Services Firm
24%
Computer Software Company
15%
Manufacturing Company
7%
Retailer
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Amazon MSK?
Amazon MSK has significantly improved our organization by building seamless integration between systems.
What needs improvement with Amazon MSK?
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. There were no other notable issues.
What is your primary use case for Amazon MSK?
We used Amazon MSK to manage high-volume third-party data entering our system. It served as a buffer when our system was unable to consume data at high speeds in real-time. The data initially went ...
What do you like most about Apache Flink?
The product helps us to create both simple and complex data processing tasks. Over time, it has facilitated integration and navigation across multiple data sources tailored to each client's needs. ...
What is your experience regarding pricing and costs for Apache Flink?
The solution is expensive. I rate the product’s pricing a nine out of ten, where one is cheap and ten is expensive.
What needs improvement with Apache Flink?
Apache should provide more examples and sample code related to streaming to help me better adapt and utilize the tool. There is a need for increased awareness and education, especially around best ...
 

Comparisons

 

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: April 2025.
851,371 professionals have used our research since 2012.