IssueTracker

Engineering is aware of this request and are investigating it. There is no ETA for the release. In the meantime it may be possible to create multiple Flex apps in different regions, and use a Compute Engine load balancer to route requests to each app by placing them in compute engine networks.

Our project (goldappybuilder) is set for us-central. Our European users are complaining and indicating that response time, at certain times, is tooo slow; up to 10 seconds. Please let us know how to setup for cross-region load balancing. Also, on Aug 25, you indicated "no ETA"; any status update? This is really urgent. Thanks

We would really like to have cross-region load balancing for GAE Standard Environment apps. i.e. the ability to have, in the same project, US and EU hosted GAE Std front ends, and then have each hit their respective back-end VMs (US to US, EU to EU). Some of our EU customers have requirements to host their data within the EU, and if we do so now the US GAE std severs have to talk to the DBs in EU (slow). We can't easily hack this with multiple projects due to security keys, datastore tables and storage buckets tied to the first project.

We will need this in the future as our user base grows.

We are also very interested in this. Is there any updates on this?

Any update on the status of this?

Any update on cross-region app engine on same project? We just need two regions (US and EU) sharing  the same Datastore info (for meta data) but accessing different dedicated back ends (in either US or EU) that run on Compute Engine in those locations respectively.

The last comment from Google on this was "Engineering is aware of this request and are investigating it. "
Below is the implementation we can envision in case this helps in the design stage:

Say the starting point is a project with App Engine standard java 8 in the US Central region. That project has a domain tied to it now called company.com that points to the US Central App Engine deployment.

We would like to create another App Engine deployment in that project that is identical but hosted in Europe. We would establish ANOTHER domain called company.eu and www.company.eu would then point to our App Engine Europe deployment (maybe internally this is done simply by having both projectid.appspot.com and projectid.appspot.eu or maybe its easier to have projectid.region.appspot.com and custom domains map to those, or maybe for backward compatibility its region.module.projectid.appspot.com and the region and module must be explicitly specified only if a project uses multi-region app engine?).

Our EU customers would access www.company.eu, hit app engine Europe, which talks to databases (compute engine) deployed in the EU and cloud storage located in the EU. Our US customers hit www.company.com and hit app engine US Central which talks to databases (compute engine) and storage buckets deployed in the US.

If a US customer tries to log in to the company.eu domain, we can see that Account X is configured for US and simply redirect to company.com. Likewise if an EU customer tries to log in to company.com with an EU configured account, we simply redirect to company.eu.

So long as both app engine US and app engine Europe (in the same project) share the same Datastore, this setup is perfect for us.

Feel free to email me for clarification if needed. Thank you.

Any update on having multiple App Engine regions within a single project all sharing the same datastore?

Is there any update on when this might enter beta?

Is there any update on this?

Any updates?

This would be super great to have !

This would be a huge upgrade to app engine standard. The best scale to zero spin up millisecond service out there

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

Come on Google, what's going on? So many issues with zero updates or response.. This is a must have!

+1

+1

+1

+1

+1

+1

+1

+1

+1

This is also needed for Google App Engine Standard Environment applications.