Quick Start for Nacos Spring Projects

This quick start introduces how to enable Nacos configuration management and service discovery features for your Spring project.

The quick start includes two samples:

  • How to enable Nacos server and Nacos Spring configuration modules to implement dynamic configuration management;
  • How to enable Nacos server and Nacos Spring service discovery modules to implement service registration and discovery.

Prerequisite

Follow instructions in Nacos Quick Start to download Nacos and start the Nacos server.

Enable Configuration Service

Once you start the Nacos server, you can follow the steps below to enable the Nacos configuration management service for your Spring project.

Sample project: nacos-spring-config-example

  • Add the Nacos Spring dependency.
  1. <dependency>
  2. <groupId>com.alibaba.nacos</groupId>
  3. <artifactId>nacos-spring-context</artifactId>
  4. <version>${latest.version}</version>
  5. </dependency>

The the latest version can be available in maven repositories such as "mvnrepository.com".

  • Add the @EnableNacosConfig annotation to enable the configuration service. In the code below, @NacosPropertySource is used to load the configuration source whose dataId is example , and autorefresh is also enabled:
  1. @Configuration
  2. @EnableNacosConfig(globalProperties = @NacosProperties(serverAddr = "127.0.0.1:8848"))
  3. @NacosPropertySource(dataId = "example", autoRefreshed = true)
  4. public class NacosConfiguration {
  5. }
  • Specify the property value for the @NacosValue annotation of Nacos.
  1. @Controller
  2. @RequestMapping("config")
  3. public class ConfigController {
  4. @NacosValue(value = "${useLocalCache:false}", autoRefreshed = true)
  5. private boolean useLocalCache;
  6. @RequestMapping(value = "/get", method = GET)
  7. @ResponseBody
  8. public boolean get() {
  9. return useLocalCache;
  10. }
  11. }
  • Start Tomcat and call curl http://localhost:8080/config/get to get configuration information. Because no configuration has been published, a falsemessage is returned.

  • Now you can call Nacos Open API to publish a configruation to the Nacos server. Assume the dataId is example, and content is useLocalCache=true.

  1. curl -X POST "http://127.0.0.1:8848/nacos/v1/cs/configs?dataId=example&group=DEFAULT_GROUP&content=useLocalCache=true"
  • Access http://localhost:8080/config/getagain, and you get a return message of true, indicating that the value of useLocalCachein your application has been updated.

Enable Service Discovery

Now you would like to enable the service discovery function of Nacos in your Spring project.

Sampe project: nacos-spring-discovery-example

  • Add the Nacos Spring dependency.
  1. <dependency>
  2. <groupId>com.alibaba.nacos</groupId>
  3. <artifactId>nacos-spring-context</artifactId>
  4. <version>${latest.version}</version>
  5. </dependency>

The the latest version can be available in maven repositories such as "mvnrepository.com".

  • Add the @EnableNacosDiscovery annotation to enable the service discovery function of Nacos:
  1. @Configuration
  2. @EnableNacosDiscovery(globalProperties = @NacosProperties(serverAddr = "127.0.0.1:8848"))
  3. public class NacosConfiguration {
  4. }
  • Use @NacosInjected to inject a Nacos NamingService instance:
  1. @Controller
  2. @RequestMapping("discovery")
  3. public class DiscoveryController {
  4. @NacosInjected
  5. private NamingService namingService;
  6. @RequestMapping(value = "/get", method = GET)
  7. @ResponseBody
  8. public List<Instance> get(@RequestParam String serviceName) throws NacosException {
  9. return namingService.getAllInstances(serviceName);
  10. }
  11. }
  1. curl -X PUT 'http://127.0.0.1:8848/nacos/v1/ns/instance?serviceName=example&ip=127.0.0.1&port=8080'
  1. [
  2. {
  3. "instanceId": "127.0.0.1#8080#DEFAULT#example",
  4. "ip": "127.0.0.1",
  5. "port": 8080,
  6. "weight": 1.0,
  7. "healthy": true,
  8. "cluster": {
  9. "serviceName": null,
  10. "name": "",
  11. "healthChecker": {
  12. "type": "TCP"
  13. },
  14. "defaultPort": 80,
  15. "defaultCheckPort": 80,
  16. "useIPPort4Check": true,
  17. "metadata": {}
  18. },
  19. "service": null,
  20. "metadata": {}
  21. }
  22. ]