Production deployment clarifications

Hello,

I am studying the Camunda deployment options and I want to make sure I have understood what is going on the finally manage to choose the proper way for my implementation.

First of all, I am firstly looking for a docker installation. As I see there are two Docker images / distributions (Camunda Run and Tomcat). From these two, the Camunda Run dist is better for a production environment since it provides a “production.yml” file that can be used for further configuration.

  • Tomcat dist does not provide any option like this?

In addition to that, I see the camunda spring-boot project which I understand that gives more flexibility and the option to potentially extend camunda’s code. However these is no Docker option for this and I should dockerize it for my needs after making the project, right? Furthermore, by exploring “Camunda Automation Platform 7 Initializr” I see only the option of a H2 database (in memory or on disk). Is this the only solution? Can’t this approach use a postgres db?

Finally, as a general comment which of all these are suggested for production?

Thank you in advance!

Go through the Blog to understand the distributions:

you can build your own docker image from the sprint boot starter code and vendor db of your choice. By default it comes with H2, but you can change the DB of your choice.

2 Likes