Question 1

How to set up reactive gRPC with Spring Reactor?

Accepted Answer

Use the protobuf compiler plugin to generate stubs and include the reactor dependency. Refer to the reactor sub-directory README for configuration details and demos.

Question 2

Reactive gRPC vs Akka gRPC: which one should I use?

Accepted Answer

For Akka-based systems, use Akka gRPC as it's mature and production-ready. Reactive gRPC is better for RxJava or Spring Reactor integrations where back-pressure is critical.

Question 3

Does reactive gRPC support back-pressure in bidirectional streams?

Accepted Answer

Yes, it implements end-to-end back-pressure via HTTP/2 and Reactive Streams, but the flow control can be complex and not always intuitive, as explained in the documentation.

Question 4

How to handle exceptions in reactive gRPC client-server communication?

Accepted Answer

Exceptions are propagated with gRPC status exceptions, but server-to-client errors are more predictable than client-to-server, which can be timing-dependent and less reliable.

Question 5

Is reactive gRPC good for Android apps with RxJava?

Accepted Answer

Yes, for RxJava on Android, it should work since generated code targets Java 8, but test thoroughly as underlying library support varies.

Question 6

What are the limitations of reactive gRPC's flow control?

Accepted Answer

Flow control isn't purely reactive; it interacts with HTTP/2 byte streams and gRPC message buffers, so calls like request(1) may not translate directly, requiring careful reasoning.

reactive-grpc

What is reactive-grpc?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions