FinOps treats cloud spending as an operational concern: capacity choices create recurring costs, so workloads must be sized against demand, availability, and outage tolerance. section 9.6
Mistake #48: assuming the cloud has infinite capacity.
- Oversizing avoids immediate growth pressure but creates tangible recurring costs; undersizing saves money but may require a restart and outage when capacity increases. section 9.6
- Review recommendations from Azure Advisor or AWS Trusted Advisor, then weigh right-sizing against reservations, savings plans, committed spend, and service availability. section 9.6
Mission-critical versus less-important workloads
A five-nines system may justify an initially oversized virtual machine, while a less important application can use a right-sized machine and tolerate downtime during growth. section 9.6
