Understanding Nacos Architecture and Service Registration in Spring Cloud

The Nacos architecture consists of Provider APP (service provider), Consumer APP (service consumer), Name Server (high‑availability routing via VIP or DNS), Nacos Server (exposes Open API, Config Service, Naming Service), a Raft‑based Consistency Protocol, and the Nacos Console.

Service registration works as follows: a service instance registers itself to the registry on startup and deregisters on shutdown; consumers query the registry to obtain available instances; the registry performs health‑check calls to ensure instances can handle requests.

In Spring Cloud, the

org.springframework.cloud.client.serviceregistry.ServiceRegistry

interface defines the contract for service registration. Nacos provides an implementation called NacoServiceRegistry, which is wired via META-INF/spring.factories in the spring-cloud-commons module. The auto‑configuration class AutoServiceRegistrationAutoConfiguration creates an AutoServiceRegistration bean, whose concrete subclass NacosAutoServiceRegistration extends AbstractAutoServiceRegistration and listens to WebServerInitializedEvent to trigger registration.

The registration flow ultimately calls NacosServiceRegistry.register(), which delegates to the Nacos client SDK’s namingService.registerInstance method. This results in an HTTP request to the server endpoint nacos/v1/ns/instance, handled by InstanceController in the nacos‑naming module.

On the server side, the request parameters are parsed to obtain serviceName and namespaceId. A Service object is created (or retrieved from a ConcurrentHashMap called serviceMap), the instance is added via addInstance, and a heartbeat task is scheduled using beatReactor.addBeatInfo() to periodically send health‑check packets. The consistencyService.listen method ensures data synchronization across the cluster using the Raft protocol.

Dynamic service discovery is achieved through the subscribe method. The client’s HostReactor runs an UpdateTask thread that pulls the latest address list every 10 seconds. If a provider fails, the server pushes a notification, and the client processes it via processServiceJSON to update its local cache.

In summary, Nacos handles service registration by (1) constructing and storing a Service object in a concurrent map, (2) scheduling heartbeat checks for all instances, and (3) synchronizing data across nodes using a Raft‑based consistency protocol.