Dedicated pod for each process application.

Camunda 8 Topics
1

Is it possible to have dedicated pod for each process application in camunda 8!
this way we can scale up and down the pods for each application when necessary.

2

@Shamanth ,

Yes, it is possible and often recommended to have a dedicated pod for each worker application in Camunda 8—especially when using Camunda 8 Self-Managed with external job workers (like Java workers). This aligns well with microservices principles, allowing for independent scaling, deployment, and resilience per application.

Why Use Dedicated Pods per Worker Application?

  1. Independent Scaling:
  • Scale each application up/down based on its workload independently.
  • Optimizes resource usage.
  1. Isolation:
  • Easier to isolate faults and troubleshoot issues.
  • Better control over resources (CPU/memory) per application.
  1. DevOps Flexibility:
  • Different teams can own and deploy their own workers.
  • Enables true CI/CD for individual apps.
  1. Observability:
  • Easier to collect and analyze metrics per app.
  • Prometheus/Grafana dashboards can be app-specific.

Camunda 8 has the following components (assuming self-managed setup):

  • Zeebe Broker Cluster (workflow engine)
  • Operate, Tasklist, Optimize (monitoring and UI)
  • External Job Workers (Java or others) – you write these

image
image692×136 6.76 KB

4

Hi @aravidhrs,

Thanks for your response. I have a follow-up query.
Is it possible to have a dedicated zeebe process engine pod for each process application. A zeebe engine pod which runs just one process application? Is it possible to configure our cluster like this?

5

@Shamanth , You can’t have Zeebe engine component alone. If you need dedicated workflow engine for your process application then you need to create new camunda cluster for each process application but which is going to be expensive. Instead you can consider enabling multi-tenancy in the Camunda cluster which is available in both Self-managed and Saas versions.