Camunda vs. UiPath Integration Service

Camunda Platform is well suited for scenarios where there are different stages in a business flow and the flow is driven by user action at each stage. For example placing of an order on an ecommerce platform. Depending on whether user was able to make the payment or not the workflow would go to dispatch or retry stage. Now the retry stage would trigger further actions like sending follow up emails etc. Likewise, dispatch stage would have a different set of actions. Since every order is important and we need to know where it stands, using Camunda Platform is imperative. Camunda Platform might not be a right choice where just a one off thing needs to be done. For example, uploading of product information by user or periodic processing of heavy images by a worker. These are all either one step processes or periodic automated processes where we can track the status without using a business modeler like Camunda Platform.

Incentivized

Areas where it would be appropriate:

1. If you want a really 'deep' integration with a third party software, and you want all the control over how it interacts with your software
2. If you want a totally white-labeled solution, that is totally invisible to your customers.
3. if you care more about a well thought out/useful API, rather than a pretty UI

Areas where it is less appropriate:

1. If you want a Zapier-esque hands-off integration for YOU.
2. if you want your customers to do more of the work, pay for it/etc.
3. if you're a really small business, it could be too expensive. But it depends on your individual contract with them.

Incentivized

• Task orchestration
• Freeware
• Graphical interface allows normal users to understand business process model diagrams more intuitively

Incentivized

• Customer Support -- They have a knowledgeable team and are very responsive.
• Communication -- Most questions are addressed quickly
• Documentation -- The API documentation is well organized and easy to follow.

Incentivized

• Documentation - It is usually daunting for beginners because of lack of good documentation
• Simplified setup on local machine for Camunda Server would help developers test changes quickly
• Easier migration from one deployment version of a Camunda process to another deployment version would help in making changes and deploying them faster.
• Heap memory management becomes issue at times resulting in stuck processes. This needs to be resolved.

Incentivized

• There weren't really many cons to our experience. The only slight downside was the cost but they worked with us on that to make it work.

Incentivized

Camunda provides pretty standard product support offerings.

MuleSoft is also a similar product to Cloud Elements, but is not available as an option in this form.

Workato and MuleSoft are competing cloud API connector platforms that perform a similar function to Cloud Elements. We chose Cloud Elements over them because CE provided a more robust path to unifying the behavior of connected systems.

Zapier is a workflow automation tool that I feel draws erroneous comparison to Cloud Elements that I need to highlight. Workflow automation tools (Zapier, IFTTT, Microsoft Flow) do provide multiple integrations, but for simplistic scenarios where only a handful of explicitly described steps need accomplished. Cloud Elements is a platform for developers to deliver faster and with higher reliability than making integrations one-by-one in complex systems that solve demanding problems.

Incentivized

• We've built a good business around developing and deploying Camunda for our clients over the last 7 years.
• Our clients are finding it a cost-effective way to try before they buy.
• There's an over-reliance on big offshore outsourcing shops, which hurts ROI and success rates.

• We are able to build integrations in HALF the time we could build them from scratch.
• They allow our development team to spend more hours focused on developing our core product, not connections to other products.
• Their large catalog of services to connect to allows us to spend much less time researching other platform integration endpoints and increases our R&D speed a considerable amount.

Incentivized