Content delivery sucks, and what you can do about it
summary
Explains concrete decisions and tradeoffs: how to measure CDN egress vs cloud egress, why cache fill behavior and POP placement matter, and when a single retry recovers many playbacks versus needing fallbacks. Describes concrete tools and architectures: TLS everywhere, encrypted edge storage, multi-CDN via DNS server or client-side routing and peer‑to‑peer, and having a hot backup CDN. Offers measurable practices and debugging steps rather than marketing fluff.
AI-written summary · about
chapters (5)
related talks
53mCDNs 101: An Introduction to Content Delivery Networks
10mEnhancing CDN Performance and Cutting Egress Costs in Large Video Libraries
16mMulti-CDN Jumpstart
29mSex, Lies & Videotapes: The Truth Behind Your CDN Logs
51mYou Need a CDN! ...or Maybe Not?
32mWhat is a CDN & why Developers should Care about using one
23mMastering the CDN Present & Future
10mAutomating content delivery in a DevOps world
