What are cost trade-offs?
Every architecture decision has a price — in money, complexity, and engineering time. Cost awareness is the habit of weighing those prices, reading a cloud bill, and choosing where to spend. The cheapest option is rarely the goal; the best value for the requirement is.
Why it matters
Cloud bills can balloon quietly, and engineering time is the most expensive resource of all. Engineers who understand cost make decisions the business can afford and can explain why a design is worth its price. It is a mark of seniority that pure coders often lack.
What to learn
- The main cost drivers: compute, storage, egress, managed services
- Reading and attributing a cloud bill
- The cost of complexity, not just infrastructure
- Buy vs build for undifferentiated work
- Right-sizing and autoscaling
- Data egress as a surprise cost
- Engineering time as the scarcest resource
Common pitfall
Optimizing infrastructure cost while ignoring engineering cost. Spending two weeks to shave a small monthly bill is a loss; that time was worth more than the saving. Weigh the engineering hours against the money saved, and remember that managed services often cost more in dollars but far less in time.
Resources
Primary (free):
- AWS — Well-Architected: cost optimization · docs
- Google Cloud — Cost management · docs
- FinOps Foundation — Introduction · docs
Practice
Take a small system design and estimate its monthly cost: compute, database, storage, and egress, with rough numbers. Identify the single biggest line item and one change that would cut it. Then judge whether that change is worth the engineering time. Done when you can defend the trade-off.
Outcomes
- Name the main cost drivers in a cloud system.
- Attribute a bill to the components that cause it.
- Weigh infrastructure savings against engineering time.
- Decide buy vs build for undifferentiated work.