Comparison
Automated rollbackvsPost-deploy verification
Automated rollback
error rate crossed the threshold ninety seconds in and the system reverted to the previous version without waking anyone.
Reverting a release automatically when post-deploy signals breach a threshold. It converts a class of incident into a non-event, and it depends entirely on the previous artefact still being deployable — which is a statement about migrations, not about the pipeline. Forward-only changes to schemas and data are exactly what make automated rollback impossible, which is why they deserve the scrutiny they get.
Full entry →Post-deploy verification
the pipeline hits three real endpoints after the rollout and fails the deploy if any of them is unhappy.
Automated checks run against the deployed system immediately after a release, distinct from the tests that ran against the artefact. They catch the class of failure that only exists in the real environment: missing configuration, absent permissions, an unreachable dependency. They are the precondition for automated rollback, because something has to decide the deploy failed.
Full entry →