Capacity planning: turn users into requests, storage, and bandwidth
Capacity Planning
4 of 5
Bandwidth & Latency Budget
Ingress is cheap. Egress will bankrupt you. Here's the math.
Cloud providers charge almost nothing for data coming *in*. They charge a lot for data going *out* (egress). A system with 100:1 read/write ratio β like any social feed β sends 100Γ more data than it receives. This is the number that forces CDNs into the architecture.
Formula
Egress = RPS Γ avg response size Γ read:write ratio
Latency budget = total allowed response time split across every component in the path.
Negligible. Almost always free.
20 GB/s = 160 Gbps. You can't buy enough NICs for this.
CDN handles 90% of reads from edge β origin only sees 2 GB/s
65ms headroom for error, retries, slow paths
Takeaway: Without the CDN math, your architecture won't make sense. WITH it, you see exactly why a CDN isn't optional at scale β it's load-bearing infrastructure.
