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

StreamSets 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

StreamSets
Ranking in Data Integration
23rd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
21
Ranking in other categories
No ranking in other categories
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 July 2025, in the Data Integration category, the mindshare of StreamSets is 1.6%, up from 1.4% compared to the previous year. The mindshare of Talend Open Studio is 4.4%, down from 5.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration
 

Featured Reviews

Ved Prakash Yadav - PeerSpot reviewer
Useful for data transformation and helps with column encryption
We use various tools and alerting systems to notify us of pipeline errors or failures. StreamSets supports data governance and compliance by allowing us to encrypt incoming data based on specified rules. We can easily encrypt columns by providing the column name and hash key. If you're considering using StreamSets for the first time, I would advise first understanding why you want to use it and how it will benefit you. If you're dealing with change tracking or handling large amounts of data, it could be cost-effective compared to services like Amazon. It's easy to schedule and manage tasks with the tool, and you can enhance your skills as an ETL developer. You can easily migrate traditional pipelines built on platforms like Informatica or Talend to StreamSets. I rate the overall solution an eight out of ten.
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 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."
"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."
"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 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 customize it to do what you need. Many other tools have started to use features similar to those introduced by StreamSets, like automated workflows that are easy to set up."
"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."
"StreamSets Transformer is a good feature because it helps you when you are developing applications and when you don't want to write a lot of code. That is the best feature overall."
"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 rapidity of integration with data may be one of the valuable features."
"Talend is safe to use because it is very restrictive. It is easy to use when one learns how to manipulate data with SQL."
"The most valuable feature of Talend Open Studio is the tMap component. There is a lot of functionality in one component."
"The API integration and big data approach are very good because of how you extract data from JSP files or big data web repositories like MongoDB."
"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 graphical design environment is also very easy."
"We're sold on the customization part of the solution."
"The most valuable feature for me when it comes to this solution is that it's easy to use."
"This product is very easy to use."
 

Cons

"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."
"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."
"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."
"Visualization and monitoring need to be improved and refined."
"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."
"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."
"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."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"The only other thing is that you have to integrate into an API gateway. We're in Azure, so we use Microsoft Azure Gateway. It doesn't come with its own gateway, which is another sort of big plus side that we saw in Boomi. Talend isn't quite there yet with the API gateway."
"Inter-version compatibility is a problem, and migration projects between versions are required."
"I think my biggest problem with the tool is that the errors are very hard to debug."
"Talend should improve the log and error handling to better track the errors you find during development. Sometimes it's challenging to see what's causing an issue, and tracking that on Talend is complicated."
"Having additional training materials, such as a video tutorial, would be an improvement."
"I rate Talend Open Studio's stability an eight out of ten. Talend has some problems sometimes."
"The server-side should be completely revamped."
"We don't get continuous replication of the data."
 

Pricing and Cost Advice

"I believe the pricing is not equitable."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"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 an expensive solution."
"We are running the community version right now, which can be used free of charge."
"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."
"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."
"It has a CPU core-based licensing, which works for us and is quite good."
"Pricing is always a challenge. It is quite an expensive model, but because the platform is so simple to use, we haven't had to purchase any additional licenses."
"The cost for one year for the ETL tools, not for the big data, is 6K per year. It is a good price."
"It is an open-source tool which means it is a free solution."
"It does the job well for nothing — without cost. That's the advantage of this product."
"There are many versions available and one is open-sourced which is free."
"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."
"It is an open-source product."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
860,592 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
11%
Manufacturing Company
10%
Insurance Company
9%
Financial Services Firm
17%
Computer Software Company
13%
Manufacturing Company
8%
Government
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

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

Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Almerys, BF&M, Findus
Find out what your peers are saying about StreamSets vs. Talend Open Studio and other solutions. Updated: May 2025.
860,592 professionals have used our research since 2012.