What about databases?
I think this is the first of these stories that I have realized has no relevance to me BEFORE I click on the link rather than after. (Currently working on Kubernetes stuff, but all the GKE posts here have not been that useful, though I have played with GKE and like it)
My takeaway/distillation from this article basically comes down to this:
* GKE clusters currently can be only in 1 region (say, us-central1)
* But you can create multiple clusters around the world, and deploy the same app on them
* Google Cloud provides global anycast IPs for load balancers
* Anycast IPs are routed to the closest PoP/datacenter available to the visitor of your application
* Then, the traffic is routed to the closest GKE cluster (without leaving Google's private worldwide network)
* This way, you serve to the user from the nearest cluster
* If a region goes offline (disaster scenario) or is under high load, the load balancer will start sending traffic to other nearby clusters
I deployed the sample demo app provided at with this at http://35.190.71.87/ (probably won't work in a month or so). Depending on where you're visiting, you'll be routed to the closest datacenter the app is deployed in.
The demo app source code is here: https://github.com/GoogleCloudPlatform/k8s-multicluster-ingr... You can try it out yourself if you have a GCP account.
Disclaimer: I work on GKE at Google.