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

"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."
"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."
"We switched to CloverETL because of its flexibility to connect to various data sources and no dependence on native language and ease of use."
"No dependence on native language and ease of use.​​"
"Server features for scheduler: It is very easy to schedule jobs and monitor them. The interface is easy to use."
"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."
"The most valuable features are the option of integration with a variety of protocols, languages, and origins."
"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."
"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"
"What I love the most is that StreamSets is very light. It's a containerized application. It's easy to use with Docker. If you are a large organization, it's very easy to use Kubernetes."
"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 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."
"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."
 

Cons

"Its documentation could be improved.​"
"​Resource management: We typically run out of heap space, and even the allocation of high heap space does not seem to be enough.​"
"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."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"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."
"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."
"Sometimes, it is not clear at first how to set up nodes. A site with an explanation of how each node works would be very helpful."
"If the data processing in StreamSets takes a long time as compared to the previous solution, then we will reconsider why we use 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 infrastructure."
"Visualization and monitoring need to be improved and refined."
 

Pricing and Cost Advice

Information not available
"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 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."
"There are two editions, Professional and Enterprise, and there is a free trial. We're using the Professional edition and it is competitively priced."
"We are running the community version right now, which 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."
"The pricing is affordable for any business."
report
Use our free recommendation engine to learn which Data Integration solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
27%
Manufacturing Company
12%
Computer Software Company
9%
Retailer
6%
Financial Services Firm
12%
Comms Service Provider
6%
Manufacturing Company
6%
Construction 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.
908,800 professionals have used our research since 2012.