So true. HN often admires complexity for complexity sake.
Even without cloudflare, a static website on 5 VPS from 5 different provider on 5 different continents with a Round Robin DNS and a low TTL will get you most of the bangs for bucks
Add geoIP to the mix (like from Azure) and you're golden, even if you are just scp'ing files to 5 VPS.
If a DC burns down, remove the A record (or even better: have a script do it for you) and reroute to the remaining 4.
That’s funny, sometimes when I visit your site, I get an HTML page that references script files and resources that come back as 404s. I wonder if it’s possible I’m hitting the site during a deployment and getting the new HTML page from one of your servers, but then the resource requests are going to a different server which hasn’t received the new version yet.
I guess occasional broken images and script failures are unavoidable though. You’d need like, some dev ops engineers to solve a problem of that complexity.
Even without cloudflare, a static website on 5 VPS from 5 different provider on 5 different continents with a Round Robin DNS and a low TTL will get you most of the bangs for bucks
Add geoIP to the mix (like from Azure) and you're golden, even if you are just scp'ing files to 5 VPS.
If a DC burns down, remove the A record (or even better: have a script do it for you) and reroute to the remaining 4.
Extra bonus: you can fire the DevOps team :)