Nacos Namespace grouping and DataID The relationship between the three

A term is used to explain

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. .

Configure grouping （Group）

​ Nacos A set of configuration sets in , It is one of the dimensions of organization configuration . Through a meaningful string （ Such as Buy or Trade ） Group configuration sets , To distinguish Data ID Same configuration set . When you are in Nacos When you create a configuration on , If the name of the configuration group is not filled in , Then the name of the configuration group is used by default DEFAULT_GROUP . Common scenarios for configuring grouping ： Different applications or components use the same configuration type , Such as database_url Configuration and MQ_topic To configure .

config set ID（Data ID）

​ Nacos Of a configuration set in ID. config set ID It is one of the dimensions of organization division and configuration .Data ID Usually used to organize the configuration set of partition system . A system or application can contain multiple configuration sets , Each configuration set can be identified by a meaningful name .Data ID Class is usually used Java package （ Such as com.taobao.tc.refund.log.level） The naming rules guarantee global uniqueness . This naming rule is not mandatory .

​ config set ： A set of related or unrelated configuration items is called a configuration set . In the system , A configuration file is usually a configuration set , Including all aspects of the system configuration . for example , A configuration set may contain data sources 、 Thread pool 、 Log level and other configuration items .

The relationship between the three

​ The relationship between the three is similar to Java Inside package And class name , The outermost Namespace Can be used to differentiate deployment environments ,Group and DataID Logically distinguish between two target objects .

By default

Namespace=public,Group=DEFAULT_GROUP, Default Cluster yes DEFAULT

Details

​ Nacos The default namespace is public, We can use it Namespace To achieve isolation , For example, we now have three environments ： Development 、 test 、 Production environment , We can create three Namespace, Different N amespace It's isolated .

​ Group In itself, it means grouping , It can divide different micro services into the same group .

​ The rest is specific micro Services , One Service It can contain more than one Cluster,Nacos Default Cluster yes DEFAULT,Cluster Is a virtual partition of a specified microservice . for instance , Will a Service Deployed in computer rooms in Beijing and Hangzhou , Beijing computer room Service You can call it （BJ）, In Hangzhou computer room Service You can call it （HZ）, In this way, microservices in the same computer room can call each other as much as possible , Lifting performance .

Switch between different environments

DataID programme

1. Appoint spring.profile.active And configuration files DataID To read different configurations in different environments , Configuration rules ： Default space + newly build dev and test Two DataId：

   1. newly build dev To configure DataID（ Created ）
   2. newly build test To configure DataID

2. adopt spring.profile.active Attribute can be used to read configuration files in multiple environments

   

   

   spring:
     profiles:
       # active: dev # Represents the development environment 
       active: test # Represents the test environment 
   

3. test

   Finally, visit again ：http://localhost:3377/localhost/config/info

   

Group programme

​ According to the previous explanation, we all know Group For grouping, the default is ：DEFAULT_GROUP, So now we need to divide into two groups , One group is “Dev Development Group ”, One group is “test Test group ”

1. newly build Group

   DEV_GROUP

​ TEST_GROUP

Configuration list , Two DataID Agreement , But grouping different profiles ：

2. After completing the above configuration , Then you need to pass bootstrap+application To complete , Specific way ： stay config Add one more Group Can be configured , Can be configured as DEV_GROUP or TEST_GROUP

​ bootstrap:

# nacos To configure 
server:
  port: 3377

spring:
  application:
    name: nacos-config-client
  cloud:
    nacos:
      discovery:
        server-addr: localhost:8848 #Nacos Address of service registration center 
      config:
        server-addr: localhost:8848 #Nacos As the configuration center address 
        file-extension: yaml # Appoint yaml Format configuration 
        group: TEST_GROUP # Add groups 

​ application:

spring:
  profiles:
    # active: dev # Represents the development environment 
    # active: test # Represents the test environment 
    active: info

3. test （ Different groups can be tested ）：

   Finally, visit again ：http://localhost:3377/localhost/config/info

Namespace Space programme

​ We have DataID Scheme and Group The plan is complete , Then let's take a look at Namespace（ Namespace ） programme , The default scheme is public, This scheme cannot be deleted , Now let's create two new namespace schemes

1. newly build dev/test Of Namespace

1. Service management - View the service list page

   At this point, we can switch the corresponding namespace , And then through Group and DataID To switch , If you want to switch namespaces , We need to pass the namespace ID To switch

2. Configure according to the domain name （Namespace+Group+DataId） To write

   ​ Through the first namespace Namespace ID To confirm the namespace used

# nacos To configure 
server:
  port: 3377

spring:
  application:
    name: nacos-config-client
  cloud:
    nacos:
      discovery:
        server-addr: localhost:8848 #Nacos Address of service registration center 
      config:
        server-addr: localhost:8848 #Nacos As the configuration center address 
        file-extension: yaml # Appoint yaml Format configuration 
        group: TEST_GROUP #  Assign groups 
        namespace: 4ba4bf0e-210c-41ce-954c-23538de1dcbc # Specify the namespace 

spring:
  profiles:
    active: dev # Represents the development environment 
    # active: test # Represents the test environment 
    # active: info

​

And then back to Nacos Configuration list , add to Dev Configuration under namespace , add to 3 strip

3. test ： visit http://localhost:3377/localhost/config/info To test it