The idea
If producers can send work faster than consumers can finish it, a queue keeps growing. Backpressure makes the imbalance visible and limits incoming work. Extra buffering may absorb a short burst, but it cannot solve sustained overload.
Design choice
Bound queue size and the amount of work in flight. Decide whether excess work waits, is rejected or is reduced in quality. Choose this behaviour deliberately: silently dropping important updates may be worse than a clear temporary rejection.
Worked example
A thumbnail service allows a fixed number of active transformations. New requests receive a busy response when its queue reaches the documented limit.
Before you ship
- Bound memory and queue length
- Measure queue age as well as depth
- Define overload behaviour
Examples are illustrative. Adapt the checks to your own environment.