Hacker News Reader

I may be completely off here, but isn't this due to their underlying architecture decisions? That is, AWS from the start has kept all regions completely separate, so that problems in one region do not influence another. But GCP has has issues with failure across regions IIRC.

View on HN

Having a software defined networking spanning across regions and failure cascades across regions are two different things. There's nothing preventing a vendor from presenting to you a single network, while they are actually distinct networks.

Having distinct networks in different regions encourages you to architect your application in a fault tolerant way.

Or the contrary. In most cases there is something to synchronize between regions, like a replica of the data.

With difficult interconnection of regions, it makes it somewhat harder to do, and it can easily end-up with "meh, AZs are good enough".

It is also potentially due to Google owing their private fiber backbone that connects all regions and as well as their software Defined Network that allow high bandwidth and low latency routing of packets across regions.

AWS also has a private backbones and offers (or will soon) VPC peering run on top of this.

Reply on news.ycombinator.com