this post was submitted on 14 Jun 2026
40 points (97.6% liked)
Selfhosted
59923 readers
778 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Given that database management systems already provide clear separation between services in the form of databases, users, and permissions, I see no need to spin up new database instances for each individual service. You say it's easier to back up tightly coupled services and databases, but why? I find it easier to back up a single database server than multiple servers.
The real concern with shared databases is performance: some services, under certain conditions, can generate load that degrades database performance for everyone. But that's usually a problem for large enterprises, not self-hosters.
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.
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.