OK, so, with the recent "no offline mode" issue, this is somewhat more important.
Here's what I regularly receive from the hop before your hosting server, depending on the time of day and which governments/hackers are DDOS whoever - typically when it's bad, it'll go
to
kinds of figures.
It also suffers from occasional loss, even when it is behaving at regular 350-390ms latency (and this is with an annex M low latency profile, seriously about as good as this will ever get from Brisbane au without fibre) - typically in the range of 2% or so over 100, but can go higher than this depending on load. People elsewhere in Australia are also going to have a 4000km addition over a not especially great link, to what is already basically a trip longer than the entire circumference of the earth, bringing them to 400-500+ms.
Amazon Elastic Compute Cloud claim they have several compute service options nearby - eg -
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html
Are these servers appropriate for running ED's back end? Do you plan to run the back end from other AWS locations? If so, is there a timeline for bringing this online?
Here's what I regularly receive from the hop before your hosting server, depending on the time of day and which governments/hackers are DDOS whoever - typically when it's bad, it'll go
14 997 ms 844 ms 1118 ms ec2-79-125-0-137.eu-west-1.compute.amazonaws.com
[79.125.0.137]
to
14 3359 ms 3477 ms 3279 ms ec2-79-125-0-73.eu-west-1.compute.amazonaws.com
[79.125.0.73]
kinds of figures.
It also suffers from occasional loss, even when it is behaving at regular 350-390ms latency (and this is with an annex M low latency profile, seriously about as good as this will ever get from Brisbane au without fibre) - typically in the range of 2% or so over 100, but can go higher than this depending on load. People elsewhere in Australia are also going to have a 4000km addition over a not especially great link, to what is already basically a trip longer than the entire circumference of the earth, bringing them to 400-500+ms.
Amazon Elastic Compute Cloud claim they have several compute service options nearby - eg -
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html
Code Name
ap-northeast-1 Asia Pacific (Tokyo)
ap-southeast-1 Asia Pacific (Singapore)
ap-southeast-2 Asia Pacific (Sydney)
eu-central-1 EU (Frankfurt)
eu-west-1 EU (Ireland)
sa-east-1 South America (Sao Paulo)
us-east-1 US East (N. Virginia)
us-west-1 US West (N. California)
us-west-2 US West (Oregon)
Are these servers appropriate for running ED's back end? Do you plan to run the back end from other AWS locations? If so, is there a timeline for bringing this online?