Part 2 of 9 · 1 min read
What an estimate is for
Why a rough number is worth more than a careful guess, and the four numbers most designs need.
Think of a cook planning a party. The cook does not weigh each guest. The cook counts about forty guests, guesses a plate each, and buys enough food for about fifty. The guess is rough, but it prevents buying a bag of rice for a hundred or a single chicken for the whole party.
Back-of-the-envelope estimation
A back-of-the-envelope estimation is a quick calculation with round numbers and stated assumptions, done to find out roughly how big a system must be. The name comes from the idea that the whole sum fits on the back of an envelope.
Example: "100,000 users, 5 requests each a day, so about half a million requests a day, so about 6 a second."
Most designs need four numbers:
- Requests per second, to size the servers.
- Peak requests per second, because systems are sized for the busy moment and not for the average.
- Storage, to size the data stores.
- Bandwidth, the amount of data moved each second, to size the network.
The process is the point. A written chain of assumptions and steps lets another person find the weak step and fix it. A single unexplained number cannot be checked.
Check yourself:
- Why is peak load more useful for sizing than average load?
- Why write the assumptions next to the numbers?