Rollback Design With Immutable Artifacts and Data Risk
Explore how to design defensible CI/CD rollbacks when application releases, configuration, and database schemas change together. Learn to use immutable image digests, compatibility migrations, expand-and-contract patterns, feature flags, and evidence-based containment while avoiding destructive reversals that could cause data loss.
We'll cover the following...
“We can just roll back” loses credibility when a release also changes a database schema. A defensible design explains what the pipeline can safely reverse after production has accepted new writes, and what it cannot.
An immutable artifact keeps a release fixed after publication, so the application layer is the fastest rollback path. A prior image digest identifies the exact previously verified version; rebuilding the same source is weaker because dependencies or build inputs may have changed.
The three layers a rollback crosses
A rollback involves three interconnected layers.
The application artifact is the ...