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

Amazon Kinesis vs Spring Cloud Data Flow 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 Kinesis
Ranking in Streaming Analytics
2nd
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
29
Ranking in other categories
No ranking in other categories
Spring Cloud Data Flow
Ranking in Streaming Analytics
10th
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Data Integration (22nd)
 

Mindshare comparison

As of March 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 5.2%, down from 9.0% compared to the previous year. The mindshare of Spring Cloud Data Flow is 3.5%, down from 4.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis5.2%
Spring Cloud Data Flow3.5%
Other91.3%
Streaming Analytics
 

Featured Reviews

CD
AWS Cloud Architect at a healthcare company with 10,001+ employees
Real-time streaming and seamless integration enhance workloads with room for competitive pricing improvements
Amazon Kinesis is easy to get started with, provides good documentation, and has a multilang daemon interface that makes it programming-language agnostic. The throughput is convenient for processing volumes out of the box and does not require complex configurations. It also provides auto-scaling with different partition keys into various shards. Lambda's scalability, seamless integration with other AWS services, and support for multiple programming languages are very beneficial.
NitinGoyal - PeerSpot reviewer
Engineering Lead at Naukri.com
Has a plug-and-play model and provides good robustness and scalability
The solution's community support could be improved. I don't know why the Spring Cloud Data Flow community is not very strong. Community support is very limited whenever you face any problem or are stuck somewhere. I'm not sure whether it has improved in the last six months because this pipeline was set up almost two years ago. I struggled with that a lot. For example, there was limited support whenever I got an exception and sought help from Stack Overflow or different forums. Interacting with Kubernetes needs a few certificates. You need to define all the certificates within your application. With the help of those certificates, your Java application or Spring Cloud Data Flow can interact with Kubernetes. I faced a lot of hurdles while placing those certificates. Despite following the official documentation to define all the replicas, readiness, and liveliness probes within the Spring Cloud Data Flow application, it was not working. So, I had to troubleshoot while digging in and debugging the internals of Spring Cloud Data Flow at that time. It was just a configuration mismatch, and I was doing nothing weird. There was a small spelling difference between how Spring Cloud Data Flow was expecting it and how I passed it. I was just following the official documentation.

Quotes from Members

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

Pros

"The product's initial setup phase is not difficult because we are using the tool on the cloud."
"There is no problem with the tool's stability."
"Its scalability is very high. There is no maintenance and there is no throughput latency. I think data scalability is high, too. You can ingest gigabytes of data within seconds or milliseconds."
"Amazon Kinesis has improved our ROI."
"I have worked in companies that build tools in-house. They face scaling challenges."
"Everything is hosted and simple."
"The solution has the capacity to store the data anywhere from one day to a week and provides limitless storage for us."
"One of the best features of Amazon Kinesis is the multi-partition."
"The most valuable features of Spring Cloud Data Flow are the simple programming model, integration, dependency Injection, and ability to do any injection. Additionally, auto-configuration is another important feature because we don't have to configure the database and or set up the boilerplate in the database in every project. The composability is good, we can create small workloads and compose them in any way we like."
"The dashboards in Spring Cloud Dataflow are quite valuable."
"The solution's most valuable feature is that it allows us to use different batch data sources, retrieve the data, and then do the data processing, after which we can convert and store it in the target."
"There are a lot of options in Spring Cloud. It's flexible in terms of how we can use it. It's a full infrastructure."
"The most valuable feature is real-time streaming."
"The ease of deployment on Kubernetes, the seamless integration for orchestration of various pipelines, and the visual dashboard that simplifies operations even for non-specialists such as quality analysts."
"The product is very user-friendly."
"The best thing I like about Spring Cloud Data Flow is its plug-and-play model."
 

Cons

