Selfhosted

59923 readers

560 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

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How do you manage you DB in a docker environment? (sh.itjust.works)

submitted 1 day ago by Croquette@sh.itjust.works to c/selfhosted@lemmy.world

28 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

[–] motruck@lemmy.zip 1 points 15 hours 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.