Part 1 of 7 · 1 min read
Why this page closes the level
In this module you will
- List the layers where a response can be cached between a user and the database.
- Read the HTTP headers Cache-Control, Expires and ETag, and trace a conditional request that returns 304.
- Compute how much traffic each layer removes, and what reaches the database.
- Work out the worst-case staleness of a response that passes through several caches.
- Choose where to cache a given piece of data, and say when fewer layers are better.
The earlier pages looked at one cache at a time. A real request passes several, and the numbers multiply while the staleness adds up. This page puts the layers in one picture and gives a way to decide which ones a design needs. The tier is Common. The numbers are made up to show the idea, unless the text names a book.