liveBook · Manning

Rollback

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

Rollback is a recovery response when a production deployment fails to start or causes unacceptable performance. Deployability scenarios use it to restore service without violating SLAs. section 5.5.1

Rollback is triggered by detected problems such as:

  • A configuration problem that prevents the updated component from starting. section 5.5.1
  • Unacceptable REST endpoint latency after deployment, attributed to an optimized query. section 5.5.1

How Microservices Patterns, Second Edition covers it

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 it assumes
Assumes a tested deployment pipeline and detected failures, without teaching those mechanisms.
What you can do after
Evaluate rollback requirements for deployment failures while keeping SLAs intact.
How it connects
Connects rollback to deployment pipelines, production deployment, and service-level agreements.

Also explained in

Compare how 14 books explain rollback →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.