Comparison
Apply blast radiusvsBlast radius
Apply blast radius
one careless change proposed to destroy the database because everything lives in a single state, and the plan was long enough not to be read.
How much of your estate one apply can affect, which is decided by how the configuration and state are split. A single monolithic state is convenient and means every change is a change to everything; splitting by environment, by lifecycle and by ownership shrinks what any one mistake can reach. It also shrinks plan times, which matters more than it should, because a plan nobody reads is not a control.
Full entry →Blast radius
you ask how much of the product breaks if this one component dies, and design so the answer is not "all of it".
The scope of impact when a given component fails. Reducing it is the point of cells, shards, bulkheads and per-tenant isolation. It is also the right frame for reviewing a change: not "will this break" but "what breaks with it".
Full entry →