Cloud Native Communication Patterns with gRPC
summary
gRPC is presented as a compact, HTTP/2 + Protocol Buffers stack for internal microservice calls, claiming lower overhead than REST and native unary, server/client, bidirectional streaming support. Practical tooling includes Protocol Buffers, generated server/client stubs (examples in Go and Java), interceptors for auth/OAuth2 and policy, deadlines/cancellation, multiplexing multiple services on one server, and API versioning via proto packages. The talk shows a working grpc-gateway REST bridge and an architecture mixing gRPC for sync calls and Kafka for async events.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:10What is gRPC?
- 4:48Fundamentals of gRPC - service definition
- 5:45Fundamentals of gRPC - gRPC service
- 7:11Fundamentals of gRPC - gRPC client
- 7:40Why gRPC?
- 10:00gRPC vs. OpenAPI/REST vs. GraphQL
- 11:51gRPC in the microservices landscape
- 14:18Unary/simple RPC
- 15:33Server streaming RPC
- 17:04Client streaming RPC
- 18:04Bidirectional-streaming RPC
- 19:59gRPC interceptors
- 21:18Deadlines
- 22:02Metadata
- 22:54Multiplexing
- 23:31Cancellation
- 24:27API specification with gRPC
- 25:45API versioning with gRPC
- 27:18Extending service definition
- 27:59Securing gRPC services with OAuth2
- 28:38REST/Open API - gRPC Bridge
- 29:47Resources
