dido:public:ra:xapend:xapend.b_stds:defact:google:grpc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:google:grpc [2021/08/13 11:20] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:google:grpc [2021/11/09 15:41] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== Google: gRPC ===== | ===== Google: gRPC ===== | ||
| - | [[dido:public:ra:xapend:xapend.b_stds:defact:google| return to Google page ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:google:start| return to Google page ]] |
| <table> | <table> | ||
| Line 52: | Line 52: | ||
| // The protocol itself is based on http2, and exploits many of its benefits. Google’s development of SPDY laid down the first designs for what eventually became http2.// | // The protocol itself is based on http2, and exploits many of its benefits. Google’s development of SPDY laid down the first designs for what eventually became http2.// | ||
| - | // gRPC supports several built in features inherited from http2, such as compressing headers, persistent single TCP connections, cancellation and timeout contracts between [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] and server.// | + | // gRPC supports several built in features inherited from http2, such as compressing headers, persistent single TCP connections, cancellation and timeout contracts between [[dido:public:ra:xapend:xapend.a_glossary:c:client|client]] and [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]].// |
| - | // The protocol has built in flow control from http2 on data frames. This is very handy for insuring clients respect the throughput of your system, but does add an extra level of complexity when diagnosing issues in your infrastructure, because either client or server can set their own flow control values.// | + | // The protocol has built in flow control from http2 on data frames. This is very handy for insuring clients respect the [[dido:public:ra:xapend:xapend.a_glossary:t:thruput|throughput]] of your system, but does add an extra level of complexity when diagnosing issues in your infrastructure, because either client or server can set their own flow control values.// |
| // Load balancing (LB) is normally performed by the client, which chooses the server for a given request from a list provided by a Load Balancing server. The LB server will monitor the health of endpoints and use this and other factors to manage the list provided to clients. Clients will use a simple algorithm such as round-robin internally, but note that the LB server may apply more complex logic when compiling the list for a given client.// | // Load balancing (LB) is normally performed by the client, which chooses the server for a given request from a list provided by a Load Balancing server. The LB server will monitor the health of endpoints and use this and other factors to manage the list provided to clients. Clients will use a simple algorithm such as round-robin internally, but note that the LB server may apply more complex logic when compiling the list for a given client.// | ||
dido/public/ra/xapend/xapend.b_stds/defact/google/grpc.1628868003.txt.gz · Last modified: 2021/08/13 11:20 by murphy
