call framework – Action-centric vs resource-centric ▪ Cross-platform, supported everywhere in many languages ▪ Automatically generate client SDKs from IDL
and serialization – Compact, efficient binary format – Fast serialization and deserialization – Downside: less human-readable ▪ Built on HTTP/2 – Binary framing and compression: more efficient protocol than HTTP 1.x – Multiplexing: stream multiple calls over a single TCP connection – Flow control: prevent senders from overwhelming receivers