System Design Card 446 — Cost Efficiency / Breakdown
Concern
Reasonable designs are not only fast and reliable; they are proportionate to the business value and expected usage. Precomputing everything, storing everything forever, or over-replicating can turn a technically plausible design into an economically poor one.
What Breakdown means for this concern
In BASIC, the Breakdown step is where you clarify the product goal, workload shape, and non-functional requirement that will dominate the design. For Cost Efficiency, that means the candidate should make this concern visible at the right moment instead of bolting it on at the end.
Design move
A good move is to split the problem before trying to solve it. Tie the concern back to the user flow, the workload, and the dominant trade-off. That keeps the design grounded and makes it easier for the interviewer to follow why a cache, queue, replica, partition, or rate limiter is actually necessary.
Common miss
The miss is optimizing for elegance or scale mythology instead of realistic cost trade-offs. BASIC helps because the staged flow keeps this concern proportional to the prompt and connected to the rest of the architecture.
BASIC prompt
“When I reach the Breakdown stage, how does Cost Efficiency change the architecture, the trade-offs, or the review checklist?”