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

"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."
"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."
"I really appreciate the numerous ready connectors available on both the source and target sides, the support for various media file formats, and the ease of configuring and managing pipelines centrally."
"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 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 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."
"It is really easy to set up and the interface is easy to use."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"I didn't have many problems installing it. It seemed very straightforward to me."
"This product is very easy to use."
"The standout feature for me is the user-friendly nature of the components."
"It has got so many connectors. It is intuitive and easy to use."
"We're sold on the customization part of the solution."
"The data integration aspect of the solution is excellent."
"The initial setup was quite straightforward. The deployment took between two and three days."
"It is user-friendly and the interface is good."
 

Cons

"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."
"We've seen a couple of cases where it appears to have a memory leak or a similar problem."
"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."
"They need to improve their customer care services. Sometimes it has taken more than 48 hours to resolve an issue. That should be reduced. They are aware of small or generic issues, but not the more technical or deep issues. For those, they require some time, generally 48 to 72 hours to respond. That should be improved."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"Visualization and monitoring need to be improved and refined."
"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."
"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."
"In the next release, Open Studio should include cloud storage as an input."
"The stability of the solution could improve when running jobs. There can be errors when running projects but in the end, it works well and the errors do not impact the result."
"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."
"The user interface could be made simpler."
"It needs better installation configuration for other databases. Although the installation allows you to select another database, this doesn't mean that all connection points in the application point to the database selected. You actually need to do a search through the entire install to locate the configuration settings and change them."
"The high price of the solution is an area of concern where improvements are required."
"The solution needs more integrations."
"The product could be more intuitive."
 

Pricing and Cost Advice

"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 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."
"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 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."
"The pricing is affordable for any business."
"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 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."
"StreamSets is an expensive solution."
"Pricing and licensing are fairly straightforward. It is reasonably priced and managed."
"The paid version of this solution has a very high price, but even with the limitations, the Community version works fine."
"I am using the open-source version of the solution, so there are no extra costs for any feature."
"It is an open-source tool which means it is a free solution."
"Right now, because we're using the open-source version, there's no cost."
"The solution will be more expensive if you have a low data volume and a large number of developers."
"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."
"For Talend Open Studio, there is a need to make yearly payments towards the licensing cost. Talend Open Studio is a bit expensive, in my opinion."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
860,168 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,168 professionals have used our research since 2012.