Which component of Camunda are available in SE version. I need to deploy the Camunda with Saga orchestration in AWS EKS. Can I use SE version or EE version has to be used??

Which component of Camunda are available in SE v/s EE version version. I need to deploy the Camunda with Saga orchestration in AWS EKS. Can I use SE version or EE version has to be used??
Also can we make Camunda highly available in SE version when we deploy it in AWS EKS?

Hi @seasonchange - if you want to use Camunda in production, you need an enterprise license. Zeebe - the process engine itself - is source-available and you are free to use it in production by itself; however, the other components (Operate, Optimize, Tasklist, etc.) require a license.

1 Like

Thanks Nathan for replying. So it means we cannot make saga implementation using Camunda (with only Zeebe component) work without these components(Operate, Optimize, Tasklist, etc.). Camunda implements Saga with help of these components only. Is my correct understanding ?

Hi @seasonchange - Operate, Optimize, and Tasklist are not required to build, deploy, and run a process. They make managing your processes easier, and come with development tools that help speed up the development process, but you can run processes with just Zeebe.

However, if you want to use Operate, Optimize, Tasklist, etc. in production, you need an enterprise license.

1 Like

Thanks for replying Nathan. I have few more queries based on my analysis on usage Camunda for Saga orchestration in AWS EKS region.
My questions for Camunda are as follows…

  1. Can we achieve high availability (of Camunda) with using only the Zeebee component of Camunda.?
  2. Can we connect Camunda to postgres DB. To achieve high availability can multiple camunda be connected to single postgres db in AWS EKS where each camunda is deployed as single pod in 2 regions?
  3. I can see that Camunda cannot be connected to NoSQL (like mongoDB) db. right?

Hi @seasonchange -

  1. Yes. Zeebe has a cloud-native architecture, so you can distribute the cluster and brokers as needed. Here’s a good resource for learning about how Zeebe works: Architecture | Camunda 8 Docs
  2. No, not in the way you’re asking. Each broker has it’s own internal database, and then the cluster exports it’s data using an exporter. I don’t think there’s a Postgres exporter yet, but it’s possible to write one. However, that data would be consume by your own services, not by Zeebe. If you use an enterprise license, the other applications (Operate etc.) all use Elasticsearch (with OpenSearch support in active development). You can still export data to Postgres but those Camunda services won’t be using Postgres.
  3. See the answer above. Zeebe works with it’s own internals and you cannot replace them, but you can export the data wherever you need with an exporter.

Hope that helps!