Try moving one of the services out of your combined database.
With a containerized database you stop it. Copy everything over to the other machine and start it.
With your set up you have to dump the database and import it on the other system.
You also get easier coarser performance isolation on a per service basis.
Oh yeah and OOM-killa ever get your database down. Well now they won’t all die at once.
The overhead of running another database instance is easily with the above advantages.
Croquette@sh.itjust.works 2 months ago
Because it is set and forget in my docker compose. I can backup the container and bring it down without affecting other services.
But that is my inexperience talking and this is is why I wanted to see what other people were doing, and having perspective like yours to learn.