"I think the default settings are far too low."
"Could include features that make it easier to scale."
"In general, the pain point for us was that once the data gets into Kinesis there is no way for us to understand what's happening because Kinesis divides everything into shards. So if we wanted to understand what's happening with a particular shard, whether it is published or not, we could not. Even with the logs, if we want to have some kind of logging it is in the shard."
"Amazon Kinesis involved a more complex setup and configuration than Azure Event Hub."
"The price is not much cheaper. So, there is room for improvement in the pricing."
"One thing that would be nice would be a policy for increasing the number of Kinesis streams because that's the one thing that's constant. You can change it in real time, but somebody has to change it, or you have to set some kind of meter. So, auto-scaling of adding and removing streams would be nice."
"Lacks first in, first out queuing."
"The tool should focus on having an alert system rather than having to use a third-party solution."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"The solution's community support could be improved."
"Spring Cloud Data Flow could improve the user interface. We can drag and drop in the application for the configuration and settings, and deploy it right from the UI, without having to run a CI/CD pipeline. However, that does not work with Kubernetes, it only works when we are working with jars as the Spring Cloud Data Flow applications."
"Spring Cloud Data Flow is not an easy-to-use tool, so improvements are required."
"Some of the features, like the monitoring tools, are not very mature and are still evolving."
"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."
"I would improve the dashboard features as they are not very user-friendly."
"There were instances of deployment pipelines getting stuck, and the dashboard not always accurately showing the application status, requiring manual intervention such as rerunning applications or refreshing the dashboard."
 

Pricing and Cost Advice

"The tool's entry price is cheap. However, pricing increases with data volume."
"In general, cloud services are very convenient to use, even if we have to pay a bit more, as we know what we are paying for and can focus on other tasks."
"Amazon Kinesis is an expensive solution."
"I think for us, with Amazon Kinesis, if we have to set up our own Kafka or cluster, it will be very time-consuming. If one considers the aforementioned aspect, Amazon Kinesis is a cheap tool."
"The pricing depends on the use cases and the level of usage. If you wanted to use Kinesis for different use cases, there's definitely a cheaper base cost involved. However, it's not entirely cheap, as different use cases might require different levels of Kinesis usage."
"It was actually a fairly high volume we were spending. We were spending about 150 a month."
"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."
"Amazon Kinesis pricing is sometimes reasonable and sometimes could be better, depending on the planning, so it's a five out of ten for me."
"This is an open-source product that can be used free of charge."
"The solution provides value for money, and we are currently using its community edition."
"If you want support from Spring Cloud Data Flow there is a fee. The Spring Framework is open-source and this is a free solution."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
884,797 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Financial Services Firm
14%
Manufacturing Company
7%
Educational Organization
5%
Financial Services Firm
18%
Computer Software Company
13%
Retailer
8%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise10
Large Enterprise9
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise1
Large Enterprise5
 

Questions from the Community

What do you like most about Amazon Kinesis?
Amazon Kinesis's main purpose is to provide near real-time data streaming at a consistent 2Mbps rate, which is really impressive.
What is your experience regarding pricing and costs for Amazon Kinesis?
Amazon Kinesis and Lambda pricing is competitive, but we noticed that scaling and large volumes could potentially increase costs significantly.
What needs improvement with Amazon Kinesis?
We are contemplating moving away from Amazon Kinesis primarily because of the cost. It is very useful, but if we write our own analytics and data processing pipeline, it would be much cheaper for u...
What needs improvement with Spring Cloud Data Flow?
There were instances of deployment pipelines getting stuck, and the dashboard not always accurately showing the application status, requiring manual intervention such as rerunning applications or r...
What is your primary use case for Spring Cloud Data Flow?
We had a project for content management, which involved multiple applications each handling content ingestion, transformation, enrichment, and storage for different customers independently. We want...
What advice do you have for others considering Spring Cloud Data Flow?
I would definitely recommend Spring Cloud Data Flow. It requires minimal additional effort or time to understand how it works, and even non-specialists can use it effectively with its friendly docu...
 

Also Known As

Amazon AWS Kinesis, AWS Kinesis, Kinesis
No data available
 

Overview

 

Sample Customers

Zillow, Netflix, Sonos
Information Not Available
Find out what your peers are saying about Amazon Kinesis vs. Spring Cloud Data Flow and other solutions. Updated: March 2026.
884,797 professionals have used our research since 2012.