Loose coupling of BPMN - Camunda vs other BPM tools

I know this question might sound very vague, but on a very high level, is there a comparison made between Camunda vs any other BPMN tools like jBPM or Activiti or BonitaSoft or so on…in terms of moving the application from one tool to the other.

For example, if there is a workflow service project that was built using jBPM and now if we have to migrate it to Camunda, how easy or hard is it? And if the same project was built using Camunda, how easy or hard is it move it to another tool? In other words, what is the best approach you can suggest(any whitepapers or blogs or documentation is appreciated) to be NOT tightly coupled with any of one BPM tool which are available in the market?

Thanks
Dheeraj

1 Like

Generally there is no actual interop between the different tools, except for their ability to “Generally” re-present the BPMN. The internal java apis, and nuanced differences between the various engines (lack of sync of APIs) makes the implementations unable to interop / “move between different tools”.

When we think of the ability to move to other tools, the general approach we take is that its a “BPM engine” and there are general expectations of features of what that type of product will provide. If we move to another engine, whatever engine we choose, would still need to have those features, but you need to expect refactor time to adjust to the new engine’s api.