Last Minute Notes
  • Github
  • Docs
  • Learn
    @sayanstwt
Lessons
0/37 done
  • How a Request Travels
  • Back-of-Envelope Math
  • Latency & Percentiles
  • From One Server to Many
  • Availability & the Nines
Learn/System Design/Foundations

Availability & the Nines

6 min Beginner 7 steps

How components in series lose nines and redundancy wins them back.

Components
4
All must work
yes
Status
serving
ClientWebAPIDatabaseonly one
request response data
In this lessonStep 1 of 7
  1. The problem
  2. The nines
  3. Series
  4. Parallel
  5. Shared fate
  6. SLOs
  7. Recap
Step 1 / 7problem

One fault takes the site down

A fault is one component deviating from spec. A failure is the whole system no longer meeting its spec.

With a single database on the path, one fault becomes a failure. Fault tolerance means faults do not become failures.

Key idea

Availability is the fraction of time the system is up and serving. Reliability is doing the correct thing.

←→ step·R replay·Space pause

You'll learn

  • Tell a fault from a failure
  • Translate nines into downtime
  • Compute availability for series and parallel components
  • Spot shared fate that breaks redundancy
  • Use SLIs, SLOs, SLAs and error budgets
Read the full notesSystem Design Fundamentals, 6