CloverDX vs. WSO2 Enterprise Integrator

CloverDX designer as a standalone is well suited for fairly straightforward transformations of data. If you want to do large scale data integrations, then their server edition adds an extra level of automation and job control.

Incentivized

The best-suited scenario is the service chain pattern or all patterns used in online mode. The less appropriate scenario is a batch service the duration time of the service is more than 10minutes because it is necessary to increase the HTTP timeout.

• Connects with Salesforce very well
• The graphical view of the transformations allows for easy creations and maintenance
• Support has always been eager to assist with any graph creation difficulties I run into

Incentivized

• Service chain pattern
• Message transformation
• Call more than one backend service
• Call service with different protocoll as the client use
• Use file as input
• Use mail as input

• The initial learning curve is a little steep. Not very steep or super steep, just a little steep.
• Having enough memory for large multi-step problems can be an issue if the graph isn't designed well.

Incentivized

• View deploy artifact in date time order
• Easy way to map data
• Easy way to manage payload

While CloverDX has an active forum for users to submit questions and assist with answers, their in house support team is incredibly responsive when I've contacted them for assistance. This seems almost at odds with most other software companies who try to save money on tech support by promoting a forum or knowledge base.

Incentivized

CloverDX was a less expensive alternative to Talend and had a more intuitive interface from what I could see during the evaluation.

Incentivized

We can start with the community version and then when we moved into production we can buy the supported version. The supported and community version have the same code so we can do every test before deciding to buy the supported version.

• Work that use to take multiple people 20 to 30 hours a week to complete each has now been fully automated to where only 1 or 2 hours a week for maintenance is required.

Incentivized

• Reduce development time to the service integration
• We can use junior developer
• Clustered in easy way