GRPC: A high performance, open source, general RPC framework

Re:GRPC: A high performance, open source, general RPC framework by Matthias247 on Saturday February 28, 2015 @09:56AM (#9123803)

Does HTTP2 have guarantees that the connection is really reused for multiple requests or could a user agent (or HTTP library) silently use multiple connections for different requests?

I think this makes a major difference for RPC applications, because with a single connection you have a guarantee that all messages will be retrieved in the same order that they were sent.

E.g. with a persistent websocket connection I have the guarantee that all messages will be in order. With mulitple HTTP/1.1 requests I don't have it. Don't know about HTTP/2.

And of course the requirements about such a thing depend on how you design your RPC API (stateless or not).

[ Parent | on HN ]

Re:GRPC: A high performance, open source, general RPC framework by ejona86 on Saturday February 28, 2015 @08:14PM (#9125662)

HTTP/2 has the concept of streams. Each stream is independent, but within a stream data and headers are ordered. Each HTTP request would be on a new stream.

gRPC maps calls to streams so calls can proceed at different rates, but you still receive the information on a particular call in order. So conceptually each call is completely separate, but we can use a single HTTP/2 connection for all the calls to a particular destination.

[ Parent | on HN ]