reactive-streams-dotnet

Ensures receivers control data flow to prevent resource exhaustion, with rules mandating fully non-blocking behavior and bounded queues for predictable usage.

Defines core interfaces like IPublisher and ISubscriber, enabling different implementations to work together seamlessly within a processing graph, as emphasized in the goals.

Subscribers control queue bounds via demand signaling, allowing bounded queues and preventing out-of-memory errors even with infinite streams, as detailed in the subscriber-controlled queue bounds section.

Preserves the benefits of parallel resource use by mandating that all aspects, including backpressure communication, are non-blocking and avoid synchronous bottlenecks.