The service registry now takes into account the service transport when creating grpc clients. This allows using dns and unix as the protocol in addition to tcp. dns will turn the gRPC client into a Thick Client that can look up multiple endpoints via DNS. Furthermore, we enabled round robin load balancing for the default transparent retry configuration of gRPC.
The service registry now takes into account the service transport when creating grpc clients. This allows using
dnsandunixas the protocol in addition totcp.dnswill turn the gRPC client into a Thick Client that can look up multiple endpoints via DNS. Furthermore, we enabled round robin load balancing for the default transparent retry configuration of gRPC.related: