liveBook · Manning

Rollback

Also called roll back, rolled back, rolling back, revert

Rollback is the reversal or discarding of changes to restore data, software, or system state to an earlier state.

How 14 Manning books explain it

Machine Learning Platform Engineering

A rollback is the restoration of a deployed application to a previously functioning version.

How it is used
Protects production availability by restoring a functioning application version after a problematic Deployment update.
How deep it goes
Explains rollback through rolling updates, ReplicaSets, status checks, events, and a kubectl command, without detailing revision internals.
Examples
Uses a hello-joker Deployment, v1-to-v2 image update, rollout events, status output, and kubectl rollout undo.
What you can do after
Operate/configure Kubernetes Deployments by applying image updates, inspecting rollout status, and undoing failed releases.

Read how Machine Learning Platform Engineering explains rollback →

LLM Customization and Fine-Tuning

Reverting a deployed system to an earlier version when the current version causes problems.

How it is used
Provides a recovery path when a production model promotion causes behavioral or safety degradation.
How deep it goes
Sets a recovery target and retention policy, outlines response phases, and recommends quarterly drills against the serving stack.
Examples
Uses an illustrative help-desk safety regression and a registry rollback from v2 to v1, followed by a validated retrain.
What you can do after
Practice rollback using a non-production registry and quarterly drills against the real serving stack.

Read how LLM Customization and Fine-Tuning explains rollback →

.NET in Action, Second Edition

A rollback discards the changes made within a database transaction.

How it is used
Prevents a failed money transfer from leaving only one account balance updated.
How deep it goes
Works through transaction creation, commit, exception handling, rollback, and change-tracker cleanup in an asynchronous repository method.
Examples
Tests a transfer of 120 between accounts holding 100 each, then checks that both balances remain unchanged.
What you can do after
Apply it via EF Core transactions to reverse failed transfers and clear stale tracked state.

Read how .NET in Action, Second Edition explains rollback →

Architecting an Apache Iceberg Lakehouse

An operation that makes an earlier table snapshot the current state without necessarily deleting files introduced by later snapshots.

How it is used
Supports recovery from bad writes, accidental deletions, dropped partitions, unintended schema changes, and data corruption.
How deep it goes
Explains immutable snapshots, metadata-pointer movement, time-travel contrast, and catalog coordination, but not a complete cleanup procedure.
Examples
Uses snapshot IDs or timestamps for historical queries and the rollback_to_snapshot procedure for recovery.
What you can do after
Diagnose incidents with historical snapshots and restore a previous table state for subsequent queries and writes.

Read how Architecting an Apache Iceberg Lakehouse explains rollback →

Microservices Patterns, Second Edition

A rollback is a recovery operation that restores data or system state to a previously valid state by discarding or reversing changes.

How it is used
Frames rollback as a production recovery response within deployability scenarios.
How deep it goes
Shows two failure-triggered rollback scenarios but does not specify rollback mechanics.
Examples
Uses configuration-related startup failure and unacceptable REST endpoint latency after query optimization.
What you can do after
Evaluate rollback requirements for deployment failures while keeping SLAs intact.

Read how Microservices Patterns, Second Edition explains rollback →

Designing AI Systems

A rollback is the restoration of a deployed system to a previously known version or configuration after a problematic change.

How it is used
Protects production deployments by restoring the prior version when application-level metrics show that a change is unhealthy.
How deep it goes
Explains rolling updates, metric-based decisions, version tracking, and service operations, but does not detail rollback data-plane mechanics.
Examples
Uses container-image replacement after elevated error rates and progressive policy enforcement with shadow and canary stages.
What you can do after
Operate/configure deployments through versioned Workflow Service operations and restore the previous container image after a failed rollout.

Read how Designing AI Systems explains rollback →

Think Like a Software Engineering Manager

A rollback is the restoration of a software system or deployment to a previous known state after a change causes problems.

How it is used
Restores production stability after a deployment produces unwanted customer effects.
How deep it goes
Defines a prepared response and gives one database-remediation example, without detailing broader implementation mechanics.
Examples
Uses duplicate customer records and database queries as the concrete restoration example.
What you can do after
Operate/configure it by preparing and executing a predefined procedure that restores a stable production state.

Read how Think Like a Software Engineering Manager explains rollback →

Kubernetes in Action, Second Edition

A rollback is the reversion of a deployed application workload to an earlier version or revision.

How it is used
Reverts failed Deployment or StatefulSet updates to an earlier revision while following, or exposing, the workload’s update strategy.
How deep it goes
Explains commands, revision inspection, rollout timing, paused Deployments, and manual OnDelete Pod replacement, but not revision storage internals.
Examples
Uses kubectl rollout undo, rollout history, targeted revision commands, and manually deleted StatefulSet Pods as operational examples.
What you can do after
Operate/configure rollback with kubectl, inspect revisions, select an older Deployment revision, and manually complete OnDelete StatefulSet rollback.

