HTTP and JSON for your gRPC Services
summary
Namely adopts gRPC and actually builds the pieces: a protoCL dockerized plugin that generates language clients, a gRPC gateway sidecar that maps HTTP/JSON to gRPC and emits Swagger, and an integration with Google Cloud Endpoints ESP that produces latency dashboards and a developer portal. Production stack uses Docker, Kubernetes ingress, Terraform, Kafka with protobuf events, and a proto mono-repo; the generated gateways run and successfully proxy HTTP calls into existing gRPC services.
AI-written summary · about
chapters (23)
- 0:00Intro
- 1:45Agenda
- 2:54Should we build services
- 4:06The two sides of an API
- 5:21What is cruft
- 6:56What is gRPC
- 9:30What is an IDL
- 10:40ProtoC
- 13:00server struct
- 16:20server implementation
- 17:53client implementation
- 18:58gRPC CLI
- 19:28Create to do
- 19:55Manage your services
- 23:04Proto repo
- 24:05GRPC options
- 26:25GRPC gateway
- 27:53Leveraging IDLs
- 29:57Latency dashboards
- 30:37Developer portal
- 32:59GraphQL
- 36:20Graph QL
- 37:08Questions
related talks
23mRunning gRPC services for serving legacy RESTful APIs on Kubernetes
46mIntroduction to gRPC
30mgRPC & Kubernetes
50mEnabling Googley microservices with gRPC
24mWhat's New in gRPC
49mBuilding fast microservices with binary protocol - introduction to gRPC
27mRunning gRPC at Scale: Lessons From the Frontlines of Production
31mCloud Native Communication Patterns with gRPC