Your Cloud Bill Has a Dependency Graph
Treat invoices as architecture topology. Cost topology beats cost accounting when growth has a join.
Cloud invoices is discussed in architecture reviews and post-mortems, often as a reliability topic or a FinOps exercise. The conversation stops at policy slides. Constrange's Observe → Measure → Model series treats it as an engineering economics problem: what does the system actually do, what does that work cost, and what model explains the gap between intent and invoice.
Observe: export cost by resource tag and service. Overlay the runtime dependency graph from traces.
Measure: attribute marginal cost per edge — what does an extra order cost in payments API calls, database reads, egress?
Model: cost propagates like latency. A join that fans out to five services multiplies spend when traffic doubles.
Accounting vs topology
FinOps dashboards sort by account, project, and tag. Architecture diagrams sort by call direction. When growth has a join — checkout calling payments, search, inventory, and fraud — cost accounting hides which edge thickened. Cost topology makes the join visible.
| Shows | Hides | |
|---|---|---|
| Cost accounting | Who pays | Why work multiplied |
| Cost topology | Which edge grew | Org chargeback politics |
| Traffic metrics | Request volume | Per-request work |
Growth with a join
Traffic doubled. Bill tripled. The join is the suspect: N+1 queries, missing cache, synchronous fan-out, cross-region calls added for one feature. Measure cost per successful business event, not per service container hour.
Practical attribution
- Pick one journey and tag spans with business event id
- Sum cloud cost per service on that path for a day
- Divide by successful events — cost per outcome
- Repeat monthly and watch which edge moves
“Invoices are logs written in currency. Read them like telemetry.”Constrange
Questions for your next review
- What would we see if we measured cost topology for one week?
- Which dependency owns the majority of the cost or delay?
- What policy or architecture assumption does the data contradict?
- What is the smallest experiment that would change our model?
The organisations that improve cost topology are not those with the best slogans. They are those that observe honestly, measure without vanity metrics, and update the model when the bill or the trace disagrees with the diagram.
Frequently asked questions
How do I map bill to architecture?
Tag resources by service and team, then overlay call graphs from tracing or service mesh.
Why does cost grow faster than traffic?
Joins amplify work — fan-out, retries, and chatty dependencies scale super-linearly.
What is cost topology?
The shape of spend following dependency edges, not only account hierarchy.
Where do we start?
Pick one revenue-critical journey and reconcile its trace graph with last month's invoice.