2 ms·
This "one global network" instead of, say, AWS's regions, was a selling point for Google against AWS. Big enterprises loved loved LOVED not having to think in t
by Terretta 4y ago
This "one global network" instead of, say, AWS's regions, was a selling point for Google against AWS. Big enterprises loved loved LOVED not having to think in terms of regions.
Recently, AWS seemed to be finally capitulating to sales demand and globalizing things.
I wonder if that will slow now there's a competitor incident report with the answer being region sharding.
- my123 4y ago> Recently, AWS seemed to be finally capitulating to sales demand and globalizing things. Short answer: no. cross-region services are few and far between. Long answer: https://docs.aws.amazon.com/whitepapers/latest/aws-fault-isolation-boundaries/abstract-and-introduction.html https://docs.aws.amazon.com/whitepapers/latest/aws-fault-iso...
- ckdarby 4y agoWhile correct that few services out of the total are cross-region I think only a few need to be to get the bulk of functionality. If restoration(S3 & snapshots) and networking are both cross region it is possible to avoid outages without much effort. S3 already supports global endpoint, cross regional replication and even manual failover. RDS supports cross regional snapshots. Networking has a bunch of options for crossing regional now. If you're worried about AWS global endpoints and services going down the design is always around pointing to the global but being able to fall back to a specific region up. At this point can just run EKS in N regions, have the clusters stateless and treat RDS+S3 for state.
- jfindley 4y agoNote that the region sharding is just about the config push, the network itself isn't getting shareded. The goal is to ensure a bad config push can't impact >1 region (in theory), not to segregate the actual network.