Back-of-the-envelope estimation in HLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is back-of-the-envelope estimation in system design?

It is a quick, rough calculation to estimate system requirements or capacity without detailed data, helping to make early design decisions.

beginner

Why is back-of-the-envelope estimation important in early system design?

It helps to quickly check feasibility, guide architecture choices, and avoid over- or under-provisioning resources before detailed analysis.

beginner

Name three common parameters estimated in back-of-the-envelope calculations.

User count, request rate (requests per second), and data storage size are commonly estimated parameters.

intermediate

How does back-of-the-envelope estimation relate to scalability?

It provides a rough idea of how much load a system must handle, helping to plan for scaling strategies like load balancing or sharding.

intermediate

What is a key limitation of back-of-the-envelope estimation?

It is approximate and may miss edge cases or detailed bottlenecks, so it should be followed by detailed analysis and testing.

What is the main goal of back-of-the-envelope estimation?

A To write production-ready code

B To create detailed architecture diagrams

C To perform load testing

D To quickly estimate system requirements

Back-of-the-envelope estimation is used for quick, rough calculations to guide early design decisions.

Which of the following is NOT typically estimated in back-of-the-envelope calculations?

A Number of users

B Exact database schema

C Data storage size

D Request rate

Exact database schema design requires detailed analysis, not rough estimation.

Back-of-the-envelope estimation helps primarily with:

A Early feasibility checks

B Detailed debugging

C Final deployment

D User interface design

It helps quickly check if a system design is feasible before investing more effort.

Which is a limitation of back-of-the-envelope estimation?

A It is very slow

B It requires complex tools

C It may miss detailed bottlenecks

D It replaces detailed testing

Because it is approximate, it can miss detailed issues that need deeper analysis.

Back-of-the-envelope estimation is most useful during which phase?

A Early system design

B Final testing

C Production monitoring

D User training

It is used early to guide design decisions before detailed work begins.

Explain how you would perform a back-of-the-envelope estimation for a new social media app's server capacity.

Think about how many people might use the app and how often they interact with it.

Describe the benefits and limitations of using back-of-the-envelope estimation in system design.

Consider why quick estimates are helpful and what risks come with rough calculations.

Practice

1. What is the main purpose of back-of-the-envelope estimation in system design?

easy

A. To quickly estimate system requirements using simple calculations

B. To write detailed code for the system

C. To create a full architecture diagram

D. To perform in-depth performance testing

Solution

1. Step 1: Understand the goal of back-of-the-envelope estimation

   This method is used to quickly guess system needs without detailed work.

2. Step 2: Compare options to the goal

   Only To quickly estimate system requirements using simple calculations matches the quick estimation purpose; others are detailed tasks.

3. Final Answer:

   To quickly estimate system requirements using simple calculations -> Option A

4. Quick Check:

   Quick estimation = To quickly estimate system requirements using simple calculations [OK]

Hint: Focus on quick, simple calculations for early guesses [OK]

Common Mistakes:

• Confusing estimation with detailed design
• Thinking it involves coding or testing
• Assuming it requires full diagrams

2. Which of the following is the correct way to start a back-of-the-envelope estimation for a web service's daily traffic?

easy

A. Calculate exact user behavior with detailed logs

B. Estimate average users per hour and multiply by 24

C. Design the database schema first

D. Write the full API specification

Solution

1. Step 1: Identify the starting point for traffic estimation

   Back-of-the-envelope estimation uses simple averages, not detailed data.

2. Step 2: Evaluate options for simplicity and relevance

   Estimate average users per hour and multiply by 24 uses average users per hour times 24 hours, a simple and effective start.

3. Final Answer:

   Estimate average users per hour and multiply by 24 -> Option B

4. Quick Check:

   Simple average x time = Estimate average users per hour and multiply by 24 [OK]

Hint: Use simple averages and multiply by time units [OK]

Common Mistakes:

• Starting with detailed logs instead of rough estimates
• Jumping to design before estimating traffic
• Confusing estimation with specification writing

3. You estimate a system will have 10,000 users daily, each making 5 requests on average. What is the total number of requests per day?

medium

A. 100,000 requests

B. 2,000 requests

C. 15,000 requests

D. 50,000 requests

Solution

1. Step 1: Multiply users by requests per user

   10,000 users x 5 requests each = 50,000 requests.

2. Step 2: Confirm total requests per day

   The total is simply the product of users and requests per user.

3. Final Answer:

   50,000 requests -> Option D

4. Quick Check:

   Users x requests = 50,000 [OK]

Hint: Multiply users by average requests per user [OK]

Common Mistakes:

• Adding instead of multiplying
• Mixing up users and requests
• Choosing an option too large or too small

4. A designer estimated 1 million requests per day but forgot to consider peak hour traffic. What is the likely problem with this estimation?

medium

A. Ignoring average request size affecting storage needs

B. Overestimating total daily traffic causing wasted resources

C. Underestimating peak load leading to potential system overload

D. Not including user authentication time

Solution

1. Step 1: Understand the impact of ignoring peak traffic

   Peak traffic is often much higher than average, so ignoring it underestimates load.

2. Step 2: Identify the consequence of underestimation

   System may overload during peak times if capacity is based on average only.

3. Final Answer:

   Underestimating peak load leading to potential system overload -> Option C

4. Quick Check:

   Ignoring peak = underestimation risk [OK]

Hint: Always consider peak, not just average, traffic [OK]

Common Mistakes:

• Assuming daily average covers peak needs
• Confusing storage with traffic load
• Focusing on unrelated factors like authentication time

5. You need to estimate the storage required for a photo-sharing app. Each photo is 3MB, and you expect 500,000 uploads per month. What is the approximate monthly storage needed?

hard

A. 1.5 TB

B. 150 GB

C. 15 GB

D. 1.5 GB

Solution

1. Step 1: Calculate total storage in MB

   500,000 photos x 3 MB each = 1,500,000 MB.

2. Step 2: Convert MB to TB

   1,500,000 MB ÷ 1024 ≈ 1465 GB ÷ 1024 ≈ 1.43 TB, approximately 1.5 TB.

3. Final Answer:

   1.5 TB -> Option A

4. Quick Check:

   Uploads x size ≈ 1.5 TB [OK]

Hint: Multiply count by size, then convert units [OK]

Common Mistakes:

• Forgetting to convert MB to GB
• Mixing up MB and GB units
• Using wrong multiplication factors