In the previous post, we talked about what back-of-the-envelope estimation is and why it matters.
Now we move to the most important concept in system design:
QPS (Queries Per Second)
π What is QPS?
QPS simply means:
How many requests your system handles every second
This is the starting point of almost every system design problem.
β±οΈ The Key Conversion You Must Know
To convert daily traffic into real-time load:
- 1 day β 100,000 seconds
This approximation makes calculations fast and simple.
π’ Basic Example
If your system gets:
- 10 million requests per day
Then:
10,000,000 / 100,000 β 100 QPS
So your system handles roughly:
100 requests per second
π§ Think in Patterns (Not Calculations)
Instead of calculating every time, learn these patterns:
1M requests/day β ~10 QPS
10M requests/day β ~100 QPS
100M requests/day β ~1,000 QPS
1B requests/day β ~10,000 QPS
Once you internalize this, estimation becomes instant.
β‘ Why QPS Matters So Much
QPS directly impacts:
- number of servers required
- database load
- system performance
Example:
- 100 QPS β small system
- 10K QPS β large system
π§© Real Example
Letβs say:
- 50 million requests/day
Using pattern:
- 50M β 5 Γ 10M
- 10M β 100 QPS
So:
- 50M β ~500 QPS
β οΈ Common Mistakes
β Trying to be too accurate
You donβt need exact numbers.
β Forgetting unit conversion
Always convert:
per day β per second
β Getting stuck on math
Focus on approximation, not precision.
π§ Key Insight
Youβre not solving math problems.
Youβre answering:
βIs this system handling hundreds, thousands, or millions of requests per second?β
π Whatβs next?
In the next post, weβll cover:
- Storage estimation
- How systems grow over time
- GB/day β TB/year thinking
If this helped, drop your thoughts π
Top comments (0)