Reactive Streams Specification for the JVM¶
Reactive Streams Special Interest Group. (2015). Reactive Streams Specification for the JVM.
Cited by¶
2 citations across 2 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Backpressure
- In software and streaming systems it is a first-class signal — reactive-streams frameworks, HTTP/2 flow control, TCP's receive window, consumer lag — each a channel preventing slow consumers from being drowned by fast producers.
This sourceDefines the asynchronous non-blocking backpressure protocol — the Subscriber's `request(n)` demand signal that gates Publisher emission so unbounded buffering is avoided.
- In software and streaming systems it is a first-class signal — reactive-streams frameworks, HTTP/2 flow control, TCP's receive window, consumer lag — each a channel preventing slow consumers from being drowned by fast producers.
- Clearance Rate
- In software, garbage collection rates, queue drain rates, and cache eviction rates are clearance, and the backpressure pattern explicitly recognizes that a downstream component's clearance rate bounds the acceptable upstream input rate.
This sourceDefines backpressure: a downstream consumer signals demand so the producer cannot push faster than the consumer's drain (clearance) rate, bounding intermediate queues — the clearance-rate-respecting design pattern.
- In software, garbage collection rates, queue drain rates, and cache eviction rates are clearance, and the backpressure pattern explicitly recognizes that a downstream component's clearance rate bounds the acceptable upstream input rate.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:eee6cad95d86 · see in the full table