Skip to content
This repository has been archived by the owner on Sep 2, 2022. It is now read-only.

More datacenters for the shared cluster #61

Closed
2 of 3 tasks
schickling opened this issue Jan 8, 2017 · 20 comments
Closed
2 of 3 tasks

More datacenters for the shared cluster #61

schickling opened this issue Jan 8, 2017 · 20 comments

Comments

@schickling
Copy link
Member

schickling commented Jan 8, 2017

In order to guarantee even better response times there should be additional datacenters in...

  • US East
  • US West
  • Asia Pacific

Note that private clusters can be hosted in any of these 12 AWS regions:

  • us-east-2
  • us-east-1
  • us-west-2
  • us-west-1
  • ca-central-1
  • eu-central-1
  • eu-west-2
  • eu-west-1
  • ap-northeast-2
  • ap-northeast-1
  • ap-southeast-2
  • ap-southeast-1
@marktani
Copy link
Contributor

marktani commented Jan 8, 2017

See #59 as well.

@malonehedges
Copy link

Here to request US West specifically. I'll be building apps primarily used in the west coast and would benefit greatly from that region.

@sedubois
Copy link

And could you also please remind where the current data center is? Ireland?

@marktani
Copy link
Contributor

marktani commented Jan 16, 2017

That's right. You can read more about our technology/data center setup here: https://www.graph.cool/docs/faq/graphcool-technology-ul6ue9gait

@mikeroelens
Copy link

+1 for US East. us-east-2 specifically.

@sorenbs
Copy link
Member

sorenbs commented Mar 3, 2017

@mikeroelens Can you elaborate on why us-east-2 specifically is important? Would a west coast datacenter provide any value to you at all?

@tomByrer
Copy link

tomByrer commented Mar 4, 2017

@sorenbs If someone already has infrastructure in a particular AWS datacenter, it would be a performance benefit for all services would be in the same datacenter. You know, TCP/IP latency and all :)

I'd suggest building a survey (Google Docs work fine, turn on random shuffle) for current customers to vote on what DC is best for them. Maybe a first & second choice if you can only support 1 US DC.

@sedubois
Copy link

sedubois commented Mar 4, 2017

If I understand right, this issue proposes to have new locations, and the user would simply manually decide in which datacenter their project would be hosted, right?

How about websites with global presence (like the one I'm working on), what is the current and long-term strategy to ensure a fast response time for users from all major regions on Earth? I guess the data must then be replicated and kept synchronized across the various datacenters, is that planned?

@abefetterman
Copy link

abefetterman commented Mar 9, 2017

Casting a vote for us-west-2 ! This will minimize average latency better than us-east, and be a benefit to the west coast developer community.

@stevewpatterson
Copy link

+1 for us-west

@sorenbs
Copy link
Member

sorenbs commented Apr 17, 2017

We are currently beta-testing regions in us-west-2 and ap-northeast-1. Please let me know if you want to be involved :-)

@aurnik
Copy link

aurnik commented May 17, 2017

@sorenbs If you need any help with US West I'd love to help!

@marktani
Copy link
Contributor

Regions US West (Oregon) and Asia Pacific (Tokyo) are now available: https://www.graph.cool/docs/blog/introducing-regions-and-better-performance-she7yaab6l/

@k00k
Copy link

k00k commented Aug 7, 2017

+1 for us-east-*

@glenbray
Copy link

glenbray commented Sep 6, 2017

+1 for Australian region - ap-southeast-2

@sorenbs
Copy link
Member

sorenbs commented Sep 6, 2017

Hi @glenbray Is there any reason other than performance that you can't use the Tokyo region?

@glenbray
Copy link

glenbray commented Sep 6, 2017

Hi @sorenbs, We collect personal information. Our privacy laws allow us to store offshore, but I'd prefer our data remain within Australia.

@sorenbs
Copy link
Member

sorenbs commented Sep 7, 2017

Got it - thanks! 👍

@sebas5384
Copy link

What about South America? there's an AWS zone in São Paulo, Brazil.

@marktani marktani changed the title More datacenters More datacenters for the shared cluster Nov 3, 2017
@marktani
Copy link
Contributor

This issue has been moved to graphcool/graphcool-framework.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests