When to use Camunda V7 and V8

As we see both the versions exists now V7 and V8, Both are on different platform model/feature/support. If @camunda can share blog, would it be helpful who is on Camunda journey and for newcomers.

  1. Is Camunda V7 will be sunset after sometime?
  2. Many customers use Camunda V7 and tightly intergrated with Springboot application. How customers can migrate to Camunda platform V8.
  3. Many features are not supported in Camunda V8, what would be the roadmap for Camunda V8?
  4. If customer would like to do POC, where we should start V7 or V8.
  5. Is Camunda V8 going in the direction as other BPM vendors, deploying the BPMN process into dedicated server/containers.
  6. In Camunda V7, we use custom java class can be directly mapped into the service task. How that can be done in Camunda V8, did not find any samples or blogs.
  7. Many customers use Camunda V7 community editions and use WebApps in production. But Camunda V8 that’s not possible in production. Are they allowed to write their own apps to monitor/work. Any API being available to develop on their own.

Note: Some of the questions can be come from customers thought process to choose Camunda as BPM engine and over to other BPM engine.

Thank you once again and hoping to hear answer from Camunda product team.


@cpbpm some related resources:

1 Like

Thank you @Philipp_Ossler. Would it be possible to share the DMN update/migration strategy to Camunda V8 too. That info is missing.

Good point. We don’t have a similar blog post or documentation for DMN yet.

The most important aspect to simplify the migration is to use only FEEL but no other expression language in the DMNs. Camunda Platform 8 supports only FEEL in DMN.

Please also have a look at the notes in the documentation, for example, about required decisions.

1 Like