Understanding Nacos Architecture and Service Registration in Spring Cloud

The Nacos architecture consists of several key components: Provider APP (service provider), Consumer APP (service consumer), Name Server (high‑availability routing via VIP or DNS), Nacos Server (provides configuration and naming services, consistency protocol based on Raft), and Nacos Console (management UI).

In a service registry, service instances register on startup and deregister on shutdown, while consumers query the registry for available instances; health checks are performed via a dedicated API.

Spring Cloud integrates Nacos through the standard org.springframework.cloud.client.serviceregistry.ServiceRegistry interface. The implementation class NacoServiceRegistry is auto‑wired via AutoServiceRegistrationAutoConfiguration defined in META-INF/spring.factories . This configuration creates an AutoServiceRegistration bean, whose concrete class NacosAutoServiceRegistration extends AbstractAutoServiceRegistration .

During the WebServerInitializedEvent , AbstractAutoServiceRegistration invokes this.bind(event) , which eventually calls NacosServiceRegistry.register() . The registration method uses the Nacos client SDK’s namingService.registerInstance to submit the instance information.

The heartbeat mechanism is built on beatReactor.addBeatInfo() to generate periodic health‑check packets, while the server validates the instance’s health via serverProxy.registerService() . If a heartbeat is missed, the instance is marked unhealthy and a service‑change event is emitted.

Nacos supports both Open API and SDK registration. Both ultimately send an HTTP request to nacos/v1/ns/instance , handled by the InstanceController in the nacos-naming module. The controller extracts serviceName and namespaceId , creates or retrieves a Service object stored in a ConcurrentHashMap , adds the instance, establishes heartbeat tasks, and registers the service for data‑consistency synchronization.

Service address queries are performed via the same controller’s list method, which parses request parameters, retrieves the corresponding Service , extracts provider IPs, and assembles a JSON response.

Dynamic service discovery is achieved through the HostReactor class. After a client subscribes, an UpdateTask thread polls the server every 10 seconds for the latest address list. The server pushes updates when a provider fails its heartbeat, and the client processes the JSON payload to refresh its local cache.

Overall, Nacos provides a robust, Raft‑based, cloud‑native service registry that integrates seamlessly with Spring Cloud, offering automatic registration, health monitoring, and real‑time service address updates.