Latency budgets
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
split an end-to-end target across the calls on the path.
Planned topics
- Start from the user-facing target, e.g. checkout p99 under 800 ms.
- Allocate to each hop on the critical path; sequential calls add, parallel calls take the maximum.
- Budget percentiles (p99), not averages; leave margin for network and serialization.
- A call without a budget gets a timeout derived from it.
Draft outline details
Demonstration
a table: gateway 20 ms, order service 120 ms, inventory 150 ms, payment 350 ms, database 100 ms, margin 60 ms.
Check your understanding
Why budget p99 rather than the average?
Show answer
Users and SLOs feel the tail; averages hide it.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.