How deeply does Think Like a Software Engineering Manager cover rollback?

Defines a prepared response and gives one database-remediation example, without detailing broader implementation mechanics.

Rollback

As explained in 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.

A rollback restores a production deployment to its previous known state when a change causes unwanted customer effects. It is a predefined response, not an improvised fix. section 12.2.4

A practical rollback procedure should:

Be written into the deployment checklist and remain accessible before deployment begins. section 12.2.4
Start when the deployment affects customers or threatens system stability. section 12.2.4
Specify concrete restoration actions rather than relying on manual improvisation. section 12.2.4

Duplicate customer records

If a deployment creates duplicate records in the customer table, the rollback procedure may direct operators to run database queries that identify and delete the duplicates, restoring system stability. section 12.2.4

How Think Like a Software Engineering Manager covers it

Cover of Think Like a Software Engineering Manager

liveBook manning.com

Read Think Like a Software Engineering Manager on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Machine Learning Platform EngineeringA rollback is the restoration of a deployed application to a previously functioning version.
liveBook manning.com

.NET in Action, Second EditionA rollback discards the changes made within a database transaction.
liveBook manning.com

Architecting an Apache Iceberg LakehouseAn operation that makes an earlier table snapshot the current state without necessarily deleting files introduced by later snapshots.
liveBook manning.com

Kubernetes in Action, Second EditionA rollback is the reversion of a deployed application workload to an earlier version or revision.
liveBook manning.com

Acing the Certified Kubernetes Administrator Exam, Second EditionRollback is the restoration of an application to a previous known configuration or version after a change.
liveBook manning.com

GitHub Actions in Action: Continuous integration and delivery for DevOpsRollback is the process of returning a deployment or system to a previously known good version or state.
liveBook manning.com

Infrastructure as Code, Patterns and Practices: With examples in Python and TerraformRollback is the restoration of infrastructure configuration or system state to an earlier known-good version.

Compare how 8 books explain rollback →

Related concepts

roll-forwardcontrasts with · 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.
database transactionpart of · A database transaction is a logical unit of database operations whose changes are committed together or rolled back as a whole.
feature flaguses · A feature flag is a configuration control that conditionally enables, disables, or selects a software feature or behavior.
load balanceruses · A load balancer is a hardware or software component that distributes incoming network traffic or requests among multiple destinations, such as servers or service instances.
kubectl rollout undoimplemented by · kubectl rollout undo is a Kubernetes command that reverts a workload to a previous recorded revision.

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.