Dev.to WebDev 🛠 Dev 👁 0 📖 1 min read

Back-of-the-Envelope Estimation: Applying It to Real Systems

So far, we’ve covered: QPS (requests per second) Storage estimation Bandwidth Bottlenecks Now comes the most important part: How do you actually use all of this in real system design? 🚀 The Goal Bac

So far, we’ve covered:

  • QPS (requests per second)
  • Storage estimation
  • Bandwidth
  • Bottlenecks

Now comes the most important part:

How do you actually use all of this in real system design?

🚀 The Goal

Back-of-the-envelope estimation is not about formulas.

It’s about answering:

“Can this system handle the expected load?”

🧠 The Mental Framework

Whenever you see a system design problem, follow this:

1. Estimate QPS
2. Estimate Storage
3. Estimate Bandwidth
4. Identify Bottleneck
5. Roughly size the system

Let’s apply this to real examples.

🔗 Example 1: URL Shortener

Assumptions:

  • 10M URLs created per day
  • each URL is accessed 100 times

Step 1: QPS

  • Writes:
10M/day → ~100 QPS
  • Reads:
1B/day → ~10K QPS

Step 2: Storage

  • ~2 KB per URL
10M × 2 KB → ~20 GB/day

Step 3: Bandwidth

Reads dominate:

  • small payload (~1 KB)
10K × 1 KB → ~10 MB/sec

Step 4: Bottleneck

  • QPS is high (reads)
  • storage grows steadily
  • bandwidth manageable

👉 Read traffic is the main concern

🔗 Example 2: Messaging System

Assumptions:

  • 100M users
  • 20 messages/user/day

Step 1: QPS

2B/day → ~20K QPS

Step 2: Storage

  • ~1 KB per message
2B KB/day → ~2 TB/day

Step 3: Bandwidth

20K × 1 KB → ~20 MB/sec

Step 4: Bottleneck

  • storage grows very fast
  • real-time delivery required

👉 Storage + delivery latency are key challenges

🔗 Example 3: Video Streaming

Assumptions:

  • 1B views/day
  • each view streams ~5 MB chunks

Step 1: QPS

1B/day → ~10K QPS

Step 2: Bandwidth

10K × 5 MB → ~50 GB/sec

Step 3: Bottleneck

👉 Network bandwidth is the biggest challenge

🧠 What You Should Notice

Across systems:

  • URL shortener → read-heavy
  • messaging → storage-heavy
  • video streaming → bandwidth-heavy

Different systems break in different ways.

⚡ The Real Skill

You’re not solving math problems.

You’re learning to quickly answer:

  • Is this system small or massive?
  • What will fail first?
  • Where should we optimize?

🔑 Final Takeaway

Back-of-the-envelope estimation helps you:

  • think clearly under uncertainty
  • make quick architectural decisions
  • avoid over-engineering

🎯 You’re Now Ready To

  • approach system design problems with confidence
  • estimate system scale quickly
  • identify bottlenecks early

If you followed along this series, you’ve built a strong foundation.

What system would you like to estimate next? 👇

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.