Q: You run a global e-commerce site. Most traffic is read-heavy (viewing products). Users complain the site is slow in Asia while your servers are in US-East. How do architecturally drastically reduce latency for read operations globally?

For read-heavy global traffic, you must push the data as close to the user as possible (Edge).

• Content Delivery Network (CDN): Serve all static assets (images, CSS, JS) and highly cacheable API responses (like the product catalog JSON) from a CDN (Cloudflare / AWS CloudFront) edge node physically located in Asia.
• Cross-Region Read Replicas: For dynamic data that cannot be purely CDN-cached, deploy async Read Replicas of your database in an Asian region (e.g., AWS RDS Cross-Region Replica). Route the Asian API servers to read from this local DB replica.
• Edge Compute: Execute lightweight routing logic or JWT validation using edge functions (Lambda@Edge or Cloudflare Workers) directly at the PoP to avoid the round-trip to US-East entirely.