Last Minute Notes
  • Github
  • Docs
  • Learn
    @sayanstwt
Lessons
0/37 done
  • DNS Resolution
  • Content Delivery Networks
  • Load Balancing
  • Gateways, Proxies & Meshes
  • Caching
  • Rate Limiting
Learn/System Design/Traffic & Edge

Content Delivery Networks

6 min Beginner 7 steps

Serve bytes from the edge, and know what happens on a miss.

Round trip
long
Origin serves
every request
Spike
-
UserTokyoUserBerlinOriginyour serversnormal loadUserLima/img/a.jpg
request response data
In this lessonStep 1 of 7
  1. The problem
  2. Edge hit
  3. Miss path
  4. Pull or push
  5. Freshness
  6. Cache key
  7. Recap
Step 1 / 7problem

Every user crosses the world

Users everywhere fetch the same image from one origin. Each fetch pays a long round trip, and every request lands on your servers.

A traffic spike or an attack hits the origin directly.

Key idea

Static content is the same for everyone. Serving it from one far away place wastes time and capacity.

←→ step·R replay·Space pause

You'll learn

  • Why serving from the origin alone is slow and fragile
  • Trace a request through edge, shield and origin
  • Choose pull or push, and invalidate by versioned URLs
  • Pick a cache key that is safe and keeps hit rate high
Read the full notesHLD Building Blocks, 3