I am not even sure if the problem described in the article is specific to gRPC. I think it's a HTTP/2 problem. Any sane HTTP/2 client making N queries to the s

I am not even sure if the problem described in the article is specific to gRPC. I think it's a HTTP/2 problem. Any sane HTTP/2 client making N queries to the same host/IP ideally should use 1 connection since h2 supports multiplexing (which is bad for load balancing if you have an L4 LB). So even if you don't use gRPC, consider putting a per-call (L7) LB in front of your app if you use HTTP/2 protocol between your apps.