Reverse String (In-Place & Two Pointers)
System Design Interview Math86,400 sec/day (≈ 10⁵ heuristic)
Back-of-the-Envelope Capacity, QPS & Cache Estimator
Adjust Daily Active Users, requests/day, payload size, and cache hit ratio just like an L5/L6 FAANG or India GCC System Design round to estimate QPS, database origin pressure, 5-year storage, and Redis RAM sizing.
Daily Active Users (DAU)10M
Requests / User / Day25
Peak Traffic Multiplier3x
Avg Payload / Record Size15 KB
CDN / Redis Read Cache Hit Ratio80% (Offloads DB)
Average QPS
2,894
Peak: 8,682 req/sDB Origin Peak QPS
1,736
After 80% cache hit offload5-Year Storage Need
6373.7 TB
Daily delta: 3576.3 GB/day80/20 Hot Cache RAM
715 GB
Peak egress: ~1,017 Mbps| Availability SLA | Downtime / Year | Downtime / Month | Typical Production Architecture |
|---|---|---|---|
| 99.9% (Three 9s) | 8.76 hours | 43.8 minutes | Multi-AZ managed DB + automated health checks |
| 99.99% (Four 9s) | 52.6 minutes | 4.38 minutes | Active-Active Multi-AZ, automated failover & circuit breakers |
| 99.999% (Five 9s) | 5.26 minutes | 26.3 seconds | Multi-Region Active-Active edge routing, Anycast BGP, Raft/Spanner |