The long-term viable approach is to not make forward-backward incompatible migrations in short period of time. If your system is truly distributed (multiple ma

The long-term viable approach is to not make forward-backward incompatible migrations in short period of time. If your system is truly distributed (multiple machines hosting it), then if one server performs migration that deletes the table, then the other server stops working. You must have 2 checkins and 2 rollouts: Create a new table while maintaingin the old one -- and let it bake in; and then delete the old table a week later (or whatever is your cadence/release cycle).