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

Apache Flink vs Software AG Apama 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
Software AG Apama
Ranking in Streaming Analytics
25th
Average Rating
7.0
Reviews Sentiment
6.6
Number of Reviews
1
Ranking in other categories
Complex Event Processing (CEP) (3rd)
 

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 Software AG Apama is 1.6%, up from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Apache Flink7.5%
Software AG Apama1.6%
Other90.9%
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.
SP
Sr Executive Accounts at a computer software company with 1,001-5,000 employees
A tool to send out promotional notifications that need to improve areas, like deployment and maintenance
Software AG Apama should support offline scenarios as it may not always be possible to stay connected with the cloud. The solution should be deployed on an on-premises model, and it should be able to handle offline scenarios. If certain rules are set in Software AG Apama, then it should be able to execute them without being connected to an open internet source. With Software AG Apama, one may face challenges since it is difficult to find people with the right skill set to operate it. The solution also makes use of a proprietary programming language that is hard to trace in the market. It is better to go with the new options available in the market since Software AG Apama has become an old product. The ease of development and maintenance should be enhanced, but it is difficult due to the use of the proprietary programming language in the product.

Quotes from Members

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

Pros

"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."
"This is truly a real-time solution."
"What I appreciate best about Apache Flink is that it's open source and geared towards a distributed stream processing framework."
"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."
"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 offers a range of powerful configurations and experiences for development teams. Its strength lies in its development experience and capabilities."
"The end-to-end latency was drastically reduced, and our capability of handling high throughput has increased by using Flink."
"It is user-friendly and the reporting is good."
"The most valuable feature of the solution is the ability that it provides its users to handle different kinds of rules."
 

Cons

"Apache Flink's documentation should be available in more languages."
"There is room for improvement in the initial setup process."
"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."
"The solution could be more user-friendly."
"One way to improve Flink would be to enhance integration between different ecosystems."
"Flink has become a lot more stable but the machine learning library is still not very flexible."
"The state maintains checkpoints and they use RocksDB or S3. They are good but sometimes the performance is affected when you use RocksDB for checkpointing."
"There is a learning curve. It takes time to learn."
"The ease of development and maintenance should be enhanced, but it is difficult due to the use of the proprietary programming language in the product."
 

Pricing and Cost Advice

"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."
"This is an open-source platform that can be used free of charge."
"It's an open source."
"A commercial license is required to operate Software AG Apama."
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
Progress Apama
 

Overview

 

Sample Customers

LogRhythm, Inc., Inter-American Development Bank, Scientific Technologies Corporation, LotLinx, Inc., Benevity, Inc.
Okasan Online Securities
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.