Skip to content

PATTERN Cited by 1 source

Multi-cloud lifeboat

Shape

Build a separate-cloud stand-in that intentionally implements only the operations critical to customers during a primary-platform outage. It is not a full replica: it uses a purpose-built architecture, accepts eventually consistent data, shares neither code nor infrastructure with the primary, and exposes a deliberately degraded experience. (Source: sources/2026-08-13-aws-recovery-strategies-to-meet-data-residency-requirements)

Why it works

A lifeboat avoids forcing the primary platform onto the lowest common denominator of two providers. Independent software and infrastructure reduce the chance that one defect or correlated infrastructure failure disables both sides; limiting functionality keeps cost and verification scope bounded.

Operational contract

  • State the critical operations the lifeboat will serve and explicitly reject the rest.
  • Design for eventual consistency, rather than coupling it to primary-platform transaction paths.
  • Regularly test activation and prove there are no primary-environment dependencies.
  • Assess whether a country-wide disruption could affect all major providers; multi-cloud within one geography is not automatically a complete disaster boundary.

Seen in

Last updated · 622 distilled / 1,953 read