Cost and Sustainability for Software Architects
Cost and sustainability treats money and resource use as design constraints. FinOps brings engineering and finance together to model, allocate and optimise cloud spend, and capacity planning forecasts demand so you provision enough without waste, including using efficient instance types and scaling policies.
Stage: Security, Reliability and Cost · Part of the Software Architect roadmap · Last reviewed 19 November 2026
What to learn in Cost and Sustainability
- Build a cost model for a service from usage drivers
- Tag resources so spend can be allocated to teams
- Compare on-demand, reserved and spot pricing trade-offs
- Forecast capacity from growth and peak load data
- Identify idle or oversized resources
- Weigh cost against reliability when choosing redundancy
Cost and Sustainability interview questions
What is FinOps?
FinOps is a practice where engineering, finance and business teams share responsibility for cloud spending. It involves visibility through tagging and reporting, optimisation of usage and commitments, and ongoing governance so cost is part of design decisions.
How do you plan capacity for a system with seasonal spikes?
Measure baseline and peak load from past data, forecast growth, load test to find per-instance limits, and set autoscaling with safe headroom. For predictable events, scale ahead of time and use cheaper capacity for the steady baseline.
Where Cost and Sustainability fits in the Software Architect roadmap
Cost and Sustainability belongs to the Security, Reliability and Cost stage (advanced level), which takes about 7 hours. The non-negotiables.
Other units in this stage
Back to the full Software Architect roadmap