Cloud cost is a design decision, not a billing problem

The monthly cloud bill is one of the few engineering metrics that arrives with a number attached, which is why it gets treated as a finance problem. It is not.

The first round of savings is administrative: rightsizing instances, deleting idle resources, moving storage to the right tier. That work is worth doing and it usually buys you twenty per cent.

The second round is architectural. Chatty services that cross an availability zone on every request, synchronous calls where an asynchronous queue would do, and caches with no eviction policy — these are design decisions that show up as money.

The useful habit is to give every significant component an owner and a cost-per-day figure on the same dashboard as its latency. When the number is visible next to the behaviour that drives it, engineers fix it without being asked.