Shulou(Shulou.com)06/03 Report--

This article shows you how Springcloud-nacos implements the configuration and registry. The content is concise and easy to understand. It will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

Recently, Ali's open source nacos is quite popular and can be shared with springcloud and dubbo, which is very convenient for dubbo to upgrade to springcloud. Here to learn his configuration and registration center. I mainly record how it is used and how it is stepped on.

Brief introduction of nacos

Nacos is dedicated to helping you discover, configure, and manage micro services. Nacos provides an easy-to-use set of features to help you quickly implement dynamic service discovery, service configuration, service metadata, and traffic management.

Nacos helps you build, deliver, and manage micro-service platforms more quickly and easily. Nacos is a service infrastructure for building modern application architectures with "service" as the center, such as micro-service paradigm and cloud native paradigm.

The above is extracted from the official website of nacos, summing up that nacos has the following advantages: (1) it supports configuration center management (including graphical interface); (2) deployment delivery is simple; (3) it includes a registry, and there is no need to build a configuration and registry alone. (4) perfect integration of spring cloud and dubbo has good expansibility.

How to use nacos. For more information, please see official configuration.

(1) download source code from Github

Git clone https://github.com/alibaba/na... Cd nacos/ mvn-Prelease-nacos clean install-U ls-al distribution/target/ cd distribution/target/nacos-server-$version/nacos/bin

(2) decompress and start nacos

Unzip nacos-server-$version.zip or tar-xvf nacos-server-$version.tar.gz cd nacos/bin sh startup.sh-m standalone

Complete, the cluster is highly available, please study it yourself, this article will not repeat too much.

Nacos implementation configuration Center

It is easy for springcloud to use nacos as the configuration center. Just add dependencies and configure the registry address using bootstrap.

(1) add the configuration center dependency of nacos

Org.springframework.cloud spring-cloud-starter-alibaba-nacos-config

(2) configure bootstrap.properties file

# name of configuration service spring.application.name=provider-service # address of nacos configuration center spring.cloud.nacos.config.server-addr=nacos.ailijie.top # Encoding method of nacos configuration spring.cloud.nacos.config.encode=utf-8 # configuration group name, which needs to be set in nacos, otherwise the spring.cloud.nacos.config.group=PROVIDER_GROUP # configuration suffix will not be found Properties does not require spring.cloud.nacos.config.file-extension=yml # to load multiple nacos configuration files spring.cloud.nacos.config.shared-dataids=provider-service.properties,test.properties # refresh loaded other environment spring.cloud.nacos.config.refreshable-dataids=provider-service.properties,test.properties

(3) A brief introduction. With nacos configuration Center, the client will be configured with a regular heartbeat, and the environment variables will be dynamically refreshed. But in bean, you need to use @ RefreshCode annotation to refresh, otherwise it will not take effect. The database configuration can customize the data source. To load other configuration files, you need to use refres-dataids to refresh the environment.

Nacos implementation registry

Similarly, nacos to implement the registry is also quite simple, after the successful configuration of nacos, we only need to add dependencies, annotations, and configure the registry address. (1) add dependencies

Org.springframework.cloud spring-cloud-starter-alibaba-nacos-discovery

(2) add @ EnableDiscoveryClient annotation to the startup class

(3) configure the registry address

# configure service name spring.application.name=xxx-service # configure service cluster name spring.cloud.nacos.discovery.cluster-name=consumer-service # configure registry address spring.cloud.nacos.discovery.server-addr=nacos.ailijie.top

It's done. It's that simple.

Experience of nacos Mining Pit

Here are some of the problems I have encountered:

(1) using version management to learn new projects, we first need to understand the version compatibility features, otherwise there will be a lot of problems. (2) the configuration does not take effect, and the @ RefreshCode annotation is not used to refresh the configuration. (3) the distinction between registry and configuration center is two concepts, and two addresses need to be configured.

The above is how Springcloud-nacos implements the configuration and registry. Have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.