Rolling, canary, feature flag, or blue-green: how should a change reach users?

Deployment puts code into an environment; release exposes behavior to users. Treating them as the same event makes rollback slower and increases blast radius. The right rollout method depends on whether old and new versions can coexist, which signals detect harm, and how quickly the team can stop exposure.

Choose the control you actually need

• Rolling deployment: gradually replaces instances and fits compatible changes that can safely serve traffic in parallel.
• Canary release: sends a small, representative slice of traffic to a new version and expands only if defined signals remain acceptable.
• Feature flag: separates code deployment from feature exposure and can target cohorts, but adds configuration states and cleanup obligations.
• Blue-green: keeps two environments and switches traffic, supporting fast reversal at greater infrastructure and data-compatibility cost.

Define safety signals before rollout

Google SRE describes canarying as a partial, time-limited deployment evaluated against a control. Select user-visible errors, latency, completion of critical paths, saturation, and business-integrity checks that could justify stopping. A canary without a comparison, enough traffic, or an accountable decision maker is only a smaller launch.

Protect state and compatibility

Use backward-compatible schema and API changes when versions overlap. Decide how queued jobs, sessions, caches, and mobile clients behave across versions. A rollback that cannot read data written by the new release is not a safe rollback.

Close the rollout

Remove obsolete flags, document the final state, and review unexpected signals. Feature flags can reduce release risk but permanent dormant branches increase test combinations and operational ambiguity. Every temporary control needs an owner and expiry condition.

Kiwi can help establish proportionate release practices with an embedded team. Production access policy, regulated change control, and formal service objectives require the organization’s authorized owners.