Core

Napkin math: sizing a system before you draw it

Design rounds put a number in the prompt on purpose. Arithmetic done in the first two minutes eliminates whole classes of architecture and is the difference between designing something and describing something. These are the reference figures and the method for using them.

a free account opens the core tier · no card

RELATED CONCEPTS

Failure domains: what a region, a zone and a cell actually buy you Error budgets: the arithmetic and the decision it forces

PRACTICE THIS IN REAL QUESTIONS

DevOps System Design & ArchitectureDesign a disaster recovery plan for a 5PB data platform with a four-hour recovery objective.→Cloud Platforms & ArchitectureYour service autoscales on CPU and still falls over during traffic spikes. Why, and what would you scale on instead?→DevOps System Design & ArchitectureDesign an authentication service for 100,000 QPS across three regions: 2KB payloads, 10ms processing, 16-core VMs. Do the math out loud.→AI & GPU InfrastructureProduct wants to raise the context limit from 8k to 128k tokens. What happens to your infrastructure?→DevOps System Design & ArchitectureDesign multi-region active-active for a tier-1 API. What breaks, and what does it cost?→DevOps System Design & ArchitectureA payments monolith releases monthly and scaling means buying hardware. Design the migration.→