JustFootball’s Journey to gRPC + Linkerd in Production
summary
JustFootball migrates a GraphQL-backed monolith that made ~80 internal calls per query to gRPC over HTTP/2 to cut connection and CPU overhead, publishing per-service protobufs via language package managers. Linkerd is added to solve gRPC’s connection-level load‑balancing problem by providing gRPC multiplexes over one HTTP/2 connection while doing Linkerd request-level load balancing, TLS between proxies, per-endpoint observability and service profiles for client timeouts/retries. A demo shows gRPC traffic stuck on one pod until Linkerd is injected into the gateway, after which traffic evens out.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 2:35Monolith to microservices
- 4:07Transitioning to gRPC
- 5:40Managing gRPC schemas
- 8:05Linkerd overview
- 10:01Linkerd for gRPC
- 13:22Linkerd demo
- 21:00Q&A
