When Should You Choose Nacos Over Kubernetes Service Discovery?

Kubernetes has become popular and many services run on it, often using Alibaba's Nacos for service registration, which feels great.

However, a question arises: if Kubernetes already provides a service registry, why still use Nacos?

Forward‑looking factors include whether the operations team is strong enough to handle Istio, whether the architecture team can adopt Dapr, whether developers can set up local tools for the Kubernetes environment (traffic forwarding, minikube, etc.), and the granularity of management control (Nacos benefits small teams, production config changes, process convenience; Kubernetes ConfigMap leans toward Git‑stored configurations with strong ops‑driven release processes).

Conversely, reverse considerations ask which registry is optimal and practical, what equipment needs to be purchased, what kind of team should be recruited (job descriptions, levels, etc.), and again the management control granularity.

Source: https://www.cnblogs.com/aarond/p/service-discovery-thinking.html