Is it possible to separate history tables with the standalone engine in Camunda7?

Hi Team,
We had recently migrated from embedded to standalone engine, in the embedded engine configuration we implemented custom history event handler to separate history tables from runtime tables and store these in different database to improve performance, can we do this similar thing using standalone engine?

If it can be done do we need to change some configurations or need to change the code?

If code need to be changed, right now we are running the standalone engine using a docker image, then we need to deploy our own service as a camunda standalone after making changes? Is the camunda-platform-run available as a git repository to fork and make some changes?

Any inputs are appreciated and for the tech stack we are using for the other services, we recently migrated to quarkus from spring-boot, actually do you some limitations in support for quarkus we shifted to standalone engine.

1 Like