The DevOps concept map
33 concepts across 12 tracks, drawn with the 82 links between them. 53 of those links (65%) cross tracks, which is the part worth looking at: the concepts that decide DevOps interviews are rarely the ones that sit neatly inside one topic. Hover a concept to see only what it touches. Click to read it.
Where the map is dense
The most-connected concepts are the ones the rest of the library keeps reaching for, which makes them the highest-leverage things to be solid on: Error budgets: the arithmetic and the decision it forces (11), Napkin math: sizing a system before you draw it (10), Saturation and utilisation targets: why systems fall over before they are full (8), Failure domains: what a region, a zone and a cell actually buy you (7), and Deploying is not releasing (7). If you are deciding where to spend a week, start with a hub rather than a leaf.
Every concept, by track
AI Infrastructure6
- The KV cache is what decides how many users you can serve6
- Tokens are the unit of cost, latency and capacity at once5
- Why GPUs break the assumptions schedulers are built on4
- Prefill and decode are two different workloads on one GPU4
- Model quality degrades without touching a single infrastructure metric4
- An agent can act as a confused deputy4
The map is for orientation. If you would rather be told what to do in order, the start-here path sequences the same material by background and stage, and the courses walk it front to back.