Envoy as a service-to-service proxy

Mux has adopted the use of the Envoy networking proxy within their Kubernetes clusters for handling gRPC interservice traffic. They chose this approach over client-based and full service-mesh solutions due to its language agnosticism, compatibility with older Kubernetes versions, and rich feature set. The Envoy sidecar container was chosen as it automatically scales network proxying capacity alongside service scaling and provides a straightforward configuration setup. Since implementing this solution, Mux no longer experiences issues with gRPC load balancing and has found additional valuable use cases for the Envoy proxy injection outside of their gRPC services.