[boulos]

Disclosure: I work on Google Cloud.

Awesome writeup! I’ve seen lots of customers do similar “let the packets spray” on both GCP and AWS. Interestingly, it’s one of the reasons I was so excited for our “ILB as next hop” [1] feature. Routing to the Service within the same Zone, unless there’s a failure at which point you wish to go elsewhere in the Region is a common pattern. I’m excited to see where Traffic Director and similar service mesh patterns lead in this space. Having everyone need to roll this by hand, seems needlessly redundant.

As an aside, another personal surprise when I got into an argument over Zone-to-Zone pricing: GCE only charges for one-way while AWS charges for send and receive. We should clearly do better marketing :).

[1] https://cloud.google.com/load-balancing/docs/internal/ilb-ne...

[dilyevsky]

gcp services are always great on marketing booklets but tend to have less than stellar reliability and you gotta read the fine print. A perfect example is ilb only supports max 250 backends and is basically unusable for mutli-regional setups.