Dynamic manage multi-tenant Process engine in combination with Spring Boot?

[aravindhrs]

@StephenOTT related topic i created here. Multi-tenancy configuration / ProcessEngine & Datasource per tenant

@jangalinski

I get your point … but still, deployment aware already works when I run two spring boot camunda apps against the same database.

Our current setup is like above @jangalinski mentioned, and multi-tenancy was handled with discriminator column. Default process engine was used to manage all tenant requests.

We won’t use any xml files to configure process engines.

@StephenOTT

I am all for not having multiple engines. Was just pointing out a valid / interesting use case for having multiple engines in a single app.

@jangalinski

I get multi tenancy, but I still do not have a good use for multiple engines per spring boot runtime …

• Our current deployment is based on standalone process engines(REST api communication), running two spring boot camunda apps(Amazon EC2 instance) against the same database. It works fine.

• Now the use case is, we got many tenants, lets say 50 tenants (tenant per DB/tenant per process engine). In this scenario we can’t run single process engine per spring boot runtime. It will results in 50 EC2 instances which is more expensive.

• So we decided to create multiple process engines per tenant in one spring boot runtime. Using this approach, we can scale spring boot app will result in less number of EC2 instances.

• If we have process engine per tenant in per spring boot app, thinking of scaling perspective will result in ending up with lots of resource usage.