Deployment Strategy
8 items tagged with "deployment-strategy"
Best Practices8
Blue-Green Deployment Strategy
Operating two identical production environments to achieve zero-downtime releases and quick rollbacks.
Canary Releases Best Practice Guide
Progressively rolling out new software to a small subset of users to minimise risk before full release.
Continuous Delivery
A discipline where software is built so it can be released to production safely at any time, with every change proven release-ready by an automated pipeline.
Deployment Pipeline Pattern
An automated, staged path that takes every code change from commit through build, tests, and successive environments, providing a single auditable route to production.
Expand and Contract Database Migration Pattern
A zero-downtime schema change technique that adds new structures, migrates reads and writes in phases, then removes the old structures once nothing depends on them.
Immutable Infrastructure
An operations model where servers and components are never modified after deployment; changes ship as freshly built, versioned replacements rather than in-place edits.
Deployment Rings
A progressive rollout strategy that releases changes to expanding audience groups, or rings, validating each ring before exposing the next to limit blast radius.
Dark Launching
Deploying new functionality to production in a hidden state and exercising it with real traffic before exposing it to users, to validate behavior and capacity safely.