Mar 13 · 13 min read · TLDR: Release safety is an architecture capability, not just a CI/CD convenience. Blue-green, canary, shadow traffic, feature flags, and GitOps patterns exist to control blast radius, measure regressions early, and make rollback fast enough to matter...
Join discussionMar 13 · 14 min read · TLDR: Feature flags separate deploy from exposure. They are operationally valuable when you need cohort rollout, instant kill switches, or entitlement control without rebuilding or redeploying the service. TLDR: Flags help only when they are treated ...
Join discussionMar 3 · 7 min read · Feature Flag Tools for Progressive Rollouts Feature flags decouple deployment from release. You merge code to main and deploy it to production, but the new behavior is hidden behind a flag. You turn it on for 1% of users, watch your metrics, bump to ...
Join discussionMar 3 · 11 min read · Deployment Strategies: Blue-Green, Canary, and Rolling Updates Deploying code to production is the most dangerous thing most teams do on a regular basis. Every deployment is a controlled introduction of change into a running system, and every change ...
Join discussionFeb 13 · 5 min read · I had another busy week this week and another day in London, which as I’ve mentioned before, seems to speed up time by a factor of five or so. I had a good week, but I’m quite tired now, so I’m looking forward to a weekend of rest and relaxation. Let...
Join discussion
Feb 13 · 8 min read · Content Role: pillar Feature Flag Implementation: Progressive Rollouts A/B testing and canary releases with LaunchDarkly alternatives Progressive rollouts have become essential for modern software deployment. The ability to release features gradually...
Join discussionFeb 12 · 10 min read · Why Manual Feature Flag Management Fails at Scale Traditional feature flag implementations rely on developers manually creating flags, updating configuration files, coordinating rollout percentages, and remembering to remove flags after full deployme...
Join discussion
