For most applications the overhead of running a second DB server is negligible.
Comment on 18% of people running Nextcloud don't know what database they are using
u_tamtam@programming.dev 16 hours agoSelf hosting doesn’t mean “being wasteful and letting containers duplicate services”. I want to know which DB application X is using, so I pool it for applications Y and Z.
Ajen@sh.itjust.works 15 hours ago
absentbird@lemmy.world 14 hours ago
And if it’s SQLite (which I believe is the default) it’s really just reading and writing a file on the file system.
tburkhol@lemmy.world 3 hours ago
This is one of my pet peeves with containerized services, like why would I want to run three or four instances of mariadb? I get it, from the perspective of the packagers, who want a ‘just works’ solution to distribute, but if I’m trying to run simple services on a 4 GB RPi or a 2 GB VPS, then replicating dbs makes a difference. It took a while, but I did, eventually, get those dockers configured to use a single db backend, but I feel like that completely negated the ‘easy to set up and maintain’ rationale for containers.
u_tamtam@programming.dev 53 minutes ago
Precisely what pre-devops sysadmins were saying when containers were becoming trendy. You are just pushing the complexity elsewhere, and creating novel classes of problems for yourself (keeping your BoM in control and minimal is one of many others that got thrown away)