Capacity planning: turn users into requests, storage, and bandwidth
Capacity Planning
3 of 5
Storage Estimation
Tiny objects × billions of users = numbers that will surprise you.
A single tweet is tiny — 280 characters, about 350 bytes. But Twitter gets 500 million tweets *per day*. That tiny object, multiplied by that many users over time, is how you end up needing an exabyte-scale object storage system. The formula is always the same.
Formula
Daily storage = writes/day × avg object size × replication factor
Use decimal units here: 1 KB = 1,000 bytes, 1 GB = 10⁹ bytes, 1 TB = 10¹² bytes, 1 PB = 10¹⁵ bytes. Binary units (KiB, GiB, TiB) use powers of 1,024. Calculate raw first, then multiply by replication and retention days.
Tiny! Text is almost free.
200,000 ÷ 350 ≈ 571: one image is about 571× a tweet in bytes
Media dominates. Text barely registers.
Durability isn't free
At $0.023/GB on S3, that's ~$250,000/month
This is why Twitter built their own object storage
Takeaway: You can't store 70 PB affordably on a general cloud. The math forces you into CDN + tiered storage + compression + object lifecycle policies.
