Spring Cloud Data Flow vs StreamSets comparison

VMware and IBM are both solutions in the Data Integration category. VMware is ranked #23 with an average rating of 7.7, while IBM is ranked #9 with an average rating of 8.4. VMware holds a 1.1% mindshare in DI, compared to IBM’s 1.8% mindshare. Additionally, 88% of VMware users are willing to recommend the solution, compared to 100% of IBM users who would recommend it.

Spring Cloud Data Flow

Read 9 Spring Cloud Data Flow reviews

1,725 Views
1,296 Comparison Views

88% willing to recommend

StreamSets

Read 22 StreamSets reviews

2,905 Views
1,916 Comparison Views

100% willing to recommend

Spring Cloud Data Flow

StreamSets

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Dec 19, 2024

StreamSets and Spring Cloud Data Flow compete in the data integration and orchestration category. StreamSets offers advantages in user-friendliness and data transformation capabilities, making it the preferred choice for those emphasizing ease of use and flexibility in design.

Features: StreamSets offers a drag-and-drop interface for data pipeline creation, supports both batch and streaming data processing, and provides robust data transformation capabilities at the source. Its control hub facilitates graphical design with flexibility. Spring Cloud Data Flow is notable for its microservices orchestration, integration with Kubernetes, and support for low-resource execution using a simple programming model.

Room for Improvement: StreamSets needs better integration with non-Java platforms, enhanced memory management, and improvements in its security features and user interface. It also requires expanded SAP HANA capabilities and more effective data drift handling. Spring Cloud Data Flow could benefit from better community support, enhanced documentation, and improved UI for Kubernetes integration. Additional support for non-Java languages would also be beneficial.

Ease of Deployment and Customer Service: StreamSets provides versatile deployment options across public and hybrid clouds and generally responsive support, although complex issues may require time. Spring Cloud Data Flow is well-suited for private cloud environments but relies heavily on community forums for support, making professional assistance necessary for more challenging deployments. StreamSets facilitates easier cloud deployments, while Spring Cloud Data Flow is ideal for those adept at self-support in private solutions.

Pricing and ROI: StreamSets offers a range of licensing options, including open-source and commercial, but faces criticism for its cost structure, making it less attractive to smaller enterprises. It offers significant ROI for larger organizations in need of comprehensive ETL solutions. Spring Cloud Data Flow provides value through its free open-source model, being cost-effective for community edition users. StreamSets reports increased sales of up to 50%, while Spring Cloud Data Flow is ideal for budget-conscious users seeking open-source capabilities.

To learn more, read our detailed Spring Cloud Data Flow vs. StreamSets Report (Updated: December 2024).

Buyer's Guide

Spring Cloud Data Flow vs. StreamSets

December 2024

Download the complete report

Helped 824,053 peers since 2012

Categories and Ranking

Spring Cloud Data Flow

Ranking in Data Integration

23rd

Average Rating

7.8

Reviews Sentiment

6.8

Number of Reviews

Ranking in other categories

Streaming Analytics (9th)

StreamSets

Ranking in Data Integration

9th

Average Rating

8.4

Reviews Sentiment

7.1

Number of Reviews

Ranking in other categories

No ranking in other categories

Mindshare comparison

As of December 2024, in the Data Integration category, the mindshare of Spring Cloud Data Flow is 1.1%, up from 1.0% compared to the previous year. The mindshare of StreamSets is 1.8%, up from 1.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.

Data Integration

Featured Reviews

NitinGoyal

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.

Read full review

Reyansh Kumar

Technical Specialist at Accenture

We no longer need to hire highly skilled data engineers to create and monitor data pipelines

The things I like about StreamSets are its * overall user interface * efficiency * product features, which are all good. Also, the scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy. You just need to configure the data sources, the paths and their configurations, and you are ready to go. It is very efficient and very easy to use for ETL pipelines. It is a GUI-based interface in which you can easily create or design your own data pipelines with just a few clicks. As for moving data into modern analytics systems, we are using it with Microsoft Power BI, AWS, and some on-premises solutions, and it is very easy to get data from StreamSets into them. No hardcore coding or special technical expertise is required. It is also a no-code platform in which you can configure your data sources and data output for easy configuration of your data pipeline. This is a very important aspect because if a tool requires code development, we need to hire software developers to get the task done. By using StreamSets, it can be done with a few clicks.

Read full review

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 product is very user-friendly."

"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 best thing I like about Spring Cloud Data Flow is its plug-and-play model."

"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 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."

"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."

"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."

"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"

"The ability to have a good bifurcation rate and fewer mistakes is valuable."

"The ETL capabilities are very useful for us. We extract and transform data from multiple data sources, into a single, consistent data store, and then we put it in our systems. We typically use it to connect our Apache Kafka with data lakes. That process is smooth and saves us a lot of time in our production systems."

