When we use apps like YouTube, Instagram, WhatsApp, or Netflix, we rarely think about what happens behind the scenes.
Millions of users are watching videos, sending messages, uploading photos, and consuming content simultaneously. Yet these platforms continue to work smoothly.
One of the first questions engineers ask when building such systems is:
How big will this system become?
Before choosing databases, servers, caches, or cloud services, it's important to estimate the scale of the problem.
This is where Back-of-the-Envelope Estimation comes in.
What Is Back-of-the-Envelope Estimation?
Back-of-the-Envelope Estimation is a simple technique used to make quick calculations about a system's expected size and traffic.
The name comes from the idea that these calculations are so simple that they could be done on the back of an envelope.
The goal isn't perfect accuracy.
The goal is to understand whether you're dealing with:
- Thousands of users
- Millions of users
- Billions of requests
- Gigabytes of data
- Terabytes of storage
These rough estimates help engineers make better design decisions.
Why Is Estimation Important?
Imagine someone asks you to build a photo-sharing application.
Before writing a single line of code, you'd probably want to know:
- How many users will use it?
- How many photos will be uploaded daily?
- How much storage will be needed?
- How much internet bandwidth will be consumed?
Without these answers, choosing the right architecture becomes difficult.
Estimation helps transform assumptions into measurable numbers.
Understanding Scale Through a Simple Example
Let's imagine a blogging platform with:
- 1 million users
- Each user writes 1 blog per day
- Average blog size is 5 KB
Daily storage:
text id=hm3zvn
1,000,000 × 5 KB = 5 GB per day
Yearly storage:
text id=iyu0sm
5 × 365 = 1.8 TB per year
A simple estimate immediately tells us that storage requirements will grow significantly over time.
Estimating User Traffic
Storage is only one part of the picture.
We also need to estimate how often users interact with the system.
Suppose:
- 1 million users
- Each user reads 10 blogs per day
Total requests:
text id="70tqyv"
1,000,000 × 10 = 10 million requests/day
Requests per second:
text id="7q4i5s"
10,000,000 ÷ 86,400 ≈ 116 requests/second
This helps engineers understand the amount of traffic the system must handle.
Why Exact Numbers Don't Matter
One common misconception is that estimations must be perfectly accurate.
In reality, they rarely are.
User behavior changes.
Traffic patterns change.
Businesses grow unexpectedly.
The purpose of estimation is not to predict the future exactly.
It's to understand the order of magnitude of the problem.
Knowing whether a system needs to handle 100 requests per second or 100,000 requests per second is far more important than calculating the exact number.
Real-World Applications
Companies use estimation when building:
Video Streaming Platforms
Estimating:
- Daily video uploads
- Storage requirements
- Streaming bandwidth
Social Media Platforms
Estimating:
- Posts created per day
- Feed requests
- Notification traffic
Messaging Applications
Estimating:
- Messages sent per second
- Active users
- Data storage growth
Cloud Storage Services
Estimating:
- File uploads
- Storage consumption
- Download traffic
The Power of Simple Calculations
Many large-scale engineering decisions start with surprisingly simple math.
A few quick calculations can reveal:
- Whether a single server is enough
- Whether caching is required
- How much storage is needed
- How fast the system might grow
This is why estimation remains one of the most valuable skills in system design.
Key Takeaways
- Back-of-the-Envelope Estimation helps understand system scale.
- It focuses on rough calculations rather than perfect accuracy.
- It helps estimate traffic, storage, bandwidth, and growth.
- It allows engineers to make informed architectural decisions.
- Every large-scale system begins with understanding its expected size.
Final Thoughts
Before building any system, it's worth asking a simple question:
"How big can this become?"
Back-of-the-Envelope Estimation provides a practical way to answer that question.
While the calculations are simple, the insights they provide can influence every architectural decision that follows.
Understanding scale is often the first step toward building systems that can grow and succeed over time.
Top comments (0)