The CloverDX Designer is robust an relatively easy to use, once you grasph the paradigm of job flows.
A large collection of building blocks is provided out of the box, and custom components can be created for readers, writers, or transforms that aren't available out of the box using their proprietary "CTL" language or pure java.
Debugging capabilies are pretty powerful, especially when running a local server instance.
Learning curve is low for many simple usage patterns. Review collected by and hosted on G2.com.
Doesn't accommodate a multi-developer, source code-controlled, multi-tier enterprise team very well. Every developer will need their own server license and diffing code is challenging since graphs are persisted as XML.
Advanced use cases quickly exceed the capabilities of users who are not developers or very advanced data analysts. We've found that someone who is already grounded in ETL concepts and development make the best advanced users.
Complex usage and very large volume workflows often require advanced troubleshooting capabilities and tax the system's capabilities.
Support tickets rarely get attention before the next day for U.S. users.
Missing out-of-the-box integrations with most AWS services that are not based on a common open-source project (like Aurora with Postgres or MySQL). We had to build several Gramlin readers and writers for our graph DB us cases. Review collected by and hosted on G2.com.
