Rollback Strategies That Actually Work: Redeploys, Feature Flags, and Migrations
Blue-green and canary deploys — covered in more depth here — are how you ship forward carefully. Rolling back needs the same care, in the
A technical reference for infrastructure engineers
Practical writing on DevOps, cloud infrastructure and modern delivery — from someone who builds and runs these systems day to day.
Blue-green and canary deploys — covered in more depth here — are how you ship forward carefully. Rolling back needs the same care, in the
Finding and fixing a bottleneck — the practical framework I wrote about earlier — answers “why is this slow.” SLOs answer a different question: how
Platform engineering and FinOps conversations — the shift I wrote about here — eventually run into this exact question from the cost side. “We should
Every “Infrastructure as Code” pitch runs into the same awkward question eventually: if everything is code, checked into git, reviewed and versioned — where does
Understanding how the control plane actually schedules and tracks pods explains what a probe result feeds into. The three Kubernetes probe types get explained by
ArgoCD showed up as one piece of the best-of-breed stack I wrote about replacing an all-in-one platform with, without ever explaining what it’s actually doing
I’ve written before about what adding more instances doesn’t actually fix — this is the narrower question of what should trigger adding them in the
Picking service boundaries is one problem — I’ve covered that separately when writing about bounded contexts and communication between services. What actually crosses those boundaries
Building a CI/CD pipeline from commit to production is one problem for a single project. A monorepo’s CI pipeline usually starts out simple the same
The .tfstate file is the part of Terraform that gets glossed over in most getting-started guides, right up until it’s the reason a deploy breaks