How would you handle service discovery in a Node.js microservices architecture, so services can find each other's network locations dynamically?

In a dynamic environment (containers being created and destroyed, auto-scaling adjusting instance counts), hardcoding a downstream service's IP address doesn't work -- service discovery mechanisms include DNS-based discovery (Kubernetes' built-in DNS resolves a service name to the current set of healthy instance IPs automatically), a dedicated service registry (like Consul, where services register themselves on startup and deregister on shutdown), or a service mesh (like Istio, which handles discovery and routing transparently at the network layer).

// Kubernetes DNS-based service discovery: no IP addresses hardcoded anywhere
const response = await fetch('http://inventory-service.default.svc.cluster.local/products/123');
// Kubernetes automatically resolves 'inventory-service' to a currently healthy pod IP