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

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
22nd
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Streaming Analytics (9th)
StreamSets
Ranking in Data Integration
16th
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 May 2025, in the Data Integration category, the mindshare of Spring Cloud Data Flow is 1.1%, up from 0.9% compared to the previous year. The mindshare of StreamSets is 1.6%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration
 

Featured Reviews

NitinGoyal - PeerSpot reviewer
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.
Karthik Rajamani - PeerSpot reviewer
Integrates with different enterprise systems and enables us to easily build data pipelines without knowing how to code
There are a few things that can be better. We create pipelines or jobs in StreamSets Control Hub. It is a great feature, but if there is a way to have a folder structure or organize the pipelines and jobs in Control Hub, it would be great. I submitted a ticket for this some time back. There are certain features that are only available at certain stages. For example, HTTP Client has some great features when it is used as a processor, but those features are not available in HTTP Client as a destination. There could be some improvements on the group side. Currently, if I want to know which users are a part of certain groups, it is not straightforward to see. You have to go to each and every user and check the groups he or she is a part of. They could improve it in that direction. Currently, we have to put in a manual effort. In case something goes wrong, we have to go to each and every user account to check whether he or she is a part of a certain group or not.

Quotes from Members

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

Pros

"The dashboards in Spring Cloud Dataflow are quite valuable."
"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 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 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 best thing I like about Spring Cloud Data Flow is its plug-and-play model."
"The product is very user-friendly."
"The most valuable feature is real-time streaming."
"The most valuable feature is the pipelines because they enable us to pull in and push out data from different sources and to manipulate and clean things up within them."
"In StreamSets, everything is in one place."
"I have used Data Collector, Transformer, and Control Hub products from StreamSets. What I really like about these products is that they're very user-friendly. People who are not from a technological or core development background find it easy to get started and build data pipelines and connect to the databases. They would be comfortable like any technical person within a couple of weeks."
"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."
"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."
"For me, the most valuable features in StreamSets have to be the Data Collector and Control Hub, but especially the Data Collector. That feature is very elegant and seamlessly works with numerous source systems."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"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."
 

Cons

"On the tool's online discussion forums, you may get stuck with an issue, making it an area where improvements are required."
"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."
"I would improve the dashboard features as they are not very user-friendly."
"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."
"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 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."
"The execution engine could be improved. When I was at their session, they were using some obscure platform to run. There is a controller, which controls what happens on that, but you should be able to easily do this at any of the cloud services, such as Google Cloud. You shouldn't have any issues in terms of how to run it with their online development platform or design platform, basically their execution engine. There are issues with that."
"I would like to see it integrate with other kinds of platforms, other than Java. We're going to have a lot of applications using .NET and other languages or frameworks. StreamSets is very helpful for the old Java platform but it's hard to integrate with the other platforms and frameworks."
"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 documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"One thing that I would like to add is the ability to manually enter data. The way the solution currently works is we don't have the option to manually change the data at any point in time. Being able to do that will allow us to do everything that we want to do with our data. Sometimes, we need to manually manipulate the data to make it more accurate in case our prior bifurcation filters are not good. If we have the option to manually enter the data or make the exact iterations on the data set, that would be a good thing."
"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."
"Currently, we can only use the query to read data from SAP HANA. What we would like to see, as soon as possible, is the ability to read from multiple tables from SAP HANA. That would be a really good thing that we could use immediately. For example, if you have 100 tables in SQL Server or Oracle, then you could just point it to the schema or the 100 tables and ingestion information. However, you can't do that in SAP HANA since StreamSets currently is lacking in this. They do not have a multi-table feature for SAP HANA. Therefore, a multi-table origin for SAP HANA would be helpful."
"In terms of the product, I don't think there is any room for improvement because it is very good. One small area of improvement that is very much needed is on the knowledge base side. Sometimes, it is not very clear how to set up a certain process or a certain node for a person who's using the platform for the first time."
 

Pricing and Cost Advice

"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."
"The solution provides value for money, and we are currently using its community edition."
"StreamSets is an expensive solution."
"It has a CPU core-based licensing, which works for us and is quite good."
"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."
"The licensing is expensive, and there are other costs involved too. I know from using the software that you have to buy new features whenever there are new updates, which I don't really like. But initially, it was very good."
"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 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."
"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."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
26%
Computer Software Company
18%
Retailer
7%
Manufacturing Company
5%
Financial Services Firm
13%
Computer Software Company
11%
Manufacturing Company
10%
Insurance Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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 do you like most about StreamSets?
The best thing about StreamSets is its plugins, which are very useful and work well with almost every data source. It's also easy to use, especially if you're comfortable with SQL. You can customiz...
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.
 

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: April 2025.
851,604 professionals have used our research since 2012.