Rollbacks are a lie

Video thumbnail: Rollbacks are a lie
Jun 18, 202643s video lengthThe Pragmatic Engineer

The Signal

The speaker argues that simple "rollback" buttons are a dangerous, frequently misunderstood default for stateful software. The core tension is that while users instinctively want an 'undo' for failing systems, the presenter asserts this causes state and schema desynchronization, demanding a 'roll forward' approach to recovery instead.

The Case

  • Databases and other persisted information constitute "state" that often cannot be cleanly undone, making a simple revert operation technically unsafe.
  • Reversing code versions while leaving upgraded data schemas in place creates a mismatch, where old code blindly attempts to interface with a schema it no longer correctly understands.0:15
  • The recommended recovery path for a system failure—such as a bug in 'version 2'—is to ship a 'version 3' containing the fix, rather than attempting a reversion to the prior state.
  • The presenter uses schema changes as a diagnostic stress test to show customers why their request for a universal rollback button is fragile, though the speaker's claim that most users have only avoided failure through 'sheer luck' remains an unsupported assertion.0:34
  • While the technical risk of code/schema mismatch is documented, the speaker’s demand to 'avoid ever talking about rollback' is an overconfident stance that presumes a single architectural paradigm for all software systems.

The 1 Minute Signal Take

The technical case against simple rollback in stateful systems is strong and well-reasoned. Skip the video; the summary covers the full scope of the operational argument, and the additional color amounts to anecdotal industry posturing.

Pro Analysis

Strategic Significance

In modern distributed systems, the assumption that software can be 'undone' is a legacy mental model that leads to catastrophic data corruption or service outages. Shifting to a forward-only deployment mindset is a prerequisite for high-availability architecture.

Who Should Care

  • Site Reliability Engineers (SREs): To design recovery workflows that minimize state inconsistency.
  • Engineering Managers: To align customer expectations regarding system reliability and recovery times.
  • Database Administrators: To enforce strict migration patterns that avoid the need for structural rollbacks.

Contrarian Takeaway

Rollback, traditionally praised as a safety feature, is actually a net negative for system stability in the presence of complex state, as it encourages engineers to ignore the risks of data schema drift.

Share this

Tags

Written by: 1 Minute Signal Editorial Team