Vertify vs. WSO2 Integration Platform

I would recommend it, as VertifyData exactly fit our use case. I can't speak for all use cases and all connectors - naturally - but the ones we are using and have explored so far, work perfectly well. Also, being a person myself that is not fluent in SQL or JSON or API language in general, I was still able to create all workflows our company needed myself. Which I consider a huge benefit.

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.

• Communication.
• Follow up.
• They're constantly trying to improve.

• 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

• Automated error trouble-shooting is not always clear/helpful
• Clearly distinguishing internal errors vs. external errors
• Perhaps a blog where users can interact with questions + solutions

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

Creating a mapping between source and target while also using lookups and transformations is not trivial. And VertifyData solved this reasonably well, at least all users in my organization understood it pretty quickly.

It is not the easiest user interface to read/understand. However, once you understand how it works, then using it is not that bad. It's hard to remember what feature is listed under what tab (Manage vs. Define). A suggestion would be to get all call to actions on the same page

Vertify offered more flexibility and was presented as a simple solution. In reality, it is more complex that we envisioned and we have never fully utilized our tools due to the lack of ability to configure things properly.

Incentivized

Independently Invited by TrustRadius

A de minimis incentive was given to thank the reviewer for their time. The incentive was not used to bias or drive a particular response, nor was the incentive contingent on a positive endorsement. More Info

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.

• Independently, teams are able to carry out their process with less communication and at a higher level of accuracy.
• VertifyData is actively taking into consideration, consulting, and supporting our plans to build out the business

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