Real Time Updates hard
For a global real-time game, User A (Sydney) and User B (London) need to interact. Direct connection is impossible (NAT). Routing via a central US server adds 300ms latency. What is the architecture solution?
- A Use a CDN.
- B Use Satellite Internet.
- C Global Mesh / Edge Acceleration. Users connect to the nearest Edge POP (Point of Presence). The POPs communicate via a dedicated fiber backbone (fast lane) rather than the public internet.
- D Use HTTP/3.
Answer: C. Global Mesh / Edge Acceleration. Users connect to the nearest Edge POP (Point of Presence). The POPs communicate via a dedicated fiber backbone (fast lane) rather than the public internet.
The public internet routing (BGP) is not optimized for latency. Services like Cloudflare Argo or AWS Global Accelerator ingest traffic at the edge and route it over private fiber lines, shaving off 30-50% of cross-globe latency.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- When a mobile app is closed/backgrounded, it cannot keep a WebSocket open. How does it receive real-time alerts (like 'New Message')?
- For a human user, what is generally considered the maximum acceptable latency for an interaction to feel 'Real-Time' (e.g., typing in a Google Doc)?
- If you want to update a news feed on a website every time a new article is published, what is the simplest (but least efficient) 'Real-Time' technique?
- In a persistent real-time connection, what is the purpose of a 'Heartbeat' or 'Ping/Pong' message?
- Why is Short Polling considered 'Chatty'?
- Server-Sent Events (SSE) are ideal for which type of real-time application?