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

Amazon Kinesis vs Spring Cloud Data Flow 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 Kinesis
Ranking in Streaming Analytics
8th
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
17th
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Data Integration (33rd)
 

Mindshare comparison

As of November 2026, in the Streaming Analytics category, the mindshare of Amazon Kinesis is 3.9%, down from 6.4% compared to the previous year. The mindshare of Spring Cloud Data Flow is 2.6%, down from 4.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Streaming Analytics Mindshare Distribution
ProductMindshare (%)
Amazon Kinesis3.9%
Spring Cloud Data Flow2.6%
Other93.5%
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

"Kinesis replaced a whole tier of servers, so we didn't need to have a server to catch the data and then send the data somewhere else, because Kinesis was the input port for very large amounts of data."
"We have seen a return on our investment with Amazon Kinesis, as we are able to process data without any issue and it is our solution for ingesting data in other databases, such as Snowflake."
"Setting Amazon Kinesis up is quick and easy; it only takes a few minutes to configure the necessary settings and start using it."
"Amazon Kinesis is easy to get started with, provides good documentation, and has a multilang daemon interface that makes it programming-language agnostic."
"The scalability is pretty good, as one can have any number of nodes spawned or replicated on the primary so that any load can be handled, perhaps a few terabytes with ease in around 15 seconds."
"The most valuable feature is that it has a pretty robust way of capturing things."
"We have been able to drop our costs for ingesting data by about 60 to 70%."
"What turns out to be most valuable is its integration with Lambda functions because you can process the data as it comes in. As soon as data comes, you'll fire a Lambda function to process a trench of data."
"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."
"The most valuable feature is real-time streaming."
"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 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."
"Overall, Spring Cloud Data Flow is a really good solution and a lot cheaper than a lot of infrastructure provided by big companies like Google or Amazon."
"This product will assist us in saving costs in many ways: No longer need to continue paying high fees for proprietary software, reduce the number of software engineers needed to support the product, and achieve faster time to market by using this product for our middleware."
"The dashboards in Spring Cloud Dataflow are quite valuable."
 

Cons

"Kinesis is good for Amazon Cloud but not as suitable for other cloud vendors."
"The services which are described in the documentation could use some visual presentation because for someone who is new to the solution the documentation is not easy to follow or beginner friendly and can leave a person feeling helpless."
"When we had some of those slow downs, we used AWS support and I can't say that we had a great experience and they resolved the issues, but they looked into some of the flow downs and ultimately we just decided there was nothing we could do."
"Amazon Kinesis could improve its pricing to be more competitive, especially for large volumes."
"There could be valid data in Kinesis that is not being processed, which affects stability. Although it rarely happens, this issue has been observed in many deployments, making it not completely stable."
"AI processing or cleaning up data would be nice since I don't think it is a feature in Amazon Kinesis right now."
"Snapshot from the the from the the stream of the data analytic I have already on the cloud, do a snapshot to not to make great or to get the data out size of the web service. But to stop the process and restart a few weeks later when I have more data or more available of the client teams."
"There are certain shortcomings in the machine learning capacity offered by the product, making it an area where improvements are required."
"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."
"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."
"The visual user interface could use some help; it needs improvement."
"The documentation on offer is not that good."
"The solution's community support could be improved."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"I would improve the dashboard features as they are not very user-friendly."
"Some of the features, like the monitoring tools, are not very mature and are still evolving."
 

Pricing and Cost Advice

"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."
"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."
"The tool's pricing is cheap."
"The product falls on a bit of an expensive side."
"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."
"The fee is based on the number of hours the service is running."
"Amazon Kinesis is an expensive solution."
"The tool's entry price is cheap. However, pricing increases with data volume."
"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."
"This is an open-source product that can be used free of charge."
report
Use our free recommendation engine to learn which Streaming Analytics solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
9%
Outsourcing Company
7%
University
7%
Financial Services Firm
15%
Outsourcing Company
9%
Computer Software Company
9%
Comms Service Provider
7%
 

Company Size

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

Questions from the Community

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 is your primary use case for Amazon Kinesis?
We use Amazon Kinesis for stream processing. We get events from on-premise devices to the cloud. We get many device events and we have to process these events that are coming from the devices. To p...
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: September 2026.
920,769 professionals have used our research since 2012.