operation of Camunda

Camunda 8 Topics
1

Here’s the situation:

  • Camunda is installed.
  • There are several instances of my application communicating with Camunda via Zeebe Client: dev1, dev2, and local.
  • A process is initiated through a REST request.
  • Upon sending a request to ‘local’, the processing occurs on ‘dev1’ or ‘dev2’, and similarly, sending a request to ‘dev1’ or ‘dev2’ may result in processing on ‘local’.

How can I configure the system so that the entire process, from start to finish, is handled on the same instance to which the request was sent?

2

Hi @Dealmon_Streisend,

could you add more details about “local”, “dev1” and “dev2”?

What are they?

How did you install Camunda?

Cheers, Ingo

3

Hi, Camunda installed with helm chart to kubernetes cluster
dev1 - container in kubernetes
dev2 - second replica of container in kubernetes
local - local development container, its running in my computer.
All 3 apps use the same key to connect to camunda

4

Hi @Dealmon_Streisend :wave:

I’m not entirely sure about it, but I think you might be looking for the message aggregator pattern. If you want your REST APIs to interact with the same process instance, you can publish messages with the same correlation key from all the different places, and collect them in the same process instance.