Nacos Configuration Center

We learned SpringCloud Config earlier, we can load remote configuration by configuring service, so that we can centrally manage configuration files at the remote end.

Actually, we can configure remote configuration file acquisition in bootstrap.yml, and then enter the configuration file loading link, and Nacos also supports this operation, and the way of use is alsoSimilar, for example, we now want to put the configuration file of the borrowing service in Nacos for management, then we need to create a configuration file in Nacos at this time:

Copy all the configuration files of the borrowing service (of course, not all CVs under normal circumstances, only those parts that need to be modified frequently, here are all CVs to save trouble) Copy over, pay attentionThe format of Data ID is the same as before, application name-environment.yml, if only the application name is written, it means that this configuration file will be used no matter what environment it is in, and thenEach configuration file can be grouped, which can be regarded as a kind of classification:

Click publish when finished:

Then import the dependencies in the project:

org.springframework.cloudspring-cloud-starter-bootstrapcom.alibaba.cloudspring-cloud-starter-alibaba-nacos-config

Then we add the bootstrap.yml file to the borrowing service:

spring:application:# Keep the service name and configuration file the samename: borrowserviceprofiles:# The environment is also consistent with the configuration fileactive: devcloud:nacos:config:# Configuration file suffixfile-extension: yml# Configure the center server address, which is the Nacos addressserver-addr: localhost:8848

Now let's start the service and try:

You can see that the configuration file was successfully read and started. In fact, it is basically the same as the previous Config.

Nacos also supports hot update of configuration files. For example, we have added an attribute to the configuration file, and this time may need to be modified in real time and updated in real time at the back end, so how to achieve this??We create a new Controller:

@RestControllerpublic class TestController {@Value("${test.txt}") //We read the string value of test.txt from the configuration file as the return value of the test interfaceString txt;@RequestMapping("/test")public String test(){return txt;}}

Let's modify the configuration file and restart the server:

You can see that it can be read normally:

Now we will modify the value of the configuration file:

Access the interface again and you will find that there is no change:

But the background successfully detected that the value was updated, but the value did not change:

Then how to achieve configuration hot update?We can do something like this:

@[email protected] //Add this annotation to achieve automatic refreshpublic class TestController {@Value("${test.txt}")String txt;@RequestMapping("/test")public String test(){return txt;}}

Restart the server and repeat the above experiment again, it is successful.