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

Back-of-Envelope Math

7 min Beginner 8 steps

Turn traffic and data numbers into servers, storage and bandwidth.

Goal
right order
One box
or 1,000?
Bottleneck
CPU, disk, net
Storageday, year, copies?Bandwidthbits per second?Users100M dailyQPSavg and peakCache sizehot 20% of reads?Serverswith headroom?not accuracy: which decision do the numbers force?
request response data
In this lessonStep 1 of 8
  1. The question
  2. Shortcuts
  3. QPS
  4. Storage
  5. Bandwidth
  6. Servers
  7. Decisions
  8. Recap
Step 1 / 8problem

One machine or a thousand?

Before you draw boxes, you need a rough size. The goal is not accuracy.

It is to know whether you need one machine or one thousand, and whether the bottleneck is CPU, memory, disk or network.

Key idea

Estimate only what changes a decision. Ten minutes of arithmetic that changes nothing is wasted.

←→ step·R replay·Space pause

You'll learn

  • Convert per day numbers to QPS in your head
  • Derive average and peak QPS and the read:write ratio
  • Estimate storage with replication, and bandwidth in bits
  • Turn peak QPS into a server count with headroom
  • Let the numbers drive design decisions
Read the full notesSystem Design Fundamentals, 4