[CAMEL-11236] camel-grpc - improve streaming capabilities to bridge reactive streams

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.20.0
• Component/s: camel-grpc
• Estimated Complexity: Unknown
• Assignee: Nicola Ferraro
• Reporter: Nicola Ferraro
• Created: 08/May/17 11:21
• Updated: 08/Sep/17 13:03
• Resolved: 08/Sep/17 13:03

Description

We have grpc producer-only capabilities at the moment. After the implementation of the grpc consumer side, it would be interesting to investigate how we can make it easy to use grpc as transport for reactive streams across network in different JVMs.

Something like this from the sending side:

from("reactive-streams:datasource")
to("grpc:my.Data?mehod=stream&host=xxx&port=yyy");

And this from the receiving side:

from("grpc:my.Data?mehod=stream&port=yyy")
to("reactive-streams:datasink");

Then from a RX implementation one can send a stream of data to datasource and receive it using the datasink stream in the other JVM.

We can leverage the streaming capabilities of grpc (payloads and return types can be "streams" of data).

Grpc has also an internal way to handle backpressure using a bounded internal buffer. We can "bridge" the grpc backpressure mechanism to the reactive-streams one, to have a proper flow control.

We should give to reactive-streams subscriptions an identifier to distinguish between a new method call or a continuation of the current stream (something like this is reported in CAMEL-11140).

Issue Links

• links to: GitHub Pull Request #1763