
🛠️ DevOps & SRE · Sankey
Where a company's monthly cloud bill goes, by team and by service type, to spot the biggest savings opportunities.
Drawing diagram…
Sankey of a monthly cloud bill of $100,000: $45,000 compute, $20,000 databases, $15,000 storage, $10,000 data transfer, $10,000 other. Compute splits into production $28,000, staging $9,000 and idle dev environments $8,000. Databases split into production $15,000 and non-production $5,000.
sankey-beta Cloud bill,Compute,45000 Cloud bill,Databases,20000 Cloud bill,Storage,15000 Cloud bill,Data transfer,10000 Cloud bill,Other services,10000 Compute,Production compute,28000 Compute,Staging compute,9000 Compute,Idle dev environments,8000 Databases,Production databases,15000 Databases,Non-production databases,5000 Storage,Backups,9000 Storage,Application data,6000
How a code change reaches production with GitOps: CI builds and tests, the image tag is written to a config repo, and Argo CD syncs the cluster to match Git.
A complete observability setup: OpenTelemetry collects metrics, logs and traces from services, which are stored separately and viewed together in Grafana with alerting.
The stages of a production incident from the first alert to the postmortem, with severity escalation along the way.
Who does what when production breaks: monitoring pages the on-call engineer, an incident channel is opened, customers are updated and the fix is rolled out.
A blue-green setup where a new version is deployed next to the live one and traffic is switched only after it passes checks, allowing instant rollback.
How infrastructure changes are made safely with Terraform: plan on pull request, policy checks, approval, apply and drift detection.