Explain like I'm five · SRE

What is a Rollback?

Rollback, told as a story about not fixing things on the spot — just going straight back to yesterday's version.

today's updated versionlet me fix it right here, right nowsomething's off, and fixing it on the spot makes it worse

Something's off, and fixing it on the spot makes it worse.Tinkering with it before you know what's wrong only tangles it further.

the more tools you grab, the longer it takesrushing to fix it on the spot only invites more mistakes

Rushing to fix it on the spot only invites more mistakes.The more you rush, the clumsier it gets, and the longer it takes.

today's version, acting uprevert right heredon't fix it in place — revert firstrevert first, then calmly find out why

Don't fix it in place — revert first.Revert first, then calmly find out why.

If something's off, revert firstfixing it comes later
Keep past versions well-storedso reverting is easy
After reverting, find the cause calmlywithout blame
Practice reverting ahead of timeso it's ready when it's urgent
today: brokenyesterday: finethe code reverts, all at once, like this

Today's version (broken) → revert → yesterday's version (fine).The code reverts like this — all at once.

the code's back to normalGUEST LOG40 bookings made todayyesterday's version never saw themdata needs careful handlingcode can revert, but the guest log that piled up still needs care

Code can revert, but data needs care.The guest-log gap that built up in between sometimes can't be reverted.

In one breath

Rollback = when something's off, don't fix it in place — revert to yesterday's version first, then calmly find out why.

A response strategy where, if something breaks right after a deploy, you revert to the last stable version first rather than debugging on the spot. It minimizes recovery time, leaving root-cause analysis for a calmer moment afterward.

When grown-ups say it

Rollback
Going straight back to yesterday's version. Recovery comes first — root-cause analysis comes later.
Release versioning
Keeping yesterday's version safely stored. Good storage is what makes reverting easy.
Roll-forward
Fixing forward instead of reverting back. Slower than rollback, but sometimes the only option.
Easy-to-revert design
Building things so you can always go back to yesterday. Prepared ahead of time, so reverting is fast when it matters.
vs. canary
Testing on 1%, versus reverting everything. A bad canary leads straight into a rollback
vs. blue-green
Flipping the sign back sends you right back. Blue-green makes rollback especially fast
Data migration risk
Records that don't follow the code back. The guest log doesn't revert as simply as the code does.
Checkpoint
A marked point to revert back to. The more often you mark one, the less you lose.
Next story
The Four Gauges on the Control-Room Wall →
Want another term as a picture book? Request →