You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This feature could be implemented in http2-client as well but for some context: typical usage of gRPC is for microservices within datacenters, where endpoints are replicated. The current design sticks all gRPC calls on a same http2 connection (hence, on a same TCP connection -- and if this connection crashes then the programmers as to restart a client passing all the parameters again). It would be nice to support some sort of connection-managers for balancing all RPCs over multiple http2 sessions (with some programmable control over how to pick a session, how many sessions to open etc.)
The text was updated successfully, but these errors were encountered:
gRPC has a "channel", which is a virtual connection to the an endpoint. An endpoint may be served by many servers. Channels have "subchannels", which are logical connections to a server. The subchannel maintains the actual TCP connection. If a channel dies, there is standard logic to either choose another subchannel, or to repair the connection.
This feature could be implemented in
http2-client
as well but for some context: typical usage of gRPC is for microservices within datacenters, where endpoints are replicated. The current design sticks all gRPC calls on a same http2 connection (hence, on a same TCP connection -- and if this connection crashes then the programmers as to restart a client passing all the parameters again). It would be nice to support some sort of connection-managers for balancing all RPCs over multiple http2 sessions (with some programmable control over how to pick a session, how many sessions to open etc.)The text was updated successfully, but these errors were encountered: