a standard for asynchronous stream processing with non-blocking back pressure
- stream processing
- back pressure
Mainly only 3 interfaces:
Publisher<T>: Data provider following the demand from Subscriber
Subscriber<T>: Subscribe data from Publisher
Subscription: used to both signal desire for data and cancel demand between a Publisher and a Subscriber
And there's one more:
Processor<T,R>: Subscriber and Publisher
Flux & Mono ( Project Reactor )
In my understandings, the interfaces of Reactive Streams are low level contracts for standardization. Therefore we need more convenient implementations on top of them. One of them is Project Reactor.
Both Mono and Flux implements Publisher.
Now it seems a bit clear for me. I'm feeling like Reactor provides definition of flow. I will continue to check Mono & Flux.