gRPC Pros & Cons

gRPC (gRPC Remote Procedure Calls) is an open source remote procedure call (RPC) system initially developed at Google in 2015. It uses HTTP/2 for transport, Protocol Buffers as the message format. In this video I want to explore gRPC, go through examples, pros and cons of gRPC.

Client/ Server communication - SOAP - HTTP (REST) - WebSockets Client Libraries gRPC gRPC Demo - todos gRPC Pros and Cons Pros - Fast two/uni and request - Unform - One library to rule them all - Progress feedback( long synchronous requests) drop pluggable wait...) - cancel request - All benefits of H2 and Protobuff Cons- schema based (not everyone wants schema) - Thick client - limited languages - Proxies still don’t understand it - Still young - Error handling - No native browser support - Timeouts, circuit breaker just like any RPC (pub/sub rules in this case) Can you create your own protocol? - Spotify example with Hermes Source Code https://github.com/hnasr/javascript_p... Timecode Motivation - 4:30 -Client Server Communication 4:30 -THe problem with client libraries 8:40 - Why GRPc gRPC - modes 16:40 - Unary - 17:20 - server streaming 17:40 - client streaming 18:30 - bidirectional 19:10 Coding : 19:40 Pros & Cons 57:00 Build own : 1:12:30 cards 00:30 H/2 7:00 graphQL 8:00 WebSockets 23:00 protobuff Resources https://grpc.io/docs/guides/ Haproxy grpc https://www.haproxy.com/blog/haproxy-... Nginx grpc https://www.google.com/amp/s/www.ngin... https://grpc.io/docs/guides/concepts/
 •  0 comments  •  flag
Share on Twitter
Published on February 29, 2020 18:49
No comments have been added yet.