Instead of clients directly connecting to load balancer, in this architectural pattern the client connects to the service registry and tries to fetch data or services from it. Once it gets all data, it does load balancing on its own and directly reaches out to the services it needs to talk to. This can have a benefit where there are multiple proxy layers and delays are happening due to the multilayer communication. In server-side discovery, the proxy layer or API Gateway later tries to connect to the service registry and makes a call to appropriate service afterward. Over here client connects to that proxy layer or API Gateway layer.