Presentation at NetPonto community: "We’re going to discuss gRPC, Google’s open-source RPC framework. I’ll dive a bit into the history of RPC as a protocol, and what its historical use has been. I’ll also highlight some benefits to adopt gRPC and how its possible to swap out parts of gRPC and still take advantage of gRPC’s benefits. Finally I’ll answer the question that has been on many lips since gRPC was announced — what does this mean for REST?"
6. [API Paradigms] - RPC vs REST
◦ RPC
▫ exposes operations as a method for acting upon data
◦ REST
▫ exposes data as resources to be acted upon
It’s a matter of context/use case!
22. gRPC on the wire
◦ HTTP/2
◦ Protocol Buffers serialization by default
◦ Clients open one long-lived connection to the server
▫ A new HTTP/2 stream for each call
▫ Allows simultaneous in-flight calls
◦ Allows bidirectional streaming
▫ Server-side streaming
▫ Client-side streaming
59. The not so good parts
◦ Load Balancing
◦ Limited error handling
◦ Support for browser js still beta
◦ Breaking API changes
◦ Poor documentation for some languages
◦ No standardization across languages