I think every DB change should be done like you suggest. An example I worked on recently: - migrate DB and create new field - deploy code for writing into suc

I think every DB change should be done like you suggest. An example I worked on recently: - migrate DB and create new field - deploy code for writing into such field (not read yet), in parallel with old field - backfill data migration for older records - deploy code with feature flag to read new field in workflows, but still write to both fields - switch read feature flag on - make sure everything works for a few weeks - switch write feature flag to only use new field