How do you implement service discovery and load balancing across NestJS microservice instances?

Q: How do you implement service discovery and load balancing across NestJS microservice instances?

// Option 1 — Kubernetes Service DNS (zero-configuration) // K8s creates a stable DNS name; kube-proxy load-balances to pods ClientsModule.register([{ name: 'ORDERS_SERVICE', transport: Transport.TCP, options: { host: 'orders-service', port: 3001 }, // 'orders-service' resolves via K8s DNS and round-robins across pods }]) // Option 2 — Consul service registration @Module({ imports: [ConsulModule.register({ host: 'consul', port: 8500 })], }) export class AppModule implements OnModuleInit { constructor(private consul: ConsulService) {} async onModuleInit() { await this.consul.register({ name: 'orders-service', address: process.env.POD_IP, port: 3001, check: { http: `http://${process.env.POD_IP}:3001/health`, interval: '10s', }, }); } } // Dynamic client — resolves healthy instances from Consul async getOrdersClient(): Promise { const instances = await this.consul.health.service({ service: 'orders-service', passing: true, // only healthy instances }); const instance = instances[Math.floor(Math.random() * instances.length)]; return ClientProxyFactory.create({ transport: Transport.TCP, options: { host: instance.Service.Address, port: instance.Service.Port }, }); } Kubernetes Service DNS — prefer for K8s deployments; zero configuration; kube-proxy handles load balancing. Consul — use for non-K8s environments or when you need health-aware routing and canary deployments. Register every instance on startup and deregister on graceful shutdown to keep the registry accurate. ClientProxyFactory.create() allows dynamic client creation when the host is not known at module load time. For gRPC in K8s, configure headless services and client-side load balancing — kube-proxy does not balance gRPC streams.

Difficulty: 6/10

service discovery, load balancing, NestJS microservices

In Kubernetes use Service DNS — K8s creates a stable hostname that load-balances across pods automatically. In non-K8s environments use Consul for health-aware service registration and discovery. Use ConsulService to register the instance on startup and resolve healthy instances dynamically before each ClientProxy creation.

Kubernetes DNS and Consul service discovery

Service discovery strategy selection:

1
Kubernetes Service DNS — prefer for K8s deployments; zero configuration; kube-proxy handles load balancing.

How do you implement service discovery and load balancing across NestJS microservice instances?

Difficulty: 6/10

service discovery, load balancing, NestJS microservices

In Kubernetes use Service DNS — K8s creates a stable hostname that load-balances across pods automatically. In non-K8s environments use Consul for health-aware service registration and discovery. Use ConsulService to register the instance on startup and resolve healthy instances dynamically before each ClientProxy creation.

Kubernetes DNS and Consul service discovery

Service discovery strategy selection:

1
Kubernetes Service DNS — prefer for K8s deployments; zero configuration; kube-proxy handles load balancing.

How do you implement service discovery and load balancing across NestJS microservice instances?

How do you implement service discovery and load balancing across NestJS microservice instances?

Scenario Questions

Follow-up Questions