There is something old school about knowing exactly where your packets are on the surface or below the ocean of the earth.
I know this might sound weird but not to someone who lives science as a normal part each day. I would like to make sure my REST calls propagate around the globe - not just to a server on the other side of the earth and back again like from us-east-1 to the Singapore ap-southeast-1 region but through us-west-2 through singapore - to europe and back to us-east-1.
Sort of when I fly - in order to maximize the number of takeoffs and landings - I try to get the most number of stops - a direct flight is not the best way to get somewhere when testing latency - as in packets on the cable from Oregon to China are better routed through Hawaii.
I liked Andrew Blum's "Tubes" book - which include details on the endpoints for sub-marine cables - https://www.amazon.com/Tubes-Journey-Internet-Andrew-Blum/dp/0061994952 - I also ran into a bit of this propagation delay working at Nokia.
This system will of course run a set of helm/kubernetes clusters (a cluster of 1 on each DC for now)
First principles will be install proxies at several regions in Amazon EC2 - https://aws.amazon.com/about-aws/global-infrastructure/
This is the path we will take (see the red circles on the Amazon AWS regions) - hopefully no backtracking and ideally it is roughly valid - as we do not actually cross the equator - I will also try through Sau Paulo.
through the following Amazon regions
US East (N. Virginia)Canada (Central)US East (Ohio)US West (N. California)US West (Oregon)Asia Pacific (Tokyo)Asia Pacific (Seoul)
Asia Pacific (Singapore)Asia Pacific (Sydney) - skip
Asia Pacific (Mumbai)EU (Frankfurt)EU (Paris)
EU (Stockholm) - skipEU (London)EU (Ireland)South America (São Paulo) - skip
|0||0000||US East (N. Virginia)||us-east-1||220.127.116.11||p0/virginia||GMT-5||New York|
|US West Ohio||us-east-2||p2/ohio|
Opposite sides of the earth - Singapore - ap-southeast-1 to New York - us-east-1
It will never be shorter that 160 ms - which is c/(radius * pi /2) = as it it takes 16% of a second for light to pass to the other side (this is without optical repeater and endpoint delays)
packets within us-east-1
packets from singapore to us-east-1
All paths are linear in sequence with the first bit reserved for off axis secondary routes. For example 00 is us-east and 10 is us-east but 01 is ca-central (north of us-east).
|WI||Task||Jira / Wiki|
|WI 1||OpenAPI specification|
|adjust readme deployment guide|