> high-availability, which IMO is absolutely essential for any serious business Depends very much on the business. You can have downtime-free deploys on a sing

> high-availability, which IMO is absolutely essential for any serious business Depends very much on the business. You can have downtime-free deploys on a single node, and as long as you've setup a system to automatically replace a faulty node with a new one (which typically takes < 10min) then a lot of businesses can live with that just fine. It's not like that cheap VM goes down every day, but just in case you can usually schedule a new instance every week or so to reduce the chance of that happening. > How do you handle regional replication? For backup purposes, you'd use litestream. Very easy to use with something like systemd or as a docker sidecar. For performance purposes, if you do need that performance you'd obviously use something else. Depending on the type of service you have, though, you can get very far with a CDN in front of your server. > Or you could simply use an off the shelf DBMS like Postgres or even MySQL. If you need it, sure.