CloverDX Designer vs CloverETL comparison

"Its simplicity and the way it handles graphs are the most valuable features."

"Connectivity to various data sources: The ability to extract data from different data sources gives greater flexibility."

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

"Key features include wealth of pre-defined components; all components are customizable; descriptive logging, especially for error messages."

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

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

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

"Its price and value for money would be okay for our purpose if there were some additional features."