Part 1 of 8 · 1 min read
Why this page comes first after load balancers
In this module you will
- Explain what a content delivery network (CDN) is and why it makes pages load faster, using round trip numbers.
- Follow a request through an edge server on a hit and on a miss, and compute the hit ratio and the load that reaches the origin.
- Set cache rules with headers such as
Cache-ControlandETag, and say what a 304 reply means. - Build a cache key, and spot the mistakes that split one file into many copies.
- Update a file that is already cached in thousands of places, using versioned names or a purge.
- Explain origin shielding and the herd of misses it prevents, and plan for a CDN failure.
The previous page spread traffic over servers in a region. This page removes most of the traffic before it reaches those servers at all. For most websites, the biggest bytes are images, scripts and video, and a CDN serves them from near the user. In an interview, adding a CDN is among the cheapest and most credible early steps. The numbers on this page are made up to show the idea, unless the text names a book.