jargon

Backend & systems·Deployment, release and rollback

you cannot go back because the migration already ran, so the only way out is to ship another change quickly.

Roll forward

Also calledfix forward

Fixing a bad release by deploying a newer version rather than reverting. It is necessary when a rollback would be destructive — irreversible migrations, consumed messages, already-published events. It is riskier under incident conditions, so it should be a consequence of the change's shape, not a habit.

Commonly confused with