> Term

Rollback

The process of reverting a system to its previous functional state after a flawed deployment.

Detailed Explanation

A rollback undoes a release. It involves restoring the previous version of application code, and critically, managing any database schema or data state changes that occurred during the brief time the flawed version was live. Rollbacks are an emergency safety valve, not a feature.

Why It Matters

Being able to roll back quickly minimizes Mean Time To Recovery (MTTR) when a critical defect escapes into production.

Common Failure Mode

Failing to account for database migrations. Rolling back the application code but leaving the new database schema in place often causes the old application code to crash.

Practical Example

Traffic is shifted back to the v1.0 servers via the load balancer after the team discovers that the v1.1 deployment is failing to process payments.

Production Manifestation

Re-deploying the previous Docker image tag or routing traffic back to the old environment in a blue/green deployment setup.

Frequently Asked Questions

What is Rollback in short?

The process of reverting a system to its previous functional state after a flawed deployment.

What is the most common failure mode?

Failing to account for database migrations. Rolling back the application code but leaving the new database schema in place often causes the old application code to crash.

AI Summary

The process of reverting a system to its previous functional state after a flawed deployment. Being able to roll back quickly minimizes Mean Time To Recovery (MTTR) when a critical defect escapes into production.