Fanout Amplification
partialContainedcascading failure · fan out propagation
Blast Radius
6%
1/18 nodes
Time to Detect
Milliseconds to seconds for downstream CPU or connection saturation signals. Root cause identification (tracing to the amplification point) typically requires distributed tracing and may take minutes to hours in investigation.
Preventive Mitigations
3
Confidence
StrongImpacted Components
Fan-Out on Write
architecture pattern · Directly connected to failure mode 'Fanout Amplification' via risk propagation path in the topology.
Failure Cascade
Fan-Out on Write
Fanout Amplification (fan out propagation) directly affects these components.
Severity at this step: partial
Detection Signals
Recovery time estimate: Immediate relief by reducing upstream inbound rate or adding downstream capacity. Permanent fix requires code change and deployment: hours to days.
Mitigation Checklist(3 preventive, 1 reactive)
Collect all N item IDs from a list response, issue a single batch query to the downstream service (SELECT WHERE id IN (...)), and map results back to the list. DataLoader (originally from Facebook/GraphQL) implements this automatically per request: it accumulates lookups within a single request tick and issues one batched query.
Replace N single-item queries with one query that returns all N items. For ORM-based N+1, use eager loading (SELECT_IN or JOIN fetch strategy). For microservices, expose a batch endpoint (GET /users?ids=1,2,3) and call it once per list response.
Set a maximum recursion depth (e.g., 5 hops for graph traversal, 3 levels for nested category resolution) and return a truncated result beyond that depth rather than continuing to recurse.
Within a single request, cache already-resolved items by ID. If the same author appears in 30 posts in a feed, only resolve them once. Request-scoped memoization avoids the redundant downstream calls without changing the API.
Affected Systems
Workloads
Blast radius analysis is derived from structured topology and failure mode knowledge. It models structural propagation patterns, not measured production behavior. Actual incident scope depends on runtime conditions, traffic, and recovery actions in place at the time of failure.