What is a CDN & why Developers should Care about using one
summary
CDNs act as global reverse proxies that cache content at the edge, reduce latency and absorb attacks: a single rack can hold ~768 TB SSD, Fastly reports handling 160 Gbps DDoS spikes and seeing up to 400+ Gbps and ~1M SYNs/sec in the largest attacks. Key capabilities include instant purge (≈150 ms), config deploys in ≈5 s, real‑time logs/stats, stale‑while‑revalidate and stale‑if‑error, Dynamic Site Acceleration for uncachable traffic, header/tag invalidation for selective purges, and handling hundreds of thousands of RPS from the edge.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:29Artur Bergman
- 0:552008 @ Wikia
- 3:37Caching reverse proxy
- 3:53Big awesome cache
- 5:08Inside-out cache
- 8:16160 Gbps DDOS
- 12:19Prince died
- 14:33Do things at the edge
- 15:24developer tools
- 16:17Dynamic Site Acceleration
- 21:41Instant config
- 21:53Instant logfiles
- 26:27Fallacies of distributed systems
- 27:01Technologies
related talks
53mCDNs 101: An Introduction to Content Delivery Networks
23mMastering the CDN Present & Future
33mCDN — The Technology Taking Games to the Next Level
23mContent delivery sucks, and what you can do about it
10mInterview
10mAutomating content delivery in a DevOps world
51mYou Need a CDN! ...or Maybe Not?
17mBuilding a High Performance, Dynamic CDN with Next.js