Outline: (1) overview: availability, the nines, composite availability, failure modes, cascading failures; (2) SLI / SLO / SLA: measuring, targets, error budget, burn rate and multiwindow alerts, contracts; (3) resilience patterns: timeout and its budget, retry, circuit breaker, fallback, bulkhead, rate limiting, health checks, layering; (4) chaos engineering: proving that the patterns work. Three simulators: slo-month and error-budget-burn (SLI / SLO / SLA), slow-dependency (Resilience Patterns).
Reliability: the probability that a system performs its function without failure, under stated conditions, for a period. Roadmap: overview → SLI/SLO/SLA → resilience patterns → chaos engineering.
The page's worked example: reduce the parallel part first, then multiply the series. Hands-on 7 runs every replica on one laptop: one host, so not independent.
Negotiation example from the page: "12 minutes of budget left in the window; a deploy that causes 30 minutes of degradation misses the SLO — wait."