gRPC and What, Why, How?
summary
gRPC is an RPC framework that claims to replace ad hoc REST boilerplate by using a proto file for service and message definitions, generating Python stubs with protoc + gRPC Python plugin, and running a simple server/client pair that immediately exchanges messages (demo prints "hello py ohio" over an insecure port). tooling shown includes the client tester boom RPC, proto linting via proto-tool, CI for stub generation, and warnings about load‑balancing, streaming, and avoiding git submodules in production.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:16About Me
- 0:40Disclaimer
- 1:35How to Make Web Services Work
- 2:15What is RPC?
- 3:15Lessons from History
- 3:30CORBA (1991) implementation of RC CORBA language neutral specification which also defines commonly needed services
- 5:12SOAP (1999)
- 5:34What SOAP brought to the table
- 5:57Why SOAP slowly lost popularity?
- 7:04REST constraints
- 7:58REST requirements
- 12:05How does it work?
- 12:42What is Protocol Buffers
- 14:55Generate client and server code
- 20:49Production Considerations
- 21:04Ramping up teams
- 22:01Managing Protobuf files
- 23:24Load balancing with gRPC
- 24:47Questions?
