Cost ($) Estimation Playbook
Why this sets you apart
Almost no guide teaches cost estimation — yet “what does this cost to run?” is a senior/staff-level signal. Turning a design into a rough monthly bill shows you reason about trade-offs, not just feasibility.
The formula
Monthly $ ≈ storage_GB × $/GB-mo + compute_hours × $/hr + egress_GB × $/GB + request_millions × $/M
Rough cloud price anchors (order of magnitude)
| Resource | ~Price |
|---|---|
| Object storage (S3-class) | ~$0.02 / GB-month |
| Block storage (SSD/EBS) | ~$0.10 / GB-month |
| Compute (general VM) | ~$0.05 / vCPU-hour (spot ~3–5× cheaper than on-demand) |
| Egress (data out) | ~$0.09 / GB |
| Managed requests/serverless | ~$0.20–$1 / million |
Worked example — the photo service
~27 PB stored (object), modest compute, 1 PB/month egress:
- Storage: 27 × 10⁶ GB × $0.02 ≈ ~$540K/month.
- Egress: 10⁶ GB × $0.09 ≈ ~$90K/month.
- Insight: storage dominates — a tiered hot/warm/cold policy (move cold blobs to archive at ~$0.004/GB) is the biggest lever.
Formulas are standard/public-domain engineering math. Approach and reference-table format adapted from the System Design Primer (CC BY 4.0), Jeff Dean’s latency numbers, the DesignGurus capacity-estimation guide, and Little’s Law.
🤖 Don't fully get this? Learn it with Claude
Stuck on Cost ($) Estimation Playbook? Open Claude, copy a block below, and it'll teach you this exact concept — visually and interactively.
Build the mental picture, not memorization.
I just read a lesson on **Cost ($) Estimation Playbook** (System Design) and want to truly understand it. Explain Cost ($) Estimation Playbook from first principles using ONE vivid real-world analogy and a visual mental model — draw it as ASCII art or a clear step-by-step diagram — with a concrete example using real numbers. Then ask me one question to check I got the mental picture, and wait for my reply. If you're unsure or a claim isn't standard, say so and reason from first principles instead of guessing.
Socratic — adapts to where you're stuck.
Teach me **Cost ($) Estimation Playbook** interactively. Ask me ONE guiding question at a time, wait for my answer, and adapt to my confusion — build the idea with me step by step instead of explaining it all at once. If you're unsure or a claim isn't standard, say so and reason from first principles instead of guessing.
Active recall exposes what you missed.
Quiz me on **Cost ($) Estimation Playbook** with 5 questions, easy to tricky, ONE at a time. Tell me if each answer is right; at the end, explain clearly what I got wrong and why. If you're unsure or a claim isn't standard, say so and reason from first principles instead of guessing.
Intuition + hook + flashcards for long-term memory.
Help me remember **Cost ($) Estimation Playbook** for the long term: give the one-sentence intuition, a memorable hook/mnemonic, a tiny worked example, and 3 active-recall flashcards (Q -> A). If you're unsure or a claim isn't standard, say so and reason from first principles instead of guessing.