A client of mine is setup using normally 7 Linode VMs..
Due to ahem.. "issues" related to a network change in the DC, that's going to balloon out to around 10 or 12 for a little while, then shrink back down.
- 2x load balancers (1 is active for public traffic; backup for private traffic; 1 is active for private traffic; backup for public traffic);
- 3x DB cluster nodes (currently at 5 due to aforementioned issues);
- 2x Web/App nodes
Currently planning to adapt this into 3 distinct sites with simpler 1x web/app + 1x db per-site to move the redundancy point out to specific DCs rather than to individual roles within a single DC.
I run many different web apps off a single VPS, a Linode with Debian. Deployment is pushing to a git repo on the server, which has a hook that simply kills the server. Supervisord ensures apps are restarted automatically. Caddy proxies everything based on domain.
Litestream backs up the databases automatically to S3 compatible storage, and linode offers automatic snapshots of the VPS.
My deployment process is git push and that’s it. If I need to setup a new webapp, I just clone the repo, add to supervisor and caddy config, and I’m good to go.
If I need to do CI, I use GitHub, which just git pushes to the server to deploy.
Due to ahem.. "issues" related to a network change in the DC, that's going to balloon out to around 10 or 12 for a little while, then shrink back down.
- 2x load balancers (1 is active for public traffic; backup for private traffic; 1 is active for private traffic; backup for public traffic);
- 3x DB cluster nodes (currently at 5 due to aforementioned issues);
- 2x Web/App nodes
Currently planning to adapt this into 3 distinct sites with simpler 1x web/app + 1x db per-site to move the redundancy point out to specific DCs rather than to individual roles within a single DC.