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

Apache Flink vs SAS Event Stream Processing comparison

 

Comparison Buyer's Guide

Executive Summary

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
SAS Event Stream Processing
Ranking in Streaming Analytics
29th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Streaming Analytics category, the mindshare of Apache Flink is 7.5%, down from 14.4% compared to the previous year. The mindshare of SAS Event Stream Processing is 1.1%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Flink7.5%
SAS Event Stream Processing1.1%
Other91.4%
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.
Roi Jason Buela - PeerSpot reviewer
Lead Technical Consultant at Thakral One
A solution with useful windowing features and great for operations and marketing
The persistence could be better. Although ESP is designed for in-memory processing, it would be better if the solution is enhanced or improved on the persistence of the data that is kept in the memory. For example, if one server goes down and the information is stored in the memory, it is lost. Therefore, the persistence needs to be improved so that if there are more cases where the server is down, the information and data can still be intact.

Quotes from Members

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

Pros

"Apache Flink allows you to reduce latency and process data in real-time, making it ideal for such scenarios."
"The documentation is very good."
"The end-to-end latency was drastically reduced, and our capability of handling high throughput has increased by using Flink."
"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."
"Flink moved on to becoming a standard technology for location platform."
"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 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 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. We use Apache Flink to control our clients' installations."
"The solution is beneficial on an enterprise level."
 

Cons

"There is room for improvement in the initial setup process."
"PyFlink is not as fully featured as Python itself, so there are some limitations to what you can do with it."
"Failure is another area where it is a bit rigid or not that flexible."
"One way to improve Flink would be to enhance integration between different ecosystems."
"The solution could be more user-friendly."
"I am using the Python API and I have found the solution to be underdeveloped compared to others. There needs to be better integration with notebooks to allow for more practical development."
"There are more libraries that are missing and also maybe more capabilities for machine learning."
"We have a machine learning team that works with Python, but Apache Flink does not have full support for the language."
"The persistence could be better."
 

Pricing and Cost Advice

"It's an open-source solution."
"This is an open-source platform that can be used free of charge."
"Apache Flink is open source so we pay no licensing for the use of the software."
"It's an open source."
"The solution is open-source, which is free."
Information not available
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Retailer
13%
Computer Software Company
8%
Comms Service Provider
5%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise3
Large Enterprise12
No data available
 

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...
Ask a question
Earn 20 points
 

Also Known As

Flink
No data available
 

Overview

 

Sample Customers

LogRhythm, Inc., Inter-American Development Bank, Scientific Technologies Corporation, LotLinx, Inc., Benevity, Inc.
Honda, HSBC, Lufthansa, Nestle, 89Degrees.
Find out what your peers are saying about Databricks, Microsoft, Apache and others in Streaming Analytics. Updated: July 2026.
908,800 professionals have used our research since 2012.