On this page
01 Every release is a version 02 What makes a rollback safe 03 Practice it
Why we version every deployment and treat the way back as part of the release.
Most teams plan the way forward in detail and the way back in a hurry. The rollback is a chat message, a half-remembered command, and a prayer that nobody changed the schema in the meantime.
Every release is a version
In InfraCore, a deployment is not an event but an object. It has a number, a configuration, a model, and the data contract it was tested against. Going back means selecting an earlier object and making it live again, which is the same operation as going forward.
What makes a rollback safe
The previous version still exists, fully, until you remove it on purpose
Schema changes are additive first, so old and new code can coexist
Traffic moves gradually, with a visible comparison between versions
The third point matters most. A gradual shift turns a rollback from a decision under pressure into a slider you pull back while the dashboard still looks calm.
Practice it
A rollback that has never been used is a theory. We encourage teams to roll back once a month on purpose, in daylight, so the first real one is not the first one.
Confidence in a release is confidence in the way back.
When going back costs one click, teams ship smaller changes more often, and the risk of each one falls. That is the real product benefit, and it has nothing to do with disasters.
Placeholder article. Names, figures and examples in this template are illustrative.