Read how Kubernetes in Action, Second Edition explains rollback →

Acing the Certified Kubernetes Administrator Exam, Second Edition

Rollback is the restoration of an application to a previous known configuration or version after a change.

How it is used
Supports rapid recovery when a Kubernetes Deployment change introduces an application bug.
How deep it goes
Explains revision history, annotations, undo behavior, and status verification, but does not detail rollback internals.
Examples
Uses an Apache Deployment, image-tag change, rollout history, change-cause annotations, undo output, and rollout-status verification.
What you can do after
Operate/configure Deployments with kubectl rollout undo, annotate rollback reasons, and verify successful recovery.

Read how Acing the Certified Kubernetes Administrator Exam, Second Edition explains rollback →

GitHub Actions in Action: Continuous integration and delivery for DevOps

Rollback is the process of returning a deployment or system to a previously known good version or state.

How it is used
Uses health, metric, and release controls to stop or reverse an unsafe deployment.
How deep it goes
Explains rollback triggers and operational techniques, but stops short of detailing rollback storage or recovery implementation.
Examples
Demonstrates readiness polling, health monitoring, metric comparison, gradual traffic exposure, and feature-toggle reversal.
What you can do after
Operate/configure deployment gates and release controls that restore the last known good behavior when signals indicate failure.

Read how GitHub Actions in Action: Continuous integration and delivery for DevOps explains rollback →

Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform

Rollback is the restoration of infrastructure configuration or system state to an earlier known-good version.

How it is used
Uses forward-moving IaC changes to restore functionality after failed infrastructure updates.
How deep it goes
Explains commit inspection, git revert, and pipeline application, but stops short of general troubleshooting internals.
Examples
Uses a removed database role, Git history, git revert, and static-analysis recovery as concrete examples.
What you can do after
Operate IaC recovery by reverting commits and rolling forward a known-working configuration through the deployment pipeline.

Read how Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform explains rollback →

Vibe Engineering

Rollback is the process of reverting a system or codebase to a previously known state after an unsuitable change or failure.

How it is used
Protects production systems from unsuitable generated changes by making recovery part of the development process.
How deep it goes
Defines rollback operationally within staged delivery and observability, but does not specify commands, storage mechanisms, or recovery algorithms.
Examples
Uses staged commits, sandboxes, canaries, production instrumentation, and an orchestrated agent fleet as operational examples.
What you can do after
Operate/configure delivery systems that include rollback before autonomous or generated changes reach production.

Read how Vibe Engineering explains rollback →

Spring Start Here, Second Edition

A rollback is the operation that undoes a transaction's changes after the transaction cannot complete successfully.

How it is used
Protects data consistency by restoring earlier state when an operation in a transaction fails.
How deep it goes
Defines rollback through a failed transaction step and restoration; stops short of explaining Spring’s implementation.
Examples
Uses a money transfer where subtracting succeeds but adding to the destination account fails.
What you can do after
Evaluate/understand how rollback prevents partial updates from leaving data inconsistent.

Read how Spring Start Here, Second Edition explains rollback →

Kargo in Action

A deployment operation that returns an environment to a previous artifact or application state.

How it is used
Uses rollback to restore a known-good state when a deployment needs reversal.
How deep it goes
Explains the need for a promotion record and the risk of mutable tags, but gives no rollback procedure.
Examples
Uses a Friday production hotfix and a mutable tag to illustrate uncertainty about the prior state.
What you can do after
Understand why a promotion record is needed to identify a trustworthy rollback target.

Read how Kargo in Action explains rollback →

Also covered in

What to know first

Related concepts

Questions about rollback

What is rollback?

Rollback is the reversal or discarding of changes to restore data, software, or system state to an earlier state.

Which Manning books explain rollback?

Machine Learning Platform Engineering, LLM Customization and Fine-Tuning, .NET in Action, Second Edition, Architecting an Apache Iceberg Lakehouse, Microservices Patterns, Second Edition, Designing AI Systems, Think Like a Software Engineering Manager, Kubernetes in Action, Second Edition and 6 more.

What should I know before learning rollback?

Manning books that teach rollback usually introduce production, deployment pipeline, versioning and error rate first.

What is the difference between rollback and roll-forward?

Rollback is the reversal or discarding of changes to restore data, software, or system state to an earlier state. Roll-forward is a recovery technique that corrects a faulty or failed change by applying a subsequent corrective change rather than reverting to a previous state.

What is rollback part of?

Rollback is part of database transaction. A database transaction is a bounded unit of database operations whose changes are treated as one logical whole, typically committed or rolled back together.

What is rollback also called?

Rollback is also called roll back, rolled back, rolling back or revert.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.