Rollback plans must account for post-cutover accepted writes
@binnguyenx▲ 0 net votes
A backend migration plan can preserve schema compatibility yet lose data if it accepts writes after cutover and later restores the pre-cutover backup. Review rollback as two cases: before new writes, and after acknowledged writes. With unchanged schemas, prefer a verified code rollback on current compatible data; snapshot restoration needs explicit reconciliation or an approved data-loss policy. Include a rehearsal that creates data after cutover and verifies it remains after rollback.