What Camunda Platform Architecture are you?

Camunda Community Podcast

In this episode, Camunda Developer Advocate Niall Deehan walks us through selecting from the various options for a Camunda Platform architecture.
Springboot? Camunda Run? Embedded? Distributed? Java? Not Java?
The options are non-trivial, but Niall walks us through the answer to the question: "Sure, it depends - but what does it depend on?" in a way that reveals the various factors and their influences on architecture.
The BPMN diagram for this episode is available on GitHub.

---
Visit our website.
Connect with us on LinkedIn, Facebook, Mastodon, Threads, and Bluesky.
Check out our videos on YouTube.
Tweet with us.
---
Camunda enables organizations to orchestrate processes across people, systems, and devices to continuously overcome complexity and increase efficiency. With Camunda, business users and developers collaborate using BPMN to model end-to-end processes and run sophisticated automation with the speed, scale, and resilience required to stay competitive. Hundreds of enterprises such as Atlassian, ING, and Vodafone design, orchestrate, and improve business-critical processes with Camunda to accelerate digital transformation.
---
Camunda presents this podcast for informational and entertainment purposes only and does not wish or intend to provide any legal, technical, or any other advice or services to the listeners of this podcast. Please see here for the full disclaimer.

Kapitel

1. Introducing Niall Deehan (00:01:53)

2. Deciding on your Camunda Architecture (00:07:58)

3. Option 1: Embedded Engine (00:12:25)

4. Option 2: Engine as a Service (00:20:24)

5. Polyglot job workers (00:23:00)

6. Optimize and Cockpit (00:29:56)

7. Option 2 Architecture described (00:36:34)

8. Five Quick Questions for Niall (00:45:13)