Dashboard/System design/11. Content Delivery Network (CDN)

SYSTEM DESIGN · LESSON 11 OF 52 · 16 MIN VIDEO · 6 TOPICS

Content Delivery Network (CDN)

Module Progress (0 / 6 Lessons Completed)0%
System design Track (0 / 52 Modules) · Overall 0/80 (0%)0%
⌁

Narrated HD Video Lesson (16 min) · Pro

Lesson Overview + Section #01 + RESHADED Checklist + Quiz #1 are unlocked free below (no login required). Unlock all 80 HD video lessons and deep-dive sections — or watch our two free sample video lessons first.

0% READSec 01/06 · System Design: The Content Delivery Network (CDN)
SYSTEM DESIGN VIDEO LESSON & GUIDE

Content Delivery Network (CDN)

Serving web assets, APIs, and streaming media from a single centralized origin fails at global scale due to speed-of-light fiber propagation delays, multi-terabit backbone transit bottlenecks, and single-site blast radius. A Content Delivery Network (CDN) resolves these constraints by placing distributed reverse-proxy caches inside ISP access networks and Internet Exchange Points (IXPs), terminating TLS locally and answering the vast majority of requests within single-digit milliseconds. In L4-L6 system design interviews, candidates are evaluated on multi-tier cache shielding math, request routing trade-offs (GeoDNS with EDNS Client Subnet vs. Anycast BGP), stampede prevention via request coalescing, and cache consistency protocols (TTLs, stateful leases, and active purges).

WHAT YOU WILL MASTER IN THIS LESSON
  • Quantify speed-of-light fiber RTT, TCP/TLS handshake amplification, and multi-terabit egress volume to justify edge caching.
  • Architect a 7-component CDN separating the low-latency client data path from asynchronous distribution, DDoS scrubbing, and telemetry-driven routing.
  • Design multi-tier child-parent cache hierarchies (origin shielding) and collapsed forwarding to absorb Zipfian long-tail misses.
  • Compare GeoDNS, Anycast BGP, HTTP 302 redirection, and client multiplexing across failover speed, load awareness, and resolver accuracy.
  • Balance staleness bounds against origin validation RPS across periodic polling, TTL expiration, stateful leases, and urgent global purges.
SYSTEMATIC BUILDING-BLOCK CHECKLIST (FROM MODULE 01)

4-Point Infrastructure Primitive Audit

Check off each dimension as you study this building block—interviewers test what it solves, how it works inside, what it costs, and how it fails.

0 / 4 Checked
INTERVIEWER SCORECARD · WHAT MAKES A STRONG HIRE?

5 Signals Bar Raisers Grade (L4 vs. L5 Senior vs. L6 Staff)

Senior (L5 / E5 / Senior SDE) Bar — Autonomous Pacing, Depth & Proactive Trade-Offs: Owns the 45-minute clock without prompting, derives every component quantitatively, surfaces failure modes (hot shards, stampedes, dual writes) BEFORE being asked, and defends consistency vs. latency trade-offs.
1. Scoping
✓ STRONG HIRE SIGNAL

Clarifies users, read/write skew, p99 latency, consistency bounds, and explicit non-goals in minutes 2–8.

✗ NO-HIRE RED FLAG

Jumps straight into drawing load balancers and microservices at minute 2 without asking a single question.

2. Right-Sized Design
✓ STRONG HIRE SIGNAL

Starts with the simplest working architecture justified by the math (e.g., 1 NVMe SQL primary + replicas + Redis for 40 writes/s & 3 TB).

✗ NO-HIRE RED FLAG

Recites a memorized Kafka + multi-DC Cassandra diagram that contradicts their own traffic calculations.

3. Technical Depth
✓ STRONG HIRE SIGNAL

Drives deep into 1–2 hard bottlenecks (partition keys, hot-key mitigation, transactional outbox, KV-cache batching) at minute 27.

✗ NO-HIRE RED FLAG

Skims across 12 boxes at identical buzzword depth and runs out of time before the deep dive.

4. Explicit Trade-Offs
✓ STRONG HIRE SIGNAL

Uses 3-part reasoning: 'A queue here because SMTP spikes to 3 s; checkout stays <60 ms, and we accept eventual email delay + retry dedup.'

✗ NO-HIRE RED FLAG

Name-drops tools ('We put Kafka and ZooKeeper here') without stating the alternative or operational cost.

5. Communication
✓ STRONG HIRE SIGNAL

Thinks aloud every 30–45s, checks alignment at phase transitions, and treats 'What if X fails?' as a cue for where points are awarded.

✗ NO-HIRE RED FLAG

Goes silent for 5 minutes while drawing or defends a flawed assumption defensively when nudged.

ARCHITECTURE & DATA-FLOW SLIDES · SLIDE 1 OF 1Section 01: System Design: The Content Delivery Network (CDN)
ARCHITECTURE / DATA FLOW DIAGRAM
single point of failureOrigin data centerVirginiaa few msUsersMelbourneUsersLondonUsersSão PauloEdge serverMelbourneEdge serverLondonEdge serverSão Paulo
SECTION 01 OF 6

1. System Design: The Content Delivery Network (CDN)

★ FREE PREVIEW
Key Takeaway: Centralized origins hit hard physical limits on fiber propagation latency, backbone transit bandwidth, and single-site availability; replicating hot content to local edge servers eliminates cross-oceanic round trips and collapses origin load.
ARCHITECTURE / DATA FLOW DIAGRAM
single point of failureOrigin data centerVirginiaa few msUsersMelbourneUsersLondonUsersSão PauloEdge serverMelbourneEdge serverLondonEdge serverSão Paulo

