back of the envelope estimation
Quick, rough arithmetic with stated assumptions to find the scale a system must handle.
In more detail
The goal is the right order of magnitude, not a forecast. Every input is a labelled assumption someone can correct, and aggressive rounding keeps it doable in your head. Estimation comes before choosing components, because the numbers decide which components make sense.
Example
A day has 86,400 seconds; call it 100,000, so a million events a day is about ten a second.Related terms
- order of magnitude — A rough size expressed as a power of ten, such as tens, thousands or millions, rather than an exact figure.
- daily active users — The number of distinct people who actually use a product on a typical day.
- queries per second — The number of requests a system handles each second, the usual unit for traffic and capacity.
- peak factor — How many times busier the busiest hour is than the average hour.
Taught in
- What A Design Is For, And How To Run A Design Discussion — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Traffic And Throughput — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Storage And Bandwidth — Scalable System Design & Distributed Architecture
- Worked Design One: Scaling The Ticket Booking System — Scalable System Design & Distributed Architecture
- Worked Design Two: A Global Chat System — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture