Case studies
Real-world scenarios from cloud cost, DevOps and database work. Each one walks through the symptoms, how the cause was found, the fix, and what to take away.
The Azure bill nobody could explain
Spend crept up for a year and nobody owned it. Tracing it resource by resource turned up idle VMs, orphaned disks and dev running all weekend.
Azure Cost Management, Resource Graph, Azure Advisor, Azure CLI
Read the case study
The database that slowed down every Monday
A weekly report and the app fought over the same table. One composite index and a read replica for reporting ended the Monday slowdowns.
PostgreSQL, pg_stat_statements, EXPLAIN ANALYZE, Read replicas
Read the case study
Deploys that only worked from one laptop
Releases ran by hand from one machine. A pipeline with tests, staging and one-click rollback made them routine for the whole team.
GitHub Actions, Docker, Bicep, Azure App Service
Read the case study
Moving a live database with minutes of downtime
Logical replication kept the new server in sync for days, then a rehearsed cutover switched traffic in under a minute with no lost writes.
PostgreSQL logical replication, Managed PostgreSQL, pg_dump --schema-only
Read the case studyNothing in this category yet.
How these are written
Every case study follows the same structure, so you can skim to the part you care about.
Seeing one of these right now?
Describe it in a few lines. I'll tell you what I'd check first.
