Protocol
Test what remains after an experiment is switched off
A switch can stop an experimental path. Recovery also has to account for the data and actions that path has already produced.
Before you use it
- Use when
- When innovation is useful but experimental changes could destabilize the stable core.
Keep this limit in mind
- Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner.
Current editorial reading
Put effects inside the boundary
Before running the experiment, list its writes, queued work and external actions. Decide which effects will be isolated, reversed or reconciled, and who owns recovery. For example, a trial classifier can write proposed labels to a separate test store. Disabling the trial then stops new labels without leaving customers with experimental labels that the normal system must interpret.
Rehearse the return path
Test the old behavior against state produced by the experiment, including mixed versions where relevant. AWS’s rollback guidance explains why shared data and protocol changes can prevent a clean return even when each version works on its own. An unchanged output schema is not enough if the experiment changes the meaning of stored values. Check that normal work resumes and that residual effects have a known disposition.
Take it with you
Keep consumers independent of experimental internals, but verify recovery separately. If an effect cannot be contained or recovered, describe that limit before the trial; do not call it reversible merely because the switch works.
Sources and evidence (1)
What we checked
AWS identifies shared persistent state and protocol changes as rollback hazards when old and new versions interpret data differently.
Selected first-party engineering passages, not a general empirical safety study. The classifier and semantic-value example are independent editorial applications.
Ensuring rollback safety during deployments · Printed p. 2: Standalone vs. distributed software deployments; Problems with protocol changes
AWS tests transitions through mixed versions, full deployment and rollback under representative traffic rather than relying only on separate version tests.
Successful switching is insufficient evidence of recovery. The draft adapts the transition-testing principle; it does not claim every effect can be reversed or certify any actual experiment.
Ensuring rollback safety during deployments · Printed pp. 5–6: Verifying that a change is safe for rollback
Editorial sources (1)
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTest what remains after an experiment is switched off
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaBreak a dependency before optimizing inside it
Original edition evidence and sources
These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.
Parnas showed that modularization outcomes depend on decomposition criteria and argued for boundaries that hide changeable design decisions to improve flexibility and comprehensibility.
This is foundational software-design reasoning; organizational adaptations require separate validation.
On the Criteria To Be Used in Decomposing Systems into Modules · Abstract and design comparison
Original edition, downloads and provenance
The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.
Version 0.1.0
No review details are supplied for this edition.
Read the original edition and overlay as JSON · Release details