Aaron Whitfield
FinOps Practitioner
Aaron has cut eight-figure cloud bills without cutting a single feature. He argues that cost is a design constraint, not an accounting problem.
Designing Cloud Systems With the Bill in Mind
Most cost work happens too late, in a spreadsheet, after the architecture is fixed. By then the available savings are rounding errors — reserved instances and a few idle volumes.
Aaron Whitfield argues for treating cost like latency: a property you design for. He covers the handful of architectural decisions that dominate a cloud bill (egress topology, storage class transitions, compute commitment shape, and data gravity), and how to attribute spend accurately enough that teams can act on it.
Includes the unit-economics model that turns a monthly invoice into a per-request number engineers can optimize.
7 chapters · 306 pages total
FinOps Practitioner
Aaron has cut eight-figure cloud bills without cutting a single feature. He argues that cost is a design constraint, not an accounting problem.