[google-appengine] Re: Google App Engine multiple regions

I agree - this function have to be there already also "google functions" are regional  https://firebase.google.com/docs/functions/locations if I see it right "aws lambda, aws elasticbeanstalk, aws cloudformation" support loadbalancing 勞

[google-appengine] Re: Google App Engine multiple regions

I agree - this function have to be there already also "google functions" are regional  https://firebase.google.com/docs/functions/locations if I see it right "aws lambda, aws elasticbeanstalk, aws cloudformation" support loadbalancing 勞

[google-appengine] Re: Google App Engine multiple regions

We need this too for GAE Standard Environment... basically an GAE in EU going to backend databases hosted on VMs in EU, and GAE in US going to backend databases hosted on VMs in US. On Monday, June 20, 2016 at 5:13:12 AM UTC-4, Yon Dev wrote: > > I am evaluating whether GAE would be a good fit

[google-appengine] Re: Google App Engine multiple regions

Hey Pavelescu, The page you link, "Creating Cross-Region Load Balancing", from our docs, is relevant for Compute Engine instances, rather than App Engine. While App Engine Flexible Environment apps run on Compute Engine VM's, they deploy only to the same region that you select for your App

[google-appengine] Re: Google App Engine multiple regions

Hello Tom, I've just came across this section in the gcloud documentation: https://cloud.google.com/compute/docs/load-balancing/http/cross-region-example Isn't this exactly what Yon tried to achieve? Thanks, Razvan marți, 21 iunie 2016, 15:17:59 UTC+3, Tom Walder a scris: > > You cannot load

[google-appengine] Re: Google App Engine multiple regions

Kaan, I believe the ping time to appspot.com domains is not indicative of the actual smallest response time as it only pings the entry point of Google's global edge network. Once your request is inside Google internal network, it will then travel to your GAE instances and back. If you ping an

[google-appengine] Re: Google App Engine multiple regions

Thank you all for your insight and answers. I will take it under consideration. Yon Den onsdag 22 juni 2016 kl. 17:38:22 UTC+9 skrev Kaan Soral: > > I think one way or another, there's going to be a delay, why do you need > to minimise the delay so much? > > Even if the instances were spread

[google-appengine] Re: Google App Engine multiple regions

I think one way or another, there's going to be a delay, why do you need to minimise the delay so much? Even if the instances were spread over the world, I'm guessing there would be a smaller data access delay in most cases I'm way outside US, my users are closer to EU, yet my appengine

[google-appengine] Re: Google App Engine multiple regions

You cannot load balance between US and EU using "conventional" load balancing. There might be some thoroughly complex way to do it with localised DNS responses. However, it would be 2 distinct App Engine projects. To be honest if cross-region load balancing is a need, App Engine is probably

[google-appengine] Re: Google App Engine multiple regions

Hello Nick, Thank you for your answer. I might be misunderstanding something so please correct me if I am wrong. I can only upload 1 app engine instance per project. So if I want to deploy to both the US and EU I will have to create 2 different projects. And if I were to create multiple

[google-appengine] Re: Google App Engine multiple regions

Hello Nick, Thank you for your answer. I might be misunderstanding something so please correct me if I am wrong. I can only upload 1 app engine instance per project. So if I want to deploy to both the US and EU I will have to create 2 different projects. And if I were to create multiple

[google-appengine] Re: Google App Engine multiple regions

Hey Yon, App Engine instances are scaled in zones within the region the application is created in . If you'd like to follow a pattern which others have made use of, you can deploy another project in the EU to handle traffic