liveBook · Manning

Finops

As explained in Grokking Software Architecture

A collaborative practice for managing and optimizing cloud spending across engineering, finance, and business teams.

FinOps makes cloud spending a shared architectural concern for engineering and finance. Because provisioned resources keep costing money even when idle, teams forecast costs, track usage, and eliminate waste. section 9.7.1 section 9.12

Reviewing a user-profile service

When reviewing infrastructure for a user-profile service, consider the cloud bill alongside design goals: the architecture should not accidentally make the company’s costs unsustainable. section 9.7.1

How Grokking Software Architecture covers it

How deep it goes
Defines the practice through forecasting, usage tracking, and waste reduction without detailing an operational workflow.
Examples
Uses a user-profile service infrastructure review and the ongoing cost of provisioned cloud resources as examples.
What you can do after
Evaluate cloud designs against the bill and account for costs from provisioned resources, even when they are unused.
How it connects
Links cloud architecture and infrastructure review with cloud financial management and finance teams.

Also explained in

Compare how 2 books explain finops →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.