Protocols
Saved & recent

Backpressure

Also called: producer throttling, downstream demand

Backpressure propagates a downstream capacity limit upstream so that a producer slows, pauses or limits outstanding work. It can use demand signals, credits, bounded buffers or blocked writes. Transport flow control is one mechanism, but application queues also need a policy for work that arrives faster than it can be processed.

If a producer offers 100 messages per second while a consumer handles 40, an unbounded queue would grow by 60 messages per second while those rates persist. Backpressure can make the producer wait as capacity fills. It does not create extra processing capacity; the system still needs to decide what to delay, reject or discard when demand exceeds its limits.

Related
Flow control, gRPC, Message broker
Further reading
gRPC — Flow Control
without feedback 100/s 40/s +60/s while rates hold producer consumer with backpressure 40/s bounded queue full feedback pauses admission illustrative messages per second
With the hypothetical rates shown, an unconstrained queue grows by 60 messages per second. Backpressure limits upstream production or admission.

View in the full Protocols collection