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

Spring Cloud Data Flow vs Talend Open Studio 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
21st
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
9
Ranking in other categories
Streaming Analytics (9th)
Talend Open Studio
Ranking in Data Integration
5th
Average Rating
8.0
Reviews Sentiment
6.8
Number of Reviews
50
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2025, in the Data Integration category, the mindshare of Spring Cloud Data Flow is 1.2%, up from 0.9% compared to the previous year. The mindshare of Talend Open Studio is 4.7%, down from 5.1% 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.
Costin Marzea - PeerSpot reviewer
Allows you to develop your own components and can be used as an OEM
Sometimes, scalability is part of planning. It depends on what you mean by scalability. People talk a lot about it, but scalability is not always about system functionality. Sometimes, it may be planning the job you're doing. If you want to split it into several jobs or servers, you don't actually have to have it built in as a functionality. You can create a job using a loop, which runs and controls several jobs in a loop that may be controlled. Scaling should not always be part of the infrastructure based on whether the engine can scale or not. I think it's your plan or project that should scale and split, and you can define these parameters. These parameters include how many servers you want to run or how many executions you want to do on different parts of the data. It's not always an issue of the engine running. Sometimes, your database should be configured to support partitioning. The product may scale very well without partitioning, but if the basic response is very slow, you didn't solve the problem. You should solve the problems at a higher level, not just at the execution level. They should be solved at the database level and communication level, and you should have firewalls. We are trying to add to the open source the ability to generate code for containers and Kubernetes that exist in the subscription version. Once you do this, Kubernetes will take care of the scaling, so there is no problem.

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."
"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 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 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 best thing I like about Spring Cloud Data Flow is its plug-and-play model."
"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."
"Talend Open Studio's installation process is easy. One just needs to install Java before installing the product"
"The solution has a good balance between automated items and the ability for a developer to integrate and extend what he needs. Other competing tools do not offer the same grade of flexibility when you need to go beyond what is provided by the tool. Talend, on the other hand, allows you to expand very easily."
"The drag-and-drop feature in the interface is very good."
"Talend lets you do everything — mapping, workflow, and orchestration — in a single place."
"It's a good tool. It has the ability to take apart and install whatever we need. It's very good for data, transformation, and loading."
"The product's initial setup phase was easy."
"The rapidity of integration with data may be one of the valuable features."
"The initial setup of the product was very easy."
 

Cons

"Spring Cloud Data Flow is not an easy-to-use tool, so 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."
"The configurations could be better. Some configurations are a little bit time-consuming in terms of trying to understand using the Spring Cloud documentation."
"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 solution's community support could be improved."
"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."
"In version 6.2 we did encounter issues with the job servers and specifically with ESB. Version 6.3 is better but large jobs can cause the MDM server to fall over, requiring a reboot."
"The documentation is lacking within the product. They need to get better at all aspects of describing how it works and how to use it."
"As for improvement or additional features, I would like to know how to use Java in Talend and also how to use Talend in the cloud or in big data. I would prefer to have storage directly on Talend."
"I would say that writing to JSON is kind of a pain. It reads from a JSON file pretty well, but writing to a JSON file is not so great because its components are not good."
"The pricing could be lower. They should work to make it more affordable."
"The user interface could be made simpler."
"The solution should offer better integration with other products."
"The solution should integrate with a version control system in the subscription versions to make it easy to work with and manage the version control."
 

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."
"The solution provides value for money, and we are currently using its community edition."
"This is an open-source product that can be used free of charge."
"I am using the open-source version and it is free."
"Price could be lower. It is getting too expensive when compared to some other solutions, which is actually a little bit concerning."
"Talend is free and you can download it."
"The cost, particularly in Africa, is quite high."
"Talend Open Studio is priced too high."
"The paid version of this solution has a very high price, but even with the limitations, the Community version works fine."
"Open Studio has a basic license and additional costs for services, including customer support and technical assistance."
"We are using the free version of the tool, because the enterprise version is a little expensive."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
856,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
26%
Computer Software Company
17%
Retailer
7%
Manufacturing Company
6%
Financial Services Firm
16%
Computer Software Company
13%
Manufacturing Company
8%
Government
7%
 

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...
How does Talend Open Studio compare with AWS Glue?
We reviewed AWS Glue before choosing Talend Open Studio. AWS Glue is the managed ETL (extract, transform, and load) from Amazon Web Services. AWS Glue enables AWS users to create and manage jobs in...
What do you like most about Talend Open Studio?
It is easy to use and covers most of the functions needed. We can use the code without any extra effort. The open source is very good. They have the same commercials with additional connectors. The...
 

Also Known As

No data available
Open Studio
 

Overview

 

Sample Customers

Information Not Available
Almerys, BF&M, Findus
Find out what your peers are saying about Spring Cloud Data Flow vs. Talend Open Studio and other solutions. Updated: June 2025.
856,873 professionals have used our research since 2012.