This topic is a interactive lesson inside the Foundations of Scalability module. The goal is not to memorize the title: reconstruct the problem it solves, the mechanism that makes it work, and the signal that tells you when to use it.
Remember the shape, not the sentence
“Scale up is buying a bigger machine; scale out is hiring more machines.”
What problem does this solve?
Start from the engineering problem rather than the definition. Interactive: numbers every engineer should know exists because a system needs a reliable way to handle a recurring constraint inside Foundations of Scalability. Ask what would become slow, ambiguous, unsafe, or impossible without it.
How the mechanism works
Break the idea into observable steps. The useful mental model is: input → transformation → decision or state change → output. Keep each step small enough that you can redraw it from memory. The surrounding module is the context: Scale up is buying a bigger machine; scale out is hiring more machines.
When to reach for it
Use nearby concepts as contrasts. In this module, compare Interactive: numbers every engineer should know with Vertical vs horizontal scaling, Latency, throughput, bandwidth — with real numbers, Availability, nines, and single points of failure. The distinction matters because good engineering choices depend on the constraints, not on memorizing isolated definitions.
See the mechanism before you memorize it
One diagram, one causal story, one reconstruction task.
Interactive: numbers every engineer should know — causal map
Frame
State the problem and the constraints before naming the technique.
Transform
Apply the core mechanism of Interactive: numbers every engineer should know and track what state changes.
Observe
Inspect the artifact, output, invariant, or behavior produced by the mechanism.
Transfer
Explain where the same idea appears elsewhere in System Design Fundamentals.
Draw the idea yourself
Rebuild the core flow on a real canvas before moving to the worked walkthrough.
Walk the system
Frame
State the problem and the constraints before naming the technique.
Transform
Apply the core mechanism of Interactive: numbers every engineer should know and track what state changes.
Observe
Inspect the artifact, output, invariant, or behavior produced by the mechanism.
Transfer
Explain where the same idea appears elsewhere in System Design Fundamentals.
Reconstruction card
Use the card as a generative note, not a summary to copy. Fill it from memory after the explanation.
TOPIC: Interactive: numbers every engineer should know
MODULE: Foundations of Scalability
TYPE: interactive lesson
PROMPT
What problem does it solve?
What changes step by step?
What evidence proves it worked?
When would you choose something else?What usually goes wrong
Close the tab. Rebuild it from memory.
Read the question, answer aloud, then reveal.
What problem is Interactive: numbers every engineer should know designed to solve?Reveal answer
It addresses a recurring constraint inside Foundations of Scalability. A strong answer names the input, the core mechanism, and the result rather than repeating the title.
What are the four stages of the mental model?Reveal answer
Frame the problem → transform the input/state → observe the evidence → transfer the idea to a new scenario.
What do 'three nines' and 'five nines' allow per year?Reveal answer
99.9% ≈ 8.7 hours of downtime/year; 99.999% ≈ 5.3 minutes/year.
Why is horizontal scaling the default for web systems?Reveal answer
Commodity machines are cheap and failure-contained; vertical scaling hits hardware ceilings and keeps a single point of failure.
Make this idea travel.
Connect it next to: Vertical vs horizontal scaling • Latency, throughput, bandwidth — with real numbers • Availability, nines, and single points of failure • Back-of-envelope estimation: QPS & storage.