Migration from Camunda Platform 7 to Camunda Platform 8

Camunda 8 Topics Discussion & Questions
1

Dear All,

We are using Camunda Platform Engine 7 and it’s deployed K8s environment and running inside a POD. We are seeing a lot of performance issues with the camunda workflows that we have designed along with the scale of data we are supposed to process. We tried to increase the parallelism in camunda platform engine 7. However, there is not much luck and we started seeing a lot of OptimisticLockingException and which requires explicit handling for each of the service tasks that we have.

We found some articles where its mentioned that camunda platform engine 8 is designed to optimise the performance with more parallelism and it even avoids the OptimisticLockingException.

Could you please help us with the guidelines or any references that should be followed for migrating from Camunda engine platform 7 to Camunda engine platform 8.

Any help would be appreciated. Thanks in advance.

Regards,
Ishan Aggarwal

2

Hello @Ishan_Aggarwal ,

if you want to look into migration to Camunda 8, please have a look here:

This gives you a very detailed view on all the aspects you need to consider.

The tooling that helps you with migration is currently under development. The guide links to a repo that you want to follow.

Jonathan

2 Likes
3

Here is another resource for your consideration - the latest Camunda Nation podcast episode: Camunda 7 to 8 Migration, with Bernd Ruecker.

3 Likes
4

Hi @jonathan.lukas - Thanks for the link. I have migrated the diagram using the solution provided. but I am facing issue with sub-process. even though the component is provided in camunda 8, using it throws below error. Can you please help with this.
A Subprocess must be expanded.

5

Hello @syedkp ,

does the Camunda Modeler linter show this problem?

Jonathan

6

@jonathan.lukas - yeah it does. I am not sure why its an error when we have the collapsed subprocess as a component.

7

Hello @syedkp ,

the reason for this error is that currently, Operate is not able to dig into the subprocess, which can lead to a bad experience.

They are working on making it available, yet this error will not block you.
Also, this will be documented.

Thank you for bringing this up!

Jonathan

8

@jonathan.lukas - Yeah I am able to deploy the bpmn file with subprocess errors. so I think its not a blocker. hopefully team will be able to resolve the glitch and modeler doesnt show up this error. Thanks.

1 Like
9

@jonathan.lukas - another issue is related to inclusive gateway. we have multiple incoming flows but we are able to see below error message. Can you help this resolve as its a blocker and we are not able to deploy the bpmn file. Please let me know if there is any alternative till we get this resolved.

“Currently the inclusive gateway can only have one incoming sequence flow”.

10

Hello @syedkp ,

this is correct. Currently, only the forking inclusive gateway is supported. The joining inclusive gateway is rather complex and will be implemented in a future release.

I hope this helps

Jonathan

11

@jonathan.lukas - oh when can we expect a fix for this? moreover is there any alternate approach to achieve the same functionality?

12

Hello @syedkp ,

there is an alternative described here:

I would suggest the same:

diagram_1
diagram_12244×2430 239 KB

Jonathan

1 Like
13

@jonathan.lukas - Thanks for the alternate solution. I will try and let you know if any help needed.

1 Like
14