Last Minute Notes
  • Github
  • Docs
  • Learn
    @sayanstwt
Lessons
0/37 done
  • How a Request Travels
  • Back-of-Envelope Math
  • Latency & Percentiles
  • From One Server to Many
  • Availability & the Nines
Learn/System Design/Foundations

How a Request Travels

7 min Beginner 8 steps

Follow one request hop by hop and see what each layer adds.

Hops
6+
Each hop adds
latency, risk
Each hop buys
scale, safety
Clientbrowser or appCDNedgeLoad balancerAPI gatewayServicestatelessCacheQueueDNSname -> IPDatabase
request response data
In this lessonStep 1 of 8
  1. The path
  2. DNS
  3. CDN
  4. Front door
  5. Data
  6. Async
  7. Add vs buy
  8. Recap
Step 1 / 8problem

One click, many hops

A user taps a button. Before any of your code runs, the request crosses DNS, a CDN, a load balancer and an API gateway.

Most designs are variations on this one path, so trace it end to end first.

Key idea

Know the default path cold. Every system design answer starts by drawing it.

←→ step·R replay·Space pause

You'll learn

  • Name every hop a request crosses, in order
  • Why DNS and the CDN come before your servers
  • What the balancer, gateway and cache each do on the path
  • Move slow work off the request path with a queue
  • Ask what each hop adds and what it buys
Read the full notesHLD Building Blocks, 1