CloverETL vs StreamSets comparison

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

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

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

"It is really easy to set up and the interface is easy to use."

"The ability to have a good bifurcation rate and fewer mistakes is valuable."

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

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

"The most valuable features are the option of integration with a variety of protocols, languages, and origins."

"In StreamSets, everything is in one place."

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

"Needs: easier automated failure recovery; more, and more intuitive auto-generated/filled-in code for components; easier/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.​"

"Its documentation could be improved.​"

"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 documentation is inadequate and has room for improvement because the technical support does not regularly update their documentation or the knowledge base."

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

"The execution engine could be improved. When I was at their session, they were using some obscure platform to run. There is a controller, which controls what happens on that, but you should be able to easily do this at any of the cloud services, such as Google Cloud. You shouldn't have any issues in terms of how to run it with their online development platform or design platform, basically their execution engine. There are issues with that."

"If you use JDBC Lookup, for example, it generally takes a long time to process data."

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

"One area for improvement could be the cloud storage server speed, as we have faced some latency issues here and there."

"The data collector in StreamSets has to be designed properly. For example, a simple database configuration with MySQL DB requires the MySQL Connector to be installed."

"The pricing is good, but not the best. They have some customized plans you can opt for."

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

"It has a CPU core-based licensing, which works for us and is quite good."

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

"We are running the community version right now, which can be used free of charge."