No more typing reviews! Try our Samantha, our new voice AI agent.

CloverETL 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

CloverETL
Ranking in Data Integration
58th
Average Rating
7.0
Reviews Sentiment
6.8
Number of Reviews
2
Ranking in other categories
Data Visualization (35th)
StreamSets
Ranking in Data Integration
24th
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 August 2026, in the Data Integration category, the mindshare of CloverETL is 0.8%, up from 0.3% compared to the previous year. The mindshare of StreamSets is 1.1%, down from 1.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Data Integration Mindshare Distribution
ProductMindshare (%)
StreamSets1.1%
CloverETL0.8%
Other98.1%
Data Integration
 

Featured Reviews

it_user856614 - PeerSpot reviewer
Lead Programmer at a healthcare company with 10,001+ employees
Very easy to schedule jobs and monitor them, however we run out heap space even with a high allocation
Flexibility: We can bring in data from multiple sources, e.g., databases, text files, JSON, email, XML, etc. This has been very helpful Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility. Server features for scheduler: It is…
SS
Enterprise Solutions Architect at a energy/utilities company with 1,001-5,000 employees
Enables effective batch loading with visual interface and enterprise support
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. I had to switch to a new EC2 box, even though the processor was not fully utilized. It would be beneficial if StreamSets addressed any potential memory leak issues to prevent unnecessary upgrades. Additionally, it would be a great enhancement if StreamSets could produce a lineage graph to visualize how the data has passed through the system.

Quotes from Members

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

Pros

"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"No dependence on native language and ease of use.​​"
"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"We switched to CloverETL because of its flexibility to connect to various data sources and no dependence on native language and ease of use."
"Familiar, intuitive GUI coming from a Java development background, in-depth, descriptive, and well-laid-out documentation, responsive support through forums directly from Clover staff, a wealth of customizable pre-defined components, descriptive logging for error messages, and ease of install with a light footprint make it very effective to use."
"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 has definitely helped us in getting the information into our data lake very quickly, in terms of ingestion, and the most important thing is it has helped us from a resourcing point of view because you can easily upskill a BI or ETL resource without any programming knowledge to work with this, which has drastically reduced the time that we are spending on workloads by 60% to 70% as well as reducing the time spent on ingestion by 30%."
"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 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 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."
"StreamSets' reusable assets have helped to reduce workload by 32% to 40%."
"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 is really easy to set up and the interface is easy to use."
 

Cons

"Its documentation could be improved.​"
"Needs easier automated failure recovery, more and more intuitive auto-generated or filled-in code for components, and easier or more automated sync between CloverETL Designer and CloverETL Server."
"​Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough.​"
"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 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."
"The documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."
"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."
"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."
"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."
"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."
"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."
 

Pricing and Cost Advice

Information not available
"StreamSets is an expensive solution."
"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."
"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."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"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."
"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."
"It's not so favorable for small companies."
"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."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
909,948 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
26%
Manufacturing Company
12%
Comms Service Provider
9%
Computer Software Company
9%
Financial Services Firm
12%
Comms Service Provider
7%
Manufacturing Company
6%
Outsourcing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise2
Large Enterprise11
 

Questions from the Community

Ask a question
Earn 20 points
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.
What advice do you have for others considering StreamSets?
If asked, I definitely recommend StreamSets to other users. My overall rating for the solution is nine.
 

Overview

 

Sample Customers

IBM, Oracle, MuleSoft, GoodData, Thomson Reuters, salesforce.com, Comcast, Active Network, SHOP.CA
Availity, BT Group, Humana, Deluxe, GSK, RingCentral, IBM, Shell, SamTrans, State of Ohio, TalentFulfilled, TechBridge
Find out what your peers are saying about CloverETL vs. StreamSets and other solutions. Updated: August 2026.
909,948 professionals have used our research since 2012.