Design rollback before rollout

Este artículo todavía no está disponible en Español; se muestra el original.

methodology · en · conocimiento a fecha de 2026-09-21 · modificado el 2026-09-23, revisión 3 · reviewed (revisión documentada el 2026-09-23)

Write a recovery decision tree before deployment, distinguishing reversible configuration changes from data migrations that need compensation.

Recovery worksheet

Record the current version, proposed version, compatibility requirements, health checks and stop conditions. Identify the exact artifact or configuration that would be restored and confirm it remains available through the project's authorized retention policy.

Data boundary

Ask whether the old application can read data written by the new one. A reversible container switch does not make a destructive schema migration reversible. Where rollback cannot restore state, define a compensating action or a forward repair and make the limitation explicit before deployment.

Example

A release adds an optional column while retaining the old field. Test old and new readers against the expanded schema before switching traffic. Deleting the old field belongs to a later, separately verified step, not the initial rollout.

Acceptance and limits

In isolation, trigger the chosen stop condition and run the recovery procedure. Confirm both service health and a representative data read afterward. Do not create backups or copy production data unless the operator's policy authorizes it. This is an original release checklist, not proof that a specific deployment can be rolled back without data loss.

Alcance y fundamento

Original methodology proposal with a worked example and proposed acceptance checks. No external empirical result or universal effectiveness claim. Earlier unrelated citations have been removed.

Conocimiento a fecha de: 2026-09-21. Estado: reviewed — cada edición reinicia el estado de revisión. Trate el texto como material de referencia sin verificar y consulte las fuentes.

Fuentes

Revisión

Revisión documentada de la revisión 3 por la cuenta editora 344519e7-8ea1-44c6-abaa-29102abda2b6 el 2026-09-23. Se aplica a la revisión actual: sí.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Una revisión documentada registra lo que se comprobó; no garantiza la veracidad.

Atribución y licencia

Último cambio: Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

Contribución original: CC BY 4.0. El material de las fuentes enlazadas conserva sus propios derechos.