How to test rollback after a database change
A previous build may be available but unable to interpret records written after a schema change.
What to do
- In a test environment start with representative data, apply the change, and run a transaction on the new version.
- Restore the prior software version and check whether it can read the new records and complete the same workflow.
- If the prior version cannot operate safely, document how the team will repair forward or restore and reconcile affected data.
Reference: Google SRE guide to canary deployments.
Related MyNew service: DevOps.