Nacos Development Manual

1.Nacos brief introduction

Nacos Provides an easy-to-use feature set , Realize dynamic service discovery 、 Service configuration 、 Service metadata and traffic management . To replace the previously used registry （zookeeper , eureka wait ）, And the configuration center （spring cloud config wait ）.

• Reference documents ：https://nacos.io/zh-cn/docs/what-is-nacos.html

2.Nacos Key features

Service discovery and service health monitoring

Service registration ：

Spring Cloud Nacos Discovery follow Spring Cloud General standards , And implemented three interfaces ：AutoServiceRegistration,ServiceRegistry and Registration. stay Spring Cloud The startup phase of the application , Will monitor WebServerInitializedEvent event . Initializing Web Received after container WebServerInitializedEvent When an event is , The registration operation will be triggered , And call ServiceRegistry register Method to register the service to Nacos Server.

Service discovery ：

NacosServerList Realization com.netflix.loadbalancer.ServerList Interface , And automatically inject it into @ConditionOnMissingBean Next . The ribbon defaults to integration . More customizable if needed , You can use @Autowired Inject NacosRegistration Bean, And directly through its own NamingService The contents of the field call Nacos API.
Dynamic configuration services
Services and metadata management

• Reference documents ：https://nacos.io/zh-cn/docs/use-nacos-with-springcloud.html（Nacos SpringCloud）

3.Nacos Cluster deployment description

stay nacos Unzip directory nacos/ Of conf Under the table of contents , There are configuration files cluster.conf, Please configure each line to ip:port.

Reference documents ：https://nacos.io/zh-cn/docs/cluster-mode-quick-start.html

4.Nacos To configure

• Reference documents ： Add link description
  https://github.com/alibaba/spring-cloud-alibaba/issues/141

4.1 Custom namespace

Namespace ： Used for tenant granularity configuration isolation . Under different namespaces , There can be the same Group or Data ID Configuration of .Namespace One of the most common scenarios is the separation of configurations between different environments , For example, develop the resources of test environment and production environment （ Such as configuration 、 service ） Isolation etc. .

4.2 Customize Group To configure

4.3 Custom extended data id To configure

4.4 Configure the refresh

Configure refresh usage @RefreshScope annotation . Code example ：

The results ：

After updating the configuration , Call again and return the result ：

5. Service startup

Start the loaded configuration file

among ：blade.ymal Configure the server in the configuration file 、spring To configure 、feign To configure 、hystrix To configure 、ribbon Configuration and other public configuration
blade-dev.yaml This is done in the configuration file redis、 Database connection and other configurations （ You can also add ）