Backpressure¶
Propagate downstream capacity pressure upstream so producers slow before overload accumulates into failure.
The Diagnostic Story¶
Symptom: One part of a coupled system keeps producing or admitting work faster than the part receiving it can absorb. The backlog grows invisibly, latency climbs, and the downstream side becomes less capable precisely when it needs headroom to recover. The upstream actors keep going because nothing tells them to stop.
Pivot: Make downstream capacity legible upstream. Propagate the stress or saturation signal against the direction of ordinary flow so that producers slow, pause, defer, or prioritize before accumulation becomes overload rather than after.
Resolution: Queue growth stays bounded, the downstream receiver holds enough slack to stabilize, and critical flow continues under prioritization rules. The system sacrifices some throughput and accepts higher latency, but preserves viability and the ability to recover without manual rebuilding.
Reach for this when you hear…¶
[stream processing] “The consumer can't keep up and we're just letting the queue pile up until the whole pipeline falls over.”
[manufacturing / kanban] “Assembly keeps pushing parts to the next station but the station is already full — we need to stop sending until they clear the line.”
[incident response] “We're getting paged faster than we can triage, and new alerts keep coming in while we're still buried in the first wave.”
When This Archetype Applies¶
Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.
Diagnostic problem
An upstream producer can generate or admit flow faster than a coupled downstream stage can absorb it, allowing hidden queue debt or overload to accumulate.
Show the applicability expression
Applicability expression2 distinct conditions
groundedpartly groundedopen
2 conditions, all required.
2Required in every casenumbered 1–2
These hold no matter which pattern applies.
Upstream-downstream rate mismatch · open
An upstream stage can produce or admit flow faster than the downstream stage can absorb it.
This proposition-sized condition was conservatively reconstructed from the authored essence_one_line, compression_statement, components fields; the source file was not modified. In this condition set, the requirement is: An upstream stage can produce or admit flow faster than the downstream stage can absorb it.
Accumulating excess inflow · grounded · 2 illustrations, not alternatives
The coupled path allows excess inflow to accumulate as queue depth, latency, loss, or overload.
This proposition-sized condition was conservatively reconstructed from the authored essence_one_line, compression_statement, components fields; the source file was not modified. In this condition set, the requirement is: The coupled path allows excess inflow to accumulate as queue depth, latency, loss, or overload.
Other requirements and context (1)
Why these sit outside the expression
Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.
Solution feasibilityUpstream production or admission can be slowed, paused, metered, or deferred.
This proposition-sized condition was conservatively reconstructed from the authored essence_one_line, compression_statement, components fields; the source file was not modified. In this archetype, the relevant feasibility condition is: Upstream production or admission can be slowed, paused, metered, or deferred. It identifies something that must be possible or available for the intervention to be workable.
Coverage
1 of 2 conditions grounded · 1 open.
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (6)
- Constraint: Limits possibilities to guide outcomes.
- Feedback: Outputs influence inputs.
- Observability: Infer internal state externally.
- Queueing: Organizes tasks into a waiting line based on arrival and service rates.
- Signaling: Revealing hidden information.
- Threshold: Safe vs harmful levels.
Also references 4 related abstractions
- Coupling: Interdependence among subsystems.
- Flow: Structured movement of energy, matter, or information.
- Resource Management: Allocation of finite assets.
- Trade-offs: Balancing competing priorities.
Editorial Notes¶
Problem Classification¶
Classification: Congestion, Backlog & Flow Breakdown → Persistent Rate Mismatch & Binding Bottleneck
Problem kernel: downstream service limits fail to constrain upstream production rate
Rationale: Both reviewers identify the same structural center: upstream producers continue supplying work faster than the downstream receiver can process because capacity pressure is not propagated upstream. The persistent producer-service rate mismatch is the bottleneck; receiver saturation describes a possible consequence but does not isolate the unsignaled upstream supply imbalance.
Boundary considered: Capacity Scarcity & Resource Contention → Assimilation Saturation & Overload
Why this classification prevailed: Persistent rate mismatch identifies the producer-receiver flow imbalance that binds throughput; assimilation overload centers the bounded receiver's nonlinear degradation once its ceiling is exceeded.
Review outcome: Reconciled after independent review; high confidence.