From Writing REST to Writing gRPC
summary
Defines a proto file first and generates Go types and client/server stubs—example is a user service with GetUser RPC that produces two generated files (messages and service) and requires embedding UnimplementedUserServiceServer to satisfy the interface. gRPC adds server streaming and client/server streaming patterns, protobuf field numbers become part of the binary wire format, and the buff ecosystem (including buff linting and protov-validate) enforces compatibility and rules—a negative ID example fails validation so the setup catches schema drift early.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 0:43REST vs gRPC comparison
- 1:46Why gRPC became popular
- 2:48Writing first gRPC contract
- 3:52Generating code from protobuf
- 4:56Implementing gRPC service
- 6:00Development experience differences
- 7:25Protocol buffers as shared contract
- 8:26Unary and streaming RPCs
- 9:29Generated code and tooling
- 11:37gRPC and other technologies
- 12:42Choosing between REST and gRPC
- 13:06Conclusion and takeaways
