NGram

That’s a very elegant way of doing it! I need to do something similar with my setup one day. Having everything hosted in my home gives me the most control but also a lower availability than if I ran everything in someone else’s datacenter. Currently an outage means that browsers and other clients just time out which is not very informative. Have you explored any other options? I was thinking of spinning up a dedicated VM somewhere to handle this and automatically switching over DNS entries at the same time (maybe automatically update DynDNS when the VM boots).

WRT is this relevant to selfhosted: I think some people will disagree, but Cloudflare is still selfhosting. It’s not localhosting, but as long as it’s services that you provision yourself it’s selfhosting.

I too spin up a new DB for every service that needs one. It makes maintenance less intrusive since I only have to shut down one service at a time to update or do a full file backup and I can safely tweak the DB config to best suit the service without worrying about negatively impacting other services on the same DB. I also like the flexibility to choose the best DB for the service, e.g. I use Postgres for a lot of the services I develop but they do also support MySQL/MariaDB, but I have other services that are more tested on MariaDB.

I’d imagine having one database for everything could eventually cause performance problems across all services if the database gets too big or clunky or queries get too complex, even if just one service is causing the problem.

I also run a lot of physical servers (I have about 10 low power computers I use as servers right now) so having a dedicated DB per service allows me to get better performance since the DB can be on the same machine as the service. Not that they need high performance, but it also helps with the efficiency.