Sheet ⁨03⁩ · ⁨Case studies⁩Surveyed ⁨2026⁩

Case Studies

In-depth engineering case studies: the problem, the constraints, the architecture decisions, how it was built, and the measurable results.

From Blue-Green to Progressive Delivery with Argo Rollouts

From Blue-Green to Progressive Delivery with Argo Rollouts

The incident that started this was not caused by carelessness. It was caused by someone being careful. A release went out at 14:20 on a Tuesday. Error rate climbed within ninety seconds. The on-call

Secrets Management Migration to Vault Without an Outage

Secrets Management Migration to Vault Without an Outage

This project did not start with a security review. It started with a resignation. A senior engineer gave notice, and someone asked the reasonable question of what they could still log into after thei

A Service Mesh Rollout That Was Worth It

A Service Mesh Rollout That Was Worth It

The request that started this was not "can we have a service mesh". It was an auditor asking how we encrypted traffic between services, and the honest answer being that we mostly did not. Everything i

Cutting p99 Latency 60% with a Caching Rearchitecture

Cutting p99 Latency 60% with a Caching Rearchitecture

The complaint that started this was not about speed. It was a support ticket saying the dashboard "sometimes doesn't load," from a customer whose account was roughly forty times larger than our median

Replacing Cron Chaos with an Event-Driven Pipeline

Replacing Cron Chaos with an Event-Driven Pipeline

The handover note said "check the pipeline runs" and nothing else. Behind that sentence were 41 cron jobs spread across 6 EC2 hosts, some chained by sleep 900 because someone had once needed job B t

Hardening a CI/CD Supply Chain to SLSA Level 3

Hardening a CI/CD Supply Chain to SLSA Level 3

The question that started this was from an auditor, and it was a fair one: can you prove that the container running in production is the one your pipeline built from the commit you think it was? We ha

Taming a 3am Pager: SLOs and Error Budgets That Stuck

Taming a 3am Pager: SLOs and Error Budgets That Stuck

A platform team was losing people to burnout, and the cause was the pager. On-call meant a phone that went off day and night with alerts about CPU, memory, and pod restarts, the overwhelming majority

Multi-Region Active-Active for a Payments API

Multi-Region Active-Active for a Payments API

A payments API that moves real money had been running comfortably in a single AWS region for years. It was reliable until the day it was not: a regional control-plane incident took the whole service o