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

Spring Cloud Data Flow vs StreamSets comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 19, 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

Spring Cloud Data Flow
Ranking in Data Integration
31st
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Streaming Analytics (16th)
StreamSets
Ranking in Data Integration
22nd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Data Integration category, the mindshare of Spring Cloud Data Flow is 1.0%, down from 1.1% compared to the previous year. The mindshare of StreamSets is 1.2%, down from 1.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration Mindshare Distribution
ProductMindshare (%)
StreamSets1.2%
Spring Cloud Data Flow1.0%
Other97.8%
Data Integration
 

Featured Reviews

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.
SS
Enterprise Solutions Architect at a energy/utilities company with 1,001-5,000 employees
Enables effective batch loading with visual interface and enterprise support
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infrastructure. I had to switch to a new EC2 box, even though the processor was not fully utilized. It would be beneficial if StreamSets addressed any potential memory leak issues to prevent unnecessary upgrades. Additionally, it would be a great enhancement if StreamSets could produce a lineage graph to visualize how the data has passed through the system.

Quotes from Members

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

Pros

"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."
"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."
"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."
"StreamSets’ data drift resilience has reduced the time it takes us to fix data drift breakages. For example, in our previous Hadoop scenario, when we were creating the Sqoop-based processes to move data from source to destinations, we were getting the job done. That took approximately an hour to an hour and a half when we did it with Hadoop. However, with the StreamSets, since it works on a data collector-based mechanism, it completes the same process in 15 minutes of time. Therefore, it has saved us around 45 minutes per data pipeline or table that we migrate. Thus, it reduced the data transfer, including the drift part, by 45 minutes."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"The most valuable would be the GUI platform that I saw. I first saw it at a special session that StreamSets provided towards the end of the summer. I saw the way you set it up and how you have different processes going on with your data. The design experience seemed to be pretty straightforward to me in terms of how you drag and drop these nodes and connect them with arrows."
"The entire user interface is very simple and the simplicity of creating pipelines is something that I like very much about it. The design experience is very smooth."
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"StreamSets data drift feature gives us an alert upfront so we know that the data can be ingested. Whatever the schema or data type changes, it lands automatically into the data lake without any intervention from us, but then that information is crucial to fix for downstream pipelines, which process the data into models, like Tableau and Power BI models. This is actually very useful for us. We are already seeing benefits. Our pipelines used to break when there were data drift changes, then we needed to spend about a week fixing it. Right now, we are saving one to two weeks. Though, it depends on the complexity of the pipeline, we are definitely seeing a lot of time being saved."
"Also, the intuitive canvas for designing all the streams in the pipeline, along with the simplicity of the entire product are very big pluses for me. The software is very simple and straightforward. That is something that is needed right now."
"The Ease of configuration for pipes is amazing. It has a lot of connectors. Mainly, we can do everything with the data in the pipe. I really like the graphical interface too"
 

Cons

"The visual user interface could use some help; it needs improvement."
"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."
"The documentation on offer is not that good."
"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."
"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 logging mechanism could be improved. If I am working on a pipeline, then create a job out of it and it is running, it will generate constant logs. So, the logging mechanism could be simplified. Now, it is a bit difficult to understand and filter the logs. It takes some time."
"StreamSets should provide a mechanism to be able to perform data quality assessment when the data is being moved from one source to the target."
"There aren't enough hands-on labs, and debugging is also an issue because it takes a lot of time. Logs are not that clear when you are debugging, and you can only select a single source for a pipeline."
"The design experience is the bane of our existence because their documentation is not the best. Even when they update their software, they don't publish the best information on how to update and change your pipeline configuration to make it conform to current best practices. We don't pay for the added support. We use the "freeware version." The user community, as well as the documentation they provide for the standard user, are difficult, at best."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"We often faced problems, especially with SAP ERP. We struggled because many columns weren't integers or primary keys, which StreamSets couldn't handle. We had to restructure our data tables, which was painful. Also, pipeline failures were common, and data drifting wasn't addressed, which made things worse. Licensing was another issue we encountered."
"There are a few things that can be better."
"If the data processing in StreamSets takes a long time as compared to the previous solution, then we will reconsider why we use StreamSets."
 

Pricing and Cost Advice

"This is an open-source product that can be used free of charge."
"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."
"The solution provides value for money, and we are currently using its community edition."
"The pricing is affordable for any business."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"The pricing is too fixed. It should be based on how much data you need to process. Some businesses are not so big that they process a lot of data."
"We use the free version. It's great for a public, free release. Our stance is that the paid support model is too expensive to get into. They should honestly reevaluate that."
"The overall cost is very flexible so it is not a burden for our organization... However, the cost should be improved. For small and mid-size organizations it might be a challenge."
"It has a CPU core-based licensing, which works for us and is quite good."
"There are different versions of the product. One is the corporate license version, and the other one is the open-source or free version. I have been using the corporate license version, but they have recently launched a new open-source version so that anybody can create an account and use it. The licensing cost varies from customer to customer. I don't have a lot of input on that. It is taken care of by PMO, and they seem fine with its pricing model. It is being used enterprise-wide. They seem to have got a good deal for StreamSets."
"Its pricing is pretty much up to the mark. For smaller enterprises, it could be a big price to pay at the initial stage of operations, but the moment you have the Seed B or Seed C funding and you want to scale up your operations and aren't much worried about the funds, at that point in time, you would need a solution that could be scaled."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
900,644 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Computer Software Company
10%
Retailer
8%
Manufacturing Company
6%
Financial Services Firm
12%
Manufacturing Company
7%
Insurance Company
7%
Computer Software Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise1
Large Enterprise5
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

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...
What needs improvement with StreamSets?
One issue I observed with StreamSets is that the memory runs out quickly when processing large volumes of data. Because of this memory issue, we have to upgrade our EC2 boxes in the Amazon AWS infr...
What is your primary use case for StreamSets?
We are using StreamSets for batch loading.
What advice do you have for others considering StreamSets?
If asked, I definitely recommend StreamSets to other users. My overall rating for the solution is nine.
 

Overview

 

Sample Customers

Information Not Available
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about Spring Cloud Data Flow vs. StreamSets and other solutions. Updated: June 2026.
900,644 professionals have used our research since 2012.