The Physics of Cross-Continental Latency

Light travels through optical fiber at roughly 200,000 km/s (about two-thirds its vacuum speed due to the refractive index of glass). When a user in Melbourne requests content from a centralized origin data center in Virginia (~16,000 km away), one-way propagation alone requires 16,000 km / 200,000 km/s = 80 ms, imposing a physical minimum Round-Trip Time (RTT) of 160 ms before accounting for router queuing or processing. Because an HTTPS page load over TCP + TLS requires roughly 3 sequential round trips (TCP SYN/SYN-ACK, TLS handshake, and the initial HTTP GET) before the first payload byte arrives, the client stalls for 3 * 160 ms = 480 ms of pure propagation delay. Placing an edge server in Melbourne (< 50 km away) reduces physical RTT below 5 ms and cuts pre-TTFB handshake overhead to under 15 ms.

MetricSingle Origin (Virginia -> Melbourne)Local CDN Edge (Melbourne PoP)
Physical Path Distance~16,000 km (transoceanic fiber)< 50 km (metro ISP / IXP)
One-Way Propagation Delay16,000 km / 200,000 km/s = 80 ms< 1 ms
Minimum Network RTT80 ms * 2 = 160 ms2 ms - 10 ms
Pre-TTFB Handshake (3 RTTs)3 * 160 ms = 480 ms6 ms - 30 ms
Autonomous System (AS) Hops8 - 15 transit networks (higher loss)1 - 2 local ISP hops (minimal loss)

Backbone Bandwidth Volume and Transit Economics

Latency is compounded by aggregate egress volume when millions of clients stream media simultaneously. If 1,000,000 concurrent viewers stream high-definition video at 5 Mbps each, serving them from Virginia requires 1,000,000 * 5 Mbps = 5 Tbps of sustained egress from a single data center. Hauling identical video segments across transoceanic cables and multiple Tier-1 transit providers incurs massive per-Mbps transit bills, introduces BGP peering congestion, and degrades TCP throughput—since standard TCP congestion control throughput scales inversely with RTT * sqrt(packet_loss).

  • Aggregate Egress Bottleneck: 1,000,000 concurrent viewers at 5 Mbps demand 5 Tbps of NIC and border-router capacity at one facility.
  • Multi-Hop Congestion Penalty: Long paths cross numerous peering boundaries where even 0.1% packet loss at 160 ms RTT collapses TCP window scaling and causes video rebuffering.
  • Redundant Transit Cost: Paying Tier-1 transit providers to carry the same 4 MB video chunk 1,000,000 times across oceans wastes capital compared to serving 999,999 copies from local metro caches.

Single-Origin Fragility and Flash Crowds

Relying on a single origin site creates an unacceptable blast radius during both traffic spikes and infrastructure outages. A viral live broadcast or major software release can multiply inbound RPS and bandwidth by 10x-50x within seconds, exhausting origin connection tables, TLS CPU offload, and storage IOPS. Distributing copies across hundreds of geographically isolated Points of Presence (PoPs) absorbs regional traffic surges near the client and ensures that a single data center power failure or fiber cut never takes down global delivery.

Interview Signal: Interviewers test whether candidates distinguish latency from bandwidth: adding 100 Gbps NICs or more origin servers solves origin throughput saturation, but can never beat the 480 ms speed-of-light penalty across 16,000 km.
SECTION 02 OF 6

2. Introduction to a CDN

🔒 PRO SECTION
Key Takeaway: A CDN is a globally distributed reverse-proxy cache measured primarily by its cache hit ratio (hits / total_requests), accelerating static assets via local storage and dynamic responses via local TLS termination and connection pooling.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

SECTION 03 OF 6

3. Design of a CDN

🔒 PRO SECTION
Key Takeaway: A resilient CDN decouples the inline user delivery path (Request Routing -> Scrubbers -> Edge Proxies) from asynchronous cache distribution and closed-loop telemetry management.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

SECTION 04 OF 6

4. In-Depth Investigation of CDN: Part 1

🔒 PRO SECTION
Key Takeaway: Production CDNs default to pull-based caching with selective push pre-warming, organize PoPs into multi-tier cache shields to capture long-tail misses, and combine GeoDNS with Anycast BGP for low-latency, fault-tolerant routing.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

SECTION 05 OF 6

5. In-Depth Investigation of CDN: Part 2

🔒 PRO SECTION
Key Takeaway: Time-to-Live (TTL) expiration handles everyday cache freshness passively, stateful leases slash validation traffic by over 5,000x for read-heavy mutable objects, and hybrid ISP/IXP placement balances ultra-low last-mile latency against deployment scale.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

SECTION 06 OF 6

6. Evaluation of CDN's Design

🔒 PRO SECTION
Key Takeaway: High cache hit ratios drive nonlinear gains in both average latency and horizontal scalability, while Anycast scrubbing and stale-if-error caching insulate services from multi-hundred-Gbps DDoS attacks and origin outages.

Section 1 + Checkpoint Quiz #1 are unlocked free outside the paywall. Unlock all architecture slides, QPS & sharding trade-off tables, and all 80 narrated HD video lessons with Full Access — or inspect our sample payment system lesson first.

ACTIVE RECALL & TRADE-OFF PROBES

System Design Checkpoint Quizzes (1)

CHECKPOINT QUIZ #1

In "System Design: The Content Delivery Network (CDN)" (The Physics of Cross-Continental Latency), how does a production-grade design handle "One-Way Propagation Delay" (Local CDN Edge (Melbourne PoP))?