6 ms·
Why does he think GCP regions aren't the same as AWS regions?
by icco 6y ago
Why does he think GCP regions aren't the same as AWS regions?
- johncolanduoni 6y agoI would agree that they are but since VPCs and storage buckets can span multiple regions on GCP I could understand being confused.
- campers 6y agoIt seems he means in terms of networking as in the prior comment: "I was particularly impressed by how you could set up “global” routing, which means load balancing against resources that run in multiple Google regions" GCP has a global networking plane, so in a single GCP project you can have resources and networking configured together from every region/AZ around the world. In AWS (which I don't use so don't quote me, and please correct me) regions are very separate from each other. You would need to create separate accounts for resources in different regions and then configure the networking between them.
- jpgvm 6y agoThe big difference is AWS doesn't provide a GSLB (global server load balancing) service outside of Cloudfront. GCP on the other hand provides L7 GSLB. You still need to create VPCs in each region and manage those but broadly speaking building a multi-region architecture with GCP is a lot better. Hell multi-zone is also easier in GCP because there are more regional primitives available.
- mwarkentin 6y agoWould https://aws.amazon.com/global-accelerator/ https://aws.amazon.com/global-accelerator/ be what you’re talking about?
- jpgvm 6y agoI haven't actually used this but this looks very similar to Google GSLB actually, in which case that is great news.
- nijave 6y agoAWS also let's you DNS load balance on top of regional load balancers (there is some DNS traffic management with health check integration)
- jpgvm 6y agoYes, R53 can help you build your own GSLB by using DNS health checks and georouting but it's not the full picture.
- tatersolid 6y agoI think the bigger difference is that layer-2 really doesn’t exist in GCP or Azure but it sort-of does in AWS. This is why virtual nets can span geographic or AZ boundaries in non-AWS clouds; they always basically do layer-3 routing even for “local subnet” traffic.
- Slippery_John 6y agoThere are differences in redundancy and isolation that could impact your resiliency strategy. An AWS zone can include multiple data centers that are isolated from other DCs in the same zone. A region is then a collection of those zones, and each zone in a region could be as much as 60 miles away from another. [0] A cursory reading of the GCP docs indicates that a GCP region is more equivalent to an AWS zone, but that may be a misunderstanding based on the more abstract language used. [1] Azure also seems to treat a region like AWS treats a zone, but they also have a concept of paired regions for more redundancy [2]. I can't seem to find details on the isolation guarantees for their DCs / Zones / Regions / Pairs though. [0]: https://aws.amazon.com/about-aws/global-infrastructure/regions_az/ https://aws.amazon.com/about-aws/global-infrastructure/regio... [1]: https://cloud.google.com/compute/docs/regions-zones/ https://cloud.google.com/compute/docs/regions-zones/ [2]: https://docs.microsoft.com/en-us/azure/best-practices-availability-paired-regions https://docs.microsoft.com/en-us/azure/best-practices-availa...