Camunda

What we do.

1. 01

   Process models in BPMN

   We model each process with your business owners and your engineers. The same model is read by both and executed as drawn.

2. 02

   Decisions in DMN

   Rules that change often go into DMN decision tables. The business can read them, and the process calls them by their decision ID.

3. 03

   Java job workers

   Each service task names a job type, and a Java worker takes those jobs. We write workers that are idempotent, so a retry does no harm.

4. 04

   Connectors

   Connectors call REST services and message brokers from the model itself. Where no connector fits, a job worker does the work.

5. 05

   Self-Managed or SaaS

   Self-Managed on Kubernetes or Camunda SaaS, with Operate, Tasklist and Optimize. From 8.8, Zeebe is the engine inside the Orchestration Cluster.

6. 06

   Agentic orchestration

   AI agents act inside the process through the Camunda AI Agent connector. Rules, approvals and the audit trail stay in the BPMN model.

// BPMN: the service task names a job type
// <bpmn:serviceTask id="CheckCredit"><bpmn:extensionElements>
//   <zeebe:taskDefinition type="check-credit" retries="3" />
// </bpmn:extensionElements></bpmn:serviceTask>
client.newWorker()
    .jobType("check-credit")
    .handler((jobClient, job) -> {
      String customerId = (String) job.getVariablesAsMap().get("customerId");
      boolean approved = creditService.check(customerId);
      jobClient.newCompleteCommand(job.getKey())
          .variables(Map.of("approved", approved))
          .send().join();
    })
    .open();