[
https://issues.apache.org/jira/browse/CALCITE-5255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598091#comment-17598091
]
Francis Chuang commented on CALCITE-5255:
-----------------------------------------
Big +1 for this. I've been using gRPC in Go for inter-micro-services
communication/rpc and it is very easy to use with a lot of batteries included.
I use https://github.com/envoyproxy/protoc-gen-validate to provide annotation
rules for each requests using protobuf options and it generates the appropriate
code in Go, c, java and python.
Will protobuf over pure http be deprecated / dropped at some point? Protobufs
are not easy to construct by hand, so it's not very easy to use them with an
HTTP debugging client such as curl and postman. On the other hand, there are
general-purpose gRPC clients such as https://github.com/bloomrpc/bloomrpc
> gRPC transport for Avatica
> --------------------------
>
> Key: CALCITE-5255
> URL: https://issues.apache.org/jira/browse/CALCITE-5255
> Project: Calcite
> Issue Type: Bug
> Components: avatica
> Reporter: Julian Hyde
> Priority: Major
>
> CALCITE-840 added a protobuf transport for Avatica, as an alternative to the
> original JSON transport. In this change, we propose to add another transport
> that uses [gRPC|https://en.wikipedia.org/wiki/GRPC].
> We should be able to re-use the existing serialization of data and metadata
> to and from protobuf. Compared to the existing protobuf-over-HTTP transport,
> the gRPC transport will benefit from gRPC's authentication, flow control, and
> streaming.
> This task would add support on the Java server and client. Upgrading the Go
> client to use gRPC could be a separate task.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
