Adapting Our XDS Control Plane for Proxyless gRPC
summary
Adapting an Envoy xDS control plane to proxyless gRPC requires changes to the transport and resource model not a simple toggle, including adding state-of-the-world support to a Delta-only go-control-plane, rewriting listener and security configs, and handling metadata differences. The team implements batching that yields ~20s propagation in practice, ships path/header traffic shifting and central load‑balancer choice across Java/Go/Python, but some Envoy features stay missing and state-of-the-world vs Delta mismatches cost engineering time.
AI-written summary · about
chapters (11)
- 0:00Introduction to Datadog
- 0:40Service discovery basics
- 1:32Overcoming legacy DNS issues
- 3:26Comparing DNS and XDS performance
- 5:40Advantages of the XDS model
- 7:41Sidecar proxy evaluation
- 11:02Adapting the control plane
- 14:13Configuration resource changes
- 15:34Proxyless gRPC results
- 18:28Concluding takeaways
- 19:35Q&A session
related talks
23mA Simplified Service Mesh With gRPC
16mxDS in gRPC for Service Mesh
20mProxyless Service Mesh with gRPC
23mHow Proxyless gRPC Works in a Service Mesh
33mgRPC For Microservices: Service-mesh and Observability
17mBuilding a gRPC Proxyless World: How Reddit Scaled Resilience...
23mxDS Support in gRPC
29mgRPC load balancing and Service Mesh