Reliability / 5 / 6
SLOs and error budgets
A taxi app's booking API serves about 100 requests a second. The health check says 100% while riders see errors. How to measure reliability the way users feel it, agree on a target, turn the gap into an error budget, and page people only when that budget is really burning.
- 14 min
- Intermediate
- 10 steps
- Good requests
- 98.5 %
- Budget left
- —
- Burn rate
- —
- Booking p99
- 450 ms
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Monitoring → Booking APIRequest
GET /healthz HTTP/1.11
Host: ride-api.internal
Response
HTTP/1.1 200 OK2
status: up
uptime: 100% this month3
healthz— A cheap internal endpoint. It does not touch the database or the booking path.200— The process is alive. It says nothing about the bookings that failed.uptime— Counted from health checks, so it hides every error a real rider saw.
Build it yourselfCheat sheetCompare lessons
Course: 74 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes
11 Case studies