this post was submitted on 14 Jun 2026
32 points (100.0% liked)

Selfhosted

60451 readers
788 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
32
How do you manage you DB in a docker environment? (sh.itjust.works)
submitted 3 weeks ago by Croquette@sh.itjust.works to c/selfhosted@lemmy.world
34 comments fedilink hide all child comments
 

Hello,

As the title suggests, how do you manage your DBs for docker services.

Do you spin a new DB for every new docker cluster or do you have a centralized DB that is accessible to the docker clusters.

What are the pros and cons of both method?

For the moment, I spin a new DB for every services as I feel it is easier to backup the service in case of a problem.

you are viewing a single comment's thread
view the rest of the comments
[–] placebo@lemmy.zip 2 points 3 weeks ago (2 children)

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.

[–] Croquette@sh.itjust.works 2 points 3 weeks ago

You say it's easier to back up tightly coupled services and databases, but why?

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.

[–] motruck@lemmy.zip 1 points 2 weeks ago

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.