You should also be looking at multi-CDN.
You should also be looking at multi-CDN.
Yes, but Google takes this to another level, all their load balancers are one single giant point of failure.
> This is why lots of folks go multi-cloud.
Or, just use AWS, where each region is almost entirely independent (some specific APIs are global by their nature, like creating a new S3 bucket), but you shouldn't be using those APIs on your run-path.
Yes, it is less convenient (and it must be less convenient for AWS to build things this way than for Google who seem to prioritise their development experience over customer availability), but new features from AWS are making it easier to deploy to multiple regions and use cross-region failover.
GLB is also distributed but clearly is a single "service" within GCP with weaknesses that can take down the entire thing, probably because of the complexity and integration involved in its architecture. It's fast and convenient but the reliability just isn't there yet.
The only challenge is that you need global geographic load balancers and that means F5 and at least a million dollar.
Also, you will find out later that some dependencies were only running in a single location and services failed with the datacenter.
Everyone always forgets about DNS, until Dyn dies.