Zero-Downtime Hot Migration and Rollback on Multi-Container Single Hosts: Lossless Schema Evolution behind a Shared Tunnel and a Ten-Second Stop-the-Bleeding Contract: chapter answers
A few containers on one host, a shared tunnel in front and a database behind make the most common production architecture of small teams, and the popular story is that a blue-green switch has zero downtime and rollback is instant. This book tests the founding claim that the downtime of a blue-green switch is not zero, that connection draining and the health-check interval set the worst interruption, and that expand-contract migration pushes irreversible steps later and markedly raises the rollback success rate. Checking the sources calls for a correction: Humble and Farley's Continuous Delive…
DOI pending · monograph page goes live after publication · 5DL-B-269 · 中文版
- Chapter 1 · Blue-Green Is Not Zero Downtime: the Interruption Window Set by Health Checks, Failure Thresholds and Connection Drain
Chapter 1 shows that a common probe configuration needs 35.0 seconds at worst to notice a dead backend, that a 10 second drain still cuts 9.5699 long connections in expectation, and that not one of four hundred fixed-se… - Chapter 2 · Expand-Contract Migration: the Rollbackability Graph and Pushing Irreversible Steps to the End
Chapter 2 draws migration as a rollbackability graph: with a 24 hour bake, expand-contract has a rollback failure rate 10.39 times lower than a one-shot migration, and with two coexisting containers only 8 of 560 interl… - Chapter 3 · The Availability Markov Chain: How Repair Time Eats the Yearly Budget
Chapter 3 uses an availability Markov chain to show that the five-nines budget leaves only 12.1 seconds per bad release, and that expand-contract cuts yearly downtime from 2431.9 to 155.9 minutes. - Chapter 4 · Many Containers on One Host behind a Shared Tunnel: Common-Cause Failure, Reconnect Backoff and Memory Headroom for Dual Running
Chapter 4 shows that two colours on one host are capped by common-cause failure, saving only 262.1 minutes at a common-cause share of 0.5, and that a single tunnel connector with a short fixed retry recovers within ten… - Chapter 5 · Lossless Evolution of a Production Database: Backfill Pace, Dual-Write Verification and the Write-Freeze Window
Chapter 5 gives the backfill batch size, chunked-hash verification and the write freeze; a random sample of 1000 rows has only a 0.3017 chance of seeing one of 7 bad rows. - Chapter 6 · The Ten-Second Stop-the-Bleeding Contract: Convolving the Time Budget, False and Missed Alarms, and the Rot of Rollback Paths
Chapter 6 splits the ten-second contract into three terms: with an automatic decision and a warm old version the 95th percentile is 6.90 seconds, while a cold start meets the budget with probability only 0.0020; probing… - Chapter 7 · The Classical Sources Examined: "When a Course Runs Out, Change" and the Ship of Theseus
Chapter 7 examines "when a course runs out, change; changing, it opens a way; open, it endures" and the ship of Theseus, with expand-contract raising the best change frequency to 52.7 a year. - Chapter 8 · The Empirical Loop: a Local Drill Checklist, the Hot-Migration Interruption Window Calculator and a Pre-Registered Test
Chapter 8 gives a ten-step local drill checklist, the distilled Hot-Migration Interruption Window Calculator and a pre-registered test, in which 59 consecutive drills without a breach are needed to say with 95 % confide…
Illustrative model calculation, not a live quote