Migration and Recovery Battlecards
Recall safe default responses for migration, recovery, and replica-freshness objections.
Can we drop the old column in this release? Rolling deploy with background workers. Your line Only after expansion, backfill, read switch, and proof that no old code path still reads it. Drop belongs in the contract phase. Do not confuse new-code readiness with production-wide compatibility. It turns a yes/no argument into a phased safety check and protects rollback while old workers or clients may still use the old shape. Backup enabled versus recovery proven The restore is the capability the business experiences. Replica lag is only a few seconds, so all reads can use replicas. A user just completed…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in