We performed a comparison between CloverDX Designer and StreamSets based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Informatica, Oracle and others in Data Integration."Its simplicity and the way it handles graphs are the most valuable features."
"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"
"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's very easy to integrate. It integrates with Snowflake, AWS, Google Cloud, and Azure. It's very helpful for DevOps, DataOps, and data engineering because it provides a comprehensive solution, and it's not complicated."
"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."
"In StreamSets, everything is in one place."
"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."
"It is really easy to set up and the interface is easy to use."
"The best feature that I really like is the integration."
"If I could give any advice to the guys who are developing it, I would suggest them to really look at the enterprise features, such as being able to log what's going on, being able to capture the current state of processing, and being able to recover from error situations. So, there should be a focus on logging, recoverability, and monitoring. We should be able to monitor what's going on, and in case of any issues, we should be able to recover and restart processing and other things. For scalability and performance, I would probably suggest the Pushdown feature so that you can do the transformation directly on the data source. You do not need to do that calculation within the ETL server. For this, you should be aware of the type of data because each database or kind of storage, such as Hadoop, has its own ANSI standard or language, such as SQL. Microsoft, Oracle, and IBM have their own language. Based on the feedback that I have got, its initial setup takes some time. It could perhaps be simpler."
"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."
"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."
"Sometimes, when we have large amounts of data that is very efficiently stored in Hadoop or Kafka, it is not very efficient to run it through StreamSets, due to the lack of efficiency or the resources that StreamSets is using."
"Using ETL pipelines is a bit complicated and requires some technical aid."
"If you use JDBC Lookup, for example, it generally takes a long time to process data."
"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."
"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."
"Visualization and monitoring need to be improved and refined."
Earn 20 points
CloverDX Designer is ranked 66th in Data Integration while StreamSets is ranked 8th in Data Integration with 24 reviews. CloverDX Designer is rated 7.0, while StreamSets is rated 8.4. The top reviewer of CloverDX Designer writes "Simple, stable, and allows us to handle data from various sources, but needs enterprise features for logging, recoverability, and monitoring". On the other hand, the top reviewer of StreamSets writes "We no longer need to hire highly skilled data engineers to create and monitor data pipelines". CloverDX Designer is most compared with , whereas StreamSets is most compared with Fivetran, Azure Data Factory, Informatica PowerCenter, SSIS and Oracle GoldenGate.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.