Category
deployment patterns
4 articles
Feature Flags Pattern: Decouple Deployments from User Exposure
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 ...
Deployment Architecture Patterns: Blue-Green, Canary, Shadow Traffic, Feature Flags, and GitOps
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...
Canary Deployment Pattern: Progressive Delivery Guarded by SLOs
TLDR: Canary deployment is useful only when the rollout gates are defined before the rollout starts. Sending 1% of traffic to a bad build is still a bad release if you do not know what metric forces rollback. TLDR: Canary is the practical choice when...
Blue-Green Deployment Pattern: Safe Cutovers with Instant Rollback
TLDR: Blue-green deployment reduces release risk by preparing the new environment completely before traffic moves. It is most effective when rollback is a routing change, not a rebuild. TLDR: Blue-green is practical for SRE teams when three things ar...