Just read a CIO article saying cloud costs are now the second biggest expense for midsize IT companies, behind labor and ahead of pretty much everything else.
That matches what I keep hearing from people running real systems. Cloud spend doesn’t feel like a line item you control anymore, it feels like something you react to after the fact. Bills go up, dashboards light up, and then everyone scrambles to shave a few percent without touching the parts that are actually painful.
What stood out to me is that a lot of this cost doesn’t seem to come from raw compute or storage anymore. It comes from all the things glued around the system to make it work at scale. Remote caches, coordination layers, metadata services, control planes, cross region calls. Stuff that exists because there isn’t a good local place for certain kinds of state to live.
Once those pieces sit on the critical path, they get hit constantly, they add latency, and they quietly become some of the most expensive parts of the system. At that point cloud cost stops being an optimization problem and starts feeling like a structural one.
I’m curious how this lines up with other people’s experience. How much of your cloud bill is tied to coordination and state rather than actual business logic. Have you had to add external services just to keep latency acceptable. Have you reached the point where you’d rather rethink architecture than keep paying the tax.
Genuinely interested in what people are seeing in practice, not vendor takes or budgeting advice.
