[microservice] Nacos cluster building and loading file configuration

Here is 【 Microservices 】, Pay attention to me to learn micro services without getting lost
If it helps you , Give the blogger a free praise to show encouragement
You are welcome to comment on the collection ️

Column introduction

【 Microservices 】 At present, it mainly updates micro services , Learn together and progress together .

Introduction to this issue

This issue focuses on Nacos Cluster setup and loading file configuration

List of articles

Catalog

Service cluster

demand

build

test

Load profile order

nacos To configure DataId Introduce

To configure yml In the document DataId

To configure console Medium DataId

test

Multi environment configuration

Service cluster

demand

• Service providers build clusters

• Service caller , Display the information of each service in the cluster in turn

build

1） Modify service provider's controller, Print the server port number

package com.czxy.controller;

import org.springframework.web.bind.annotation.*;

import javax.annotation.Resource;
import javax.servlet.http.HttpServletRequest;


@RestController
public class EchoController {

    @Resource
    private HttpServletRequest request;

    @RequestMapping(value = "/echo/{string}", method = RequestMethod.GET)
    public String echo(@PathVariable String string) {
        int serverPort = request.getServerPort();
        return "Hello Nacos Discovery " + string + ":" + serverPort;
    }
}

 2） To write yml To configure

# Port number 
server:
  port: 8170

spring:
  application:
    name: service-provider          # service name 
  cloud:
    nacos:
      discovery:
        server-addr: 127.0.0.1:8848   #nacos Service address 

# Port number 
server:
  port: 8270

spring:
  application:
    name: service-provider          # service name 
  cloud:
    nacos:
      discovery:
        server-addr: 127.0.0.1:8848   #nacos Service address 

3） To configure idea Start item

-Dspring.profiles.active=8170

test

• start-up 3 A service （2 Service offerings ,1 Service consumption ）

• see nacos Console

Load profile order

• Yes 3.4.5 chapter / The first 4 Step Explain the content in detail

• The order in which the configuration files are loaded （ The first 4 Step by step ）

nacos To configure DataId Introduce

• nacos Provides 3 Ways of planting , To configure dataId Loading order of

A: Shared configuration ：

spring.cloud.nacos.config.shared-dataids

spring.cloud.nacos.config.refreshable-dataids

B: Load multiple configurations ：

spring.cloud.nacos.config.ext-config[n] C: Internal rule splicing ：

spring.cloud.nacos.config.prefix

spring.cloud.nacos.config.file-extension

spring.cloud.nacos.config.group

To configure yml In the document DataId

spring:
  application:
    name: config-service              #  service name 
  cloud:
    nacos:
      config:
        server-addr: 127.0.0.1:8848     # nacos  Service address 
        shared-dataids: test1.yml       # 1.1  Shared configuration 
        refreshable-dataids: test1.yml  # 1.2  Shared configuration , Dynamic refresh 
        ext-config:                     # 2.  Configure multiple 
          - data-id: test2-1.yml
            group: DEFAULT_GROUP
            refresh: true
          - data-id: test2-2.yml
            group: DEFAULT_GROUP
            refresh: true
        prefix: test3                   # 3.1  Prefix , Default  ${spring.application.name}
        file-extension: yaml            # 3.2  suffix 
        group: DEFAULT_GROUP            # 3.3  Group name 

To configure console Medium DataId

• nacos Console configuration

test

• Loaded later dataId Will overwrite the previously loaded dataId What to set up

• Check the log

Located property source: [
BootstrapPropertySource {name='bootstrapProperties-test3-demo.yaml'}, BootstrapPropertySource {name='bootstrapProperties-test3.yaml'}, BootstrapPropertySource {name='bootstrapProperties-test2-2.yml'}, BootstrapPropertySource {name='bootstrapProperties-test2-1.yml'}, BootstrapPropertySource {name='bootstrapProperties-test1.yml'}]

Multi environment configuration

 

• stay Nacos For different environments （ Development 、 test 、 Production etc. ） in , It provides several concepts at different levels of management , Include ：Data ID、Group、Namespace.

Concept	describe
Data ID	Unique identification of data , Can be understood as Spring Cloud The profile name of the application
Group	Used to correct Data ID Do collection management , Equivalent to small classification
Namespace	Used for tenant granularity configuration isolation . Equivalent to a large classification

• Group group To configure

spring.cloud.nacos.config.group=                # Group name

• Namespace namespace To configure

spring.cloud.nacos.config.namespace=            #namespace Of ID