Back-of-the-Envelope: The Art of Rapid System Estimation

TL;DR
Back-of-the-envelope (BOTE) is a rapid calculation method leveraging basic math and standard system constants to evaluate a product's feasibility, scale, and underlying cost. The core formula: Assumptions + Product Metrics + Physical Constants = Resource Estimation (QPS, Storage, Bandwidth).
1. What is Back-of-the-Envelope (BOTE)?
"Back of the envelope" is a pragmatic metaphor for performing quick, rough calculations to derive an approximate estimate. In Product Management and System Design, BOTE serves as the critical bridge translating Business Metrics (user volume, engagement frequency) into Engineering Metrics (server resources, bandwidth, memory).
The core components of a BOTE workflow include:
- Traffic Estimates: Calculating the number of Queries Per Second (QPS).
- Storage Estimates: Quantifying the data generated daily and its compounded accumulation over years.
- Bandwidth Estimates: Measuring data transferred into (Ingress) and out of (Egress) the system.
- Memory Estimates: Determining the RAM required to cache frequently accessed data (typically leveraging the 80/20 rule).
2. When should you apply it?
BOTE is not a substitute for rigorous capacity planning; rather, it acts as an early validation filter. You should deploy BOTE in the following scenarios:
- Feasibility Checks: When a stakeholder requests a feature like "tracking driver location every single second." BOTE helps you quantitatively prove that the storage and ingestion costs might far outweigh the potential revenue.
- System Design / Product Execution Interviews: BOTE is the mandatory first step to shape architectural decisions. A system designed for 100 QPS (manageable on a single server) is fundamentally different from one built for 100,000 QPS (requiring Microservices, Load Balancers, and Database Sharding).
- Cost Estimation: Rapidly determining whether infrastructure costs will cannibalize the product's Unit Economics.
3. Step-by-Step Guide
Executing a BOTE estimation requires mental agility in converting metrics. Here is the standard cognitive framework:
Step 1: Establish Base Assumptions Always begin with Daily Active Users (DAU) or Monthly Active Users (MAU). Do not obsess over exact precision; choose round, logically sound numbers. Example: "The system has 10 million registered users. I will assume a 10% DAU (1 million). On average, each user triggers 5 requests per day."
Lý thuyết là chưa đủ. Hãy biến nó thành bản năng!
Thực hành ngay với các bài tập tương tác
Thực hành Framework này ngay