Whether gRPC
, dubbo
, rsocket
or webflux
, their API design follows the Reactive Streams specification, and they all provide their own implementation.
Reactor
is the current standard for Reactive libraries .Use the Reactor
library can be better to perform reactive programming.
From the perspective of interface-oriented programming, if Reactive Streams is a design specification, then Reactor
is the interface, and grpc
, etc. provide specific implementation.
Non-Blocking Reactive Streams Foundation for the JVM both implementing a Reactive Extensions inspired API and efficient event streaming support.
Reactive gRPC is a suite of libraries for using gRPC with Reactive Streams programming libraries. Using a protocol buffers compiler plugin, Reactive gRPC generates alternative gRPC bindings for each reactive technology. The reactive bindings support unary and streaming operations in both directions. Reactive gRPC also builds on top of gRPC's back-pressure support, to deliver end-to-end back-pressure-based flow control in line with Reactive Streams back-pressure model.