Skip to content
BENIBIX Learn

Rollback vs Hotfix

A rollback and a hotfix both deal with a bad change in the live app, in opposite ways. A rollback goes back to the last version that worked, often in a minute. A hotfix goes forward with a new version that fixes the bug. Roll back first to stop the harm, then ship the hotfix calmly.

Development☁️ DevOps & Cloud

Rollback

Put the last version that worked back after a bad deploy.

A rollback puts the previous working version back after a bad deploy. Instead of fixing the bug while users suffer, you return to what worked. Then you fix the bug calmly and ship again. A good rollback takes one command and a minute or two. It only works if the old build is still saved and the data still fits it.

Example
Jack's new release doubles the error rate. He runs one command, the old version is back in 40 seconds, and he fixes the bug after lunch.
Why it matters
Fast undo makes shipping less scary. Teams that can roll back in a minute are happy to deploy often.
Full entry
Development🚀 Product & Releases

Hotfix

A small, quick release that fixes one big bug in the live app.

A hotfix is a small, urgent release that fixes one serious problem in the live app. It skips the usual wait for the next planned release. It is often made from the code that is live, not from work still in progress. A hotfix still goes through tests, just quickly. The fix is then merged back so the next release has it too.

Example
Jack's checkout stops taking card payments on Saturday. He ships hotfix 2.4.1 within an hour, with only that one fix in it.
Why it matters
Some bugs cost money every minute. A hotfix path lets you fix them now, without shipping half-done work.
Full entry

In one line

Rollback
Put the last version that worked back after a bad deploy.
Hotfix
A small, quick release that fixes one big bug in the live app.