"It's very easy to integrate. It integrates with Snowflake, AWS, Google Cloud, and Azure. It's very helpful for DevOps, DataOps, and data engineering because it provides a comprehensive solution, and it's not complicated."

"The scheduling within the data engineering pipeline is very much appreciated, and it has a wide range of connectors for connecting to any data sources like SQL Server, AWS, Azure, etc. We have used it with Kafka, Hadoop, and Azure Data Factory Datasets. Connecting to these systems with StreamSets is very easy."

More StreamSets pros

Cons

"I would improve the dashboard features as they are not very user-friendly."

"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."

"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."

"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."

"The solution's community support could be improved."

"Spring Cloud Data Flow is not an easy-to-use tool, so 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 monitoring visualization is not that user-friendly. It should include other features to visualize things, like how many records were streamed from a source to a destination on a particular date."

"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."

"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."

"The software is very good overall. Areas for improvement are the error logging and the version history. I would like to see better, more detailed error logging information."

"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."

"The data collector in StreamSets has to be designed properly. For example, a simple database configuration with MySQL DB requires the MySQL Connector to be installed."

"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."

"StreamSet works great for batch processing but we are looking for something that is more real-time. We need latency in numbers below milliseconds."

More StreamSets cons

Pricing and Cost Advice

"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."

"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."

"StreamSets Data Collector is open source. One can utilize the StreamSets Data Collector, but the Control Hub is the main repository where all the jobs are present. Everything happens in Control Hub."

"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."

"StreamSets is expensive, especially for small businesses."

"StreamSets is an expensive solution."

"I believe the pricing is not equitable."

"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's not so favorable for small companies."

More StreamSets pricing and cost advice

See which vendors are best for you

Use our free recommendation engine to learn which Data Integration solutions are best for your needs.

See recommendations

824,053 professionals have used our research since 2012.

Top Industries

By visitors reading reviews

Financial Services Firm

27%

Computer Software Company

18%

Manufacturing Company

Retailer

Financial Services Firm

17%

Computer Software Company

10%

Manufacturing Company

10%

Insurance Company

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...

See all answers

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...

See all answers

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...

See all answers

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...

See all answers

What needs improvement with StreamSets?

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 ...

See all answers

What is your primary use case for StreamSets?

StreamSets is used for data transformation rather than ETL processes. It focuses on transforming data directly from sources without handling the extraction part of the process. The transformed data...

See all answers

Comparisons

Apache Flink vs Spring Cloud Data Flow

Compared 35% of the time

TIBCO BusinessWorks vs Spring Cloud Data Flow

Compared 11% of the time

Google Cloud Dataflow vs Spring Cloud Data Flow

Compared 9% of the time

Apache Spark Streaming vs Spring Cloud Data Flow

Compared 7% of the time

SSIS vs Spring Cloud Data Flow

Compared 2% of the time

More Spring Cloud Data Flow Competitors

Informatica PowerCenter vs StreamSets

Compared 13% of the time

IBM InfoSphere DataStage vs StreamSets

Compared 10% of the time

Fivetran vs StreamSets

Compared 10% of the time

webMethods.io vs StreamSets

Compared 8% of the time

More StreamSets Competitors

Product Reports

Buyer's Guide

Spring Cloud Data Flow

November 2024

Download Spring Cloud Data Flow product report

Buyer's Guide

StreamSets

November 2024

Download StreamSets product report

Learn More

VMware

Video not available

IBM

Overview

Spring Cloud Data Flow is a toolkit for building data integration and real-time data processing pipelines.
Pipelines consist of Spring Boot apps, built using the Spring Cloud Stream or Spring Cloud Task microservice frameworks. This makes Spring Cloud Data Flow suitable for a range of data processing use cases, from import/export to event streaming and predictive analytics. Use Spring Cloud Data Flow to connect your Enterprise to the Internet of Anything—mobile devices, sensors, wearables, automobiles, and more.

StreamSets is a data integration platform that enables organizations to efficiently move and process data across various systems. It offers a user-friendly interface for designing, deploying, and managing data pipelines, allowing users to easily connect to various data sources and destinations. StreamSets also provides real-time monitoring and alerting capabilities, ensuring that data is flowing smoothly and any issues are quickly addressed.

Sample Customers

Information Not Available

Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge

Buyer's Guide

Spring Cloud Data Flow vs. StreamSets

December 2024

Free Report: Spring Cloud Data Flow vs. StreamSets

Find out what your peers are saying about Spring Cloud Data Flow vs. StreamSets and other solutions. Updated: December 2024.

DOWNLOAD NOW

824,053 professionals have used our research since 2012.

See our Spring Cloud Data Flow vs. StreamSets report.

See our list of best Data Integration vendors.

We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.