CloverDX Designer Room for Improvement

JL
Data professional at a financial services firm with 1,001-5,000 employees

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.

View full review »
Buyer's Guide
Data Integration
April 2024
Find out what your peers are saying about CloverDX, Talend, Microsoft and others in Data Integration. Updated: April 2024.
768,740 professionals have used our research since 2012.