1. AWS Well-Architected Framework
Performance Efficiency Pillar (July 2023): In the section "PERF 2: How do you select the best performing architecture?"
the framework states
"To reduce latency
you can locate your infrastructure closer to your users or locate your data closer to your infrastructure." It further advises to "Select the right AWS Region(s) and Edge locations based on where your customers are located to reduce latency." (Page 11).
2. Microsoft Azure Documentation
"Multi-region N-tier application": In the architecture overview
it is stated
"Deploying the application in multiple regions can reduce latency for users. If you route users to the nearest region
they will experience lower network latency." This is listed as a primary benefit of the multi-region pattern. (Reference Architecture ID: architectures/n-tier/multi-region-n-tier.yml).
3. Google Cloud Documentation
"Choosing a network service tier": This document explains how network design impacts performance for global users. It notes
"For the lowest possible latency
Google Cloud recommends that you serve your traffic from a region that is closest to your users." (Section: "When to use Standard Tier and Premium Tier").
4. Armbrust
M.
et al. (2009). Above the Clouds: A Berkeley View of Cloud Computing. University of California
Berkeley. In Section 3.2
"Classes of Utility Computing
" the paper discusses the importance of geographic location for latency-sensitive applications: "For a user in New York
a datacenter in California can easily add 80 ms of latency to every interaction due to the speed of light
versus a datacenter in New York." (Page 10
EECS Department
Technical Report No. UCB/EECS-2009-28).