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.
Supported in partVerified against the work's full text
The Reactive Streams spec supports one example, a demand-signalling protocol that stops fast publishers overwhelming slow subscribers; HTTP/2, TCP receive window and consumer lag are not covered.
“a fast data source does not overwhelm the stream destination”
- 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.
Supported in partVerified against the work's full text
The Reactive Streams spec defines backpressure, where subscriber demand limits what a publisher may send, but it never names garbage collection, queue drain or cache eviction rates as clearance.
“backpressure is an integral part of this model in order to allow the queues which mediate between threads to be bounded”
- 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¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 2 of 2 citations: 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
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