Concept 1 of 71 min
Availability targets, error budgets and observability
An error budget
| Target | 99.95% |
|---|---|
| Allowed down | 0.05% |
| Minutes a month | 43,200 |
| Minutes a year | 525,600 |
- Month = 43,200 × 0.0005 = 21.6 minutes
- Year = 525,600 × 0.0005 = 262.8
About 4.4 hours of downtime a year is all the target allows.
Average against p99
| 99 checkouts | 300 ms each |
|---|---|
| 1 checkout | 9,000 ms |
- Fast part = 0.99 × 300 = 297
- Slow part = 0.01 × 9,000 = 90
- Average = 297 + 90 = 387 ms
The average hides the 9-second wait that p99 shows.
That effort comes from releases. The 99th-percentile latency shows the slow tail that averages hide, distributed tracing times each hop of a request across services, and a rarely called serverless function pays a cold start.
A 30-day month has 43,200 minutes and a year 525,600, so each extra nine cuts the allowance tenfold. The error budget links release speed to reliability: raising the target or lowering it to free budget dodges the point.
The slowest 1% of requests are often the busiest users or the largest orders. CPU (central processing unit) graphs and access logs show servers, not the path of one request; a trace's spans make the slow hop stand out.
After idle time the platform starts a fresh environment and loads the code; warm instances or lighter runtimes reduce it.
- Confusing the monthly and the yearly downtime allowance.
- Moving the target when the error budget runs out.
- Judging latency on the average.
A trading platform promises clients 99.9% availability. How would you set up the team to keep that promise?
A complete answer covers
- Turn it into an error budget: about 43 minutes a month.
- Measure availability from the client's side, with alerts on the budget burn rate.
- Freeze risky releases when the budget is spent.
- Track tail latency and tracing to find problems before outages.
Also in our technical interviews, on camera, with a score.
Concept 2 of 71 min
Containers, probes, autoscaling and limits
The why, the charts, the worked example and the interview questions are in Essentials, with every quiz.
See the plansSign inConcept 3 of 71 min
Canary and blue-green releases, code and secrets
The why, the charts, the worked example and the interview questions are in Essentials, with every quiz.
See the plansSign inConcept 4 of 71 min
Zones, recovery targets, distance and scaling out
The why, the charts, the worked example and the interview questions are in Essentials, with every quiz.
See the plansSign inConcept 5 of 71 min
Networking basics: layers, DNS, subnets and UDP
The why, the charts, the worked example and the interview questions are in Essentials, with every quiz.
See the plansSign inConcept 6 of 71 min
Storage choices and cloud costs
The why, the charts, the worked example and the interview questions are in Essentials, with every quiz.
See the plansSign inConcept 7 of 71 min
AdvancedBuying capacity in layers: commit the base, scale the peak
The why, the charts, the worked example and the interview questions are in Essentials, with every quiz.
See the plansSign inRecap
- Downtime allowed = (1 − availability) × minutes in the period; a spent error budget pauses risky releases.
- Containers share the host kernel and lose their disk on redeploy; readiness gates traffic, liveness restarts; set memory limits.
- Canary exposes a few users first; blue-green rolls back by switching traffic; changes live in code, secrets in a manager.
- Spread replicas across zones and test failover; recovery point = data lost, recovery time = time down.
- Price the cloud per hour × 8,760, egress per GB, and rebuild only what changed.
25 questions on Cloud and infrastructure
Timed, like the real one, drawn from a bank of 33. Every answer explained.