We are building organization-wide Workflow services and going to use Camunda for it.
In our organization, there are a lot of departments and they have a lot of processes. So instead of all integrating with Camunda (or other tools) for process orchestration, we decided to build workflow service which will provide orchestration capability via rest APIs.
We are going to create springboot microservice, exposing rest APIs. And internally, we are going to use Camunda Java APIs. For data customer segregation, we are goint to use multi-tenancy capability provided by Camunda. It means each department will be onboarded as a tenant. Onc tenant may have more than one process. Each process may have multiple versions running in paralel.
For deploying process defination to the engine, we are going to use REST API, so that process defination can be deployed without restarting an engine instance.
When I log in to the cockpit, I am able to see the deployment tab. Where all the deployments are visible.
- What does the deployment entity mean?
- Should I create a new deployment for each process definition upload?
- Can I deploy multiple modes under one deployment?
- If I create too many deployments under one engine (one deployment per model), how it will impact the performance?