Scope-Bound Cancellation
Scope-Bound Cancellation governs cancellation propagation, shaping system behavior under specific failure modes and workloads.
Definition
Scope-Bound Cancellation is a design property concerning cancellation propagation. It defines how the system behaves under specific conditions — what guarantees hold, what trade-offs apply, and how the mechanism interacts with related techniques. The property is only meaningful when its preconditions are met; outside those conditions it provides no benefit and may add cost.
Context and scope
Apply Scope-Bound Cancellation when designing systems where cancellation propagation matters. It is most useful under partial failure, high load, or correctness requirements. Pair it with observability to verify the claimed behavior in production. Do not assume the property holds without testing the specific configuration and workload.
Common misconceptions
- Scope-Bound Cancellation eliminates all problems in its domain — it only bounds or shapes specific failure modes, not all pathologies.
- Scope-Bound Cancellation is free once you adopt the right tool — the property depends on configuration, workload, and failure pattern, not the product label alone.
Anti-patterns
- Enabling Scope-Bound Cancellation without measuring its cost in latency, availability, or operational complexity under production-like conditions.
- Assuming Scope-Bound Cancellation composes safely with other guarantees — combining mechanisms can introduce new failure modes or negate benefits.
Related concepts
Authoritative source
What it is
Scope-Bound Cancellation is a design property concerning cancellation propagation. It defines how the system behaves under specific conditions — what guarantees hold, what trade-offs apply, and how the mechanism interacts with related techniques. The property is only meaningful when its preconditions are met; outside those conditions it provides no benefit and may add cost.
When to use
Apply Scope-Bound Cancellation when designing systems where cancellation propagation matters. It is most useful under partial failure, high load, or correctness requirements. Pair it with observability to verify the claimed behavior in production. Do not assume the property holds without testing the specific configuration and workload.
Common misconceptions
- Scope-Bound Cancellation eliminates all problems in its domain — it only bounds or shapes specific failure modes, not all pathologies.
- Scope-Bound Cancellation is free once you adopt the right tool — the property depends on configuration, workload, and failure pattern, not the product label alone.
Anti-patterns to avoid
- Enabling Scope-Bound Cancellation without measuring its cost in latency, availability, or operational complexity under production-like conditions.
- Assuming Scope-Bound Cancellation composes safely with other guarantees — combining mechanisms can introduce new failure modes or negate benefits.
Related concepts
- Promise and Task Cancellation (promise-cancellation)
- Structured Concurrency (structured-concurrency)