Foundations
Route a request through DNS, TLS and three hops, paying the real latency cost of every choice you make.
Size six systems against a ticking clock. Order of magnitude is a pass; a decimal place is not required.
A service is at 100% of something. Find which resource, before the queue depth passes the point of no return.
Partition a cluster and choose what to sacrifice. Every choice shows you the user-visible consequence.
Ship four versions of an API to a client you cannot update. Break it once and the round ends.
The other tracks
Where the state lives, and what it costs to keep it · 6 modules · 30h
Making the second request cheap · 4 modules · 16h
Decoupling two services without losing a message · 5 modules · 21h
From one box to a fleet, without a rewrite · 5 modules · 17h
What happens on the worst day · 5 modules · 18h
The six systems you will actually be asked to draw · 6 modules · 22h
Running the forty-five minutes on purpose · 5 modules · 12h
