Implement own JobExecutor

camunda-community-hub / micronaut-camunda-platform-7

Integration between Micronaut and Camunda (Workflow Engine). We configure Camunda with sensible defaults, so that you can get started with minimum configuration: simply add a dependency in your Micronaut project to embed the workflow engine!

https://camunda.com/blog/2021/07/automate-any-process-on-micronaut/

Apache License 2.0

75 stars 31 forks source link

Implement own JobExecutor #112

Closed tobiasschaefer closed 3 years ago

tobiasschaefer commented 3 years ago

Currently, we're using the org.camunda.bpm.engine.impl.jobexecutor.DefaultJobExecutor which manages its own threads. As suggested by the comment in DefaultJobExecutor we should implement our own JobExecutor.

Advantages

better usage of resources because then we only have a Micronaut Managed Thread Pool, i.e. not multiple thread pools claiming the same limited resources.

arolfes commented 3 years ago

To compare with https://github.com/camunda/camunda-bpm-platform/blob/master/engine-spring/core/src/main/java/org/camunda/bpm/engine/spring/components/jobexecutor/SpringJobExecutor.java

arolfes commented 3 years ago

Hi @tobiasschaefer

the changes for loadtesting with postgres are in this branch https://github.com/arolfes/micronaut-camunda-bpm/tree/Postgres-Prometheus-Grafana