Elastic, multiple camunda spring boot instances and shared database.

[andrei....@gmail.com]

Hi camunda team.

Support of spring boot configuration for camunda is excellent. I have interesting question.

We are building modular microservices environment with spring boot.

Each set of processes for departments will be packaged in spring boot container + REST API to work with data (data will stored separately) + web apps for GUI.

Each set of processes will be connected to single database (oracle or postgre) and mapped to separate schema (financial, legaldepartment, etc.)

My question is:

If we have performance problems - can we increase number of running springboot modules and will this make problems to shared database. As I understood from camunda docs - shared db feature available only for Shared Camunda engine, which included in EE releases. For springboot configuration used embedded engine which is not supported for shared db. Will we have any problems if we run multiple instances of same spring boot containers, pointed to same schema/database?

How to configure/split spring boot modules to have possibility to run them on shared DB and have elastic environment (start/stop additional instances to process more/less requests)?

[Philipp Ossler]

Hi Andrei,

what shard db features do you mean? Note that you can use a clustered process engine with the community edition. 

Please describe your performance problems. What are the reasons?

To the architectur, have a look at the cluster model [1]. Your microservices would look like:

You have multiple instances of the same microservice which share the same db scheme. So the process engine runs in a homogen cluster mode since the other microservices uses their own db scheme. This should work without problems. Just use the same data source for the microservice instances. [1]

Note that there is a whitepaper [2] from camunda about microservices you might be interested in.

  

Greetings,

Philipp

[1] https://docs.camunda.org/manual/7.4/introduction/architecture/#clustering-model

[2] https://network.camunda.org/whitepaper/16