Latency Budget
Split two hundred milliseconds across DNS, TLS, TTFB, download and render without cheating physics. Harder than it sounds, and it recalibrates your instincts permanently.
You have seen the waterfall and you have read the pipeline. This is where you find out whether any of it transferred.
The game hands you a budget and a destination and asks you to spend it. The trap it sets is the one everybody falls into on a real project: over-spending on the parts that feel like engineering, bundle size, render time, and under-spending on the parts that are pure geography. Watch where you lose.
Play it three times. If your third score is not meaningfully better than your first, go back to the waterfall in the first chapter and drive the 3G preset again, paying attention to the round-trip counter rather than the milliseconds.
Latency Budget
Split 200ms across DNS, TLS, TTFB, download and render without cheating physics.
Play Latency BudgetYou should now be able to
- Allocate a latency budget across a real request
- Recognise which costs are fixed by distance rather than code
Loading…