菜鸟的Spring Cloud Alibaba学习总结（一）：Nacos

科技2022-08-05 108

菜鸟的Spring Cloud Alibaba学习总结（一）：Nacos

说明一、父工程创建二、Nacos（1）服务注册（2）服务配置三、Nacos集群（1）数据库创建（2）nacos集群搭建（3）nginx配置（4）集群测试四、微服务入住nacos集群

说明

更新时间：2020/10/06 17:02，更新了nacos

本文主要对Spring Cloud Alibaba中的Nacos进行学习与记录，偏向于实战，本文会持续更新，不断地扩充

注意：本文仅为记录学习轨迹，如有侵权,联系删除

一、父工程创建

spring cloud alibaba坐标依赖：https://spring.io/projects/spring-cloud-alibaba 这里还是采用聚合工程的方式进行创建，创建Maven父工程spring_cloud_alibaba，删除src目录，修改pom坐标文件

<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.zsc</groupId> <artifactId>spring_cloud_alibaba</artifactId> <version>1.0-SNAPSHOT</version> <packaging>pom</packaging>  <properties> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> <maven.compiler.source>11</maven.compiler.source> <maven.compiler.target>11</maven.compiler.target> <junit.version>4.12</junit.version> <lombok.version>1.18.10</lombok.version> <log4j.version>1.2.17</log4j.version> <mysql.version>8.0.18</mysql.version> <druid.version>1.1.21</druid.version> <mybatis.spring.boot.version>2.1.1</mybatis.spring.boot.version> </properties>  <dependencyManagement> <dependencies>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-dependencies</artifactId> <version>2.2.2.RELEASE</version> <type>pom</type> <scope>import</scope> </dependency>  <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-dependencies</artifactId> <version>Hoxton.SR1</version> <type>pom</type> <scope>import</scope> </dependency>  <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-alibaba-dependencies</artifactId> <version>2.1.0.RELEASE</version> <type>pom</type> <scope>import</scope> </dependency>  <dependency> <groupId>mysql</groupId> <artifactId>mysql-connector-java</artifactId> <version>${mysql.version}</version> <scope>runtime</scope> </dependency>  <dependency> <groupId>com.alibaba</groupId> <artifactId>druid</artifactId> <version>${druid.version}</version> </dependency>  <dependency> <groupId>org.mybatis.spring.boot</groupId> <artifactId>mybatis-spring-boot-starter</artifactId> <version>${mybatis.spring.boot.version}</version> </dependency>  <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>${junit.version}</version> </dependency>  <dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>${log4j.version}</version> </dependency>  <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <version>${lombok.version}</version> <optional>true</optional> </dependency> </dependencies> </dependencyManagement> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <configuration> <fork>true</fork> <addResources>true</addResources> </configuration> </plugin> </plugins> </build> </project>

聚合工程的pom，里面注意加packaging标签，里面的内容是pom，上面的pom文件中，重点引入了spring cloud alibaba坐标依赖，这个依赖里面包含了很多alibaba的组件的版本控制 spring cloud alibaba坐标依赖：https://spring.io/projects/spring-cloud-alibaba

spring-cloud-alibaba-dependencies点进去之后还集成了很多Alibaba的组件像是上面图片上的Nacos等，这些里面都有集成，并且有相应的版本控制。

二、Nacos

Nacos官网：https://nacos.io/zh-cn/docs/what-is-nacos.html 关于Nacos的具体信息可以去它的官网看一下，上面还有详细的教程。

还是之前的技术选型的图片，从图中可以看出，Nacos = 服务注册中心 + 服务配置 + 服务总线

（1）服务注册

服务注册是Nacos的基本功能，Nacos跟Eureka的功能一样，但是Nacos使用起来更简单，也不用自己创建模块用来创建服务端，Nacos需要自己下载，之后就可以直接使用，我们开发的一个个服务模块都将作为客户端入住到Nacos里面。

关于Nacos的下载这里用的用docker进行安装，具体可以看本人的菜鸟学习Docker实例这篇博客。

服务提供模块创建这里为了演示出Nacos的负载均衡能力，需要创建两个或以上个支付服务，这里创建两个（cloud-alibaba-provider-payment9001和cloud-alibaba-provider-payment9002），下面以一个支付服务（cloud-alibaba-provider-payment9001）为例

创建9001项目后，引入坐标依赖

<dependencies>  <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId> </dependency>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-actuator</artifactId> </dependency> <dependency> <groupId>org.projectlombok</groupId> <artifactId>lombok</artifactId> <optional>true</optional> </dependency>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>test</scope> </dependency> </dependencies>

重点是SpringCloud ailibaba nacos依赖，上面代码中这个依赖没有写对应的版本，因为在父工程中的pom中引入的alibaba的坐标依赖，里面就有对应的版本控制

修改配置yml文件

server: port: 9001 spring: application: name: nacos-payment-provider cloud: nacos: discovery: server-addr: 39.96.22.34:8848 #配置Nacos地址 management: endpoints: web: exposure: include: "*"

controller写接口

@RestController public class PaymentController { @Value("${server.port}") private String port; @GetMapping("/payment/nacos/{id}") public String getPayment(@PathVariable("id") Long id){ return "nacos registry,serverPort:"+port+"\t id:"+id; } }

主启动类最后启动该项目即可，然后登录Nacos，就可以看到有该服务的入住同样的创建9002服务，内容基本一样，只是端口号改为了9002。

服务消费者创建创建cloud-alibaba-nacos-consumer-order83模块，用来调用支付服务，引入坐标依赖

yml

server: port: 83 spring: application: name: nacos-consumer-order83 cloud: nacos: discovery: server-addr: 39.96.22.34:8848 #配置Nacos地址 server-url: nacos-user-service: http://nacos-payment-provider

主启动类这里的服务调用先暂时采用restTemplate的方式进行，跟之前的一样，先编写配置类，注意注解的添加

@Configuration public class ApplicationContextConfig { @Bean @LoadBalanced public RestTemplate getRestTemplate(){ return new RestTemplate(); } }

编写接口进行服务调用

@RestController public class PaymentController { @Resource private RestTemplate restTemplate; @Value("${server-url.nacos-user-service}") private String url; @GetMapping("/consumer/payment/nacos/{id}") public String paymentInfo(@PathVariable("id") Long id){ return restTemplate.getForObject(url+"/payment/nacos/"+id,String.class); } }

之后启动9001、9002、83三个项目服务也已经入住同时也实现了负载均衡

（2）服务配置

Nacos作为配置中心，它跟之前Config不一样，Nacos简化了Config的很多的操作，它可以实现实时刷新配置，而且，Nacos的配置文件不再存放到github等远程仓库那样麻烦，而是存放在Nacos上面，这样就简化了很多配置等操作，变得对开发人员更加友好，还有很重要的一点是，Nacos引入了命名空间、分组等来区分并存放远程的配置文件下面简单讲一下Nacos作为服务配置的便利性，以及为什么说是对程序员很友好。

服务配置模块创建首先创建一个服务配置中心模块cloud-alibaba-nacos-config-client-3377，引入pom文件

<dependencies>  <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-starter-alibaba-nacos-config</artifactId> </dependency>  <dependency> <groupId>com.alibaba.cloud</groupId> <artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId> </dependency>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-actuator</artifactId> </dependency>  <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>test</scope> </dependency> </dependencies>

重点是nacos config的引入，然后是配置文件，这里要配置两个配置文件，一个是bootstrap.yml，用来注册服务以及端口号等配置，一个是application.yml，用于切换不同环境的配置文件

bootstrap.yml

server: port: 3377 spring: application: name: nacos-config-client cloud: nacos: discovery: server-addr: 39.96.22.34:8848 #配置Nacos地址 config: server-addr: 39.96.22.34:8848 #配置Nacos地址 file-extension: yaml namespace: bd1a2abd-aec2-4ddf-9a62-b651fcd79436 #命名空间的id group: DEV_GROUP #分组

application.yml

spring: profiles: active: dev #开发环境

编写接口，注意加上@RefreshScope注解

@RestController @RefreshScope //注意添加Nacos配置的动态实时刷新 public class ConfigClientController { @Value("${config.info}") private String configInfo; @GetMapping("/config/info") public String getConfigInfo(){ return configInfo; } }

最后是主启动类

Nacos配置文件首先是在Nacos上面创建命名空间Namespace01 然后是在对应的分组下创建分组，以及配置文件

这里要重点说一下，配置的文件名字的规范这样，就在Namespaces01命名空间下创建了一个分组DEV_GROUP，该分组下有一个配置nacos-config-client-dev.yaml配置文件注意，上面在bootstrap.yml中需要配置对应的命名空间和分组名

运行3377项目，访问成功，当然也可以自己随便创建并切换其他环境当在Nacos上面修改了配置文件后，项目不用重启都会实现实时配置刷新，这就相当于整合了之前的Config和Bus的功能，而且Nacos用起来也很方便。

三、Nacos集群

简单说一高可用的Nacos集群的架构图微服务首先访问nginx服务集群，通过反向代理到相关的nacos集群，nacos集群再访问数据库集群。

由于本人用的服务器配置太差，不支持搭建这么复杂的集群架构，而且只有一台服务器，这里就只搭建1台nginx + 2台nacos+1台mysql这样的集群，本来想多搭建几个nacos集群，结果nacos消耗的内存太高，服务器只有2G内存，只够支持两台nacos的搭建，所以才选择了这样的架构，实际生成肯定不止一台nginx，也不止一台mysql

（1）数据库创建

docker如何下载mysql镜像以及创建可以看本人的菜鸟学习Docker实例这篇博客。

首先创建数据库，用于nacos，不再使用nacos的内置服务器，数据库名：nacos_config，sql脚本如下

/* Navicat Premium Data Transfer Source Server : cainiao Source Server Type : MySQL Source Server Version : 80019 Source Schema : nacos_config Target Server Type : MySQL Target Server Version : 80019 File Encoding : 65001 Date: 06/10/2020 10:40:58 */ SET NAMES utf8mb4; SET FOREIGN_KEY_CHECKS = 0; -- ---------------------------- -- Table structure for config_info -- ---------------------------- DROP TABLE IF EXISTS `config_info`; CREATE TABLE `config_info` ( `id` bigint(0) NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `content` longtext CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'content', `md5` varchar(32) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'md5', `gmt_create` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', `src_user` text CHARACTER SET utf8 COLLATE utf8_bin NULL COMMENT 'source user', `src_ip` varchar(20) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'source ip', `app_name` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `tenant_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT '' COMMENT '租户字段', `c_desc` varchar(256) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `c_use` varchar(64) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `effect` varchar(64) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `type` varchar(64) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `c_schema` text CHARACTER SET utf8 COLLATE utf8_bin NULL, PRIMARY KEY (`id`) USING BTREE, UNIQUE INDEX `uk_configinfo_datagrouptenant`(`data_id`, `group_id`, `tenant_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = 'config_info' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for config_info_aggr -- ---------------------------- DROP TABLE IF EXISTS `config_info_aggr`; CREATE TABLE `config_info_aggr` ( `id` bigint(0) NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'group_id', `datum_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'datum_id', `content` longtext CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT '内容', `gmt_modified` datetime(0) NOT NULL COMMENT '修改时间', `app_name` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `tenant_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT '' COMMENT '租户字段', PRIMARY KEY (`id`) USING BTREE, UNIQUE INDEX `uk_configinfoaggr_datagrouptenantdatum`(`data_id`, `group_id`, `tenant_id`, `datum_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = '增加租户字段' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for config_info_beta -- ---------------------------- DROP TABLE IF EXISTS `config_info_beta`; CREATE TABLE `config_info_beta` ( `id` bigint(0) NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'group_id', `app_name` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'app_name', `content` longtext CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'content', `beta_ips` varchar(1024) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'betaIps', `md5` varchar(32) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'md5', `gmt_create` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', `src_user` text CHARACTER SET utf8 COLLATE utf8_bin NULL COMMENT 'source user', `src_ip` varchar(20) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'source ip', `tenant_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT '' COMMENT '租户字段', PRIMARY KEY (`id`) USING BTREE, UNIQUE INDEX `uk_configinfobeta_datagrouptenant`(`data_id`, `group_id`, `tenant_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = 'config_info_beta' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for config_info_tag -- ---------------------------- DROP TABLE IF EXISTS `config_info_tag`; CREATE TABLE `config_info_tag` ( `id` bigint(0) NOT NULL AUTO_INCREMENT COMMENT 'id', `data_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'group_id', `tenant_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT '' COMMENT 'tenant_id', `tag_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'tag_id', `app_name` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'app_name', `content` longtext CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'content', `md5` varchar(32) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'md5', `gmt_create` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', `src_user` text CHARACTER SET utf8 COLLATE utf8_bin NULL COMMENT 'source user', `src_ip` varchar(20) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'source ip', PRIMARY KEY (`id`) USING BTREE, UNIQUE INDEX `uk_configinfotag_datagrouptenanttag`(`data_id`, `group_id`, `tenant_id`, `tag_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = 'config_info_tag' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for config_tags_relation -- ---------------------------- DROP TABLE IF EXISTS `config_tags_relation`; CREATE TABLE `config_tags_relation` ( `id` bigint(0) NOT NULL COMMENT 'id', `tag_name` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'tag_name', `tag_type` varchar(64) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'tag_type', `data_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'data_id', `group_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'group_id', `tenant_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT '' COMMENT 'tenant_id', `nid` bigint(0) NOT NULL AUTO_INCREMENT, PRIMARY KEY (`nid`) USING BTREE, UNIQUE INDEX `uk_configtagrelation_configidtag`(`id`, `tag_name`, `tag_type`) USING BTREE, INDEX `idx_tenant_id`(`tenant_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = 'config_tag_relation' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for group_capacity -- ---------------------------- DROP TABLE IF EXISTS `group_capacity`; CREATE TABLE `group_capacity` ( `id` bigint(0) UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键ID', `group_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '' COMMENT 'Group ID，空字符表示整个集群', `quota` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '配额，0表示使用默认值', `usage` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '使用量', `max_size` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '单个配置大小上限，单位为字节，0表示使用默认值', `max_aggr_count` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '聚合子配置最大个数，，0表示使用默认值', `max_aggr_size` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '单个聚合数据的子配置大小上限，单位为字节，0表示使用默认值', `max_history_count` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '最大变更历史数量', `gmt_create` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', PRIMARY KEY (`id`) USING BTREE, UNIQUE INDEX `uk_group_id`(`group_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = '集群、各Group容量信息表' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for his_config_info -- ---------------------------- DROP TABLE IF EXISTS `his_config_info`; CREATE TABLE `his_config_info` ( `id` bigint(0) UNSIGNED NOT NULL, `nid` bigint(0) UNSIGNED NOT NULL AUTO_INCREMENT, `data_id` varchar(255) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL, `group_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL, `app_name` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'app_name', `content` longtext CHARACTER SET utf8 COLLATE utf8_bin NOT NULL, `md5` varchar(32) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `gmt_create` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP, `gmt_modified` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP, `src_user` text CHARACTER SET utf8 COLLATE utf8_bin NULL, `src_ip` varchar(20) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `op_type` char(10) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL, `tenant_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT '' COMMENT '租户字段', PRIMARY KEY (`nid`) USING BTREE, INDEX `idx_gmt_create`(`gmt_create`) USING BTREE, INDEX `idx_gmt_modified`(`gmt_modified`) USING BTREE, INDEX `idx_did`(`data_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = '多租户改造' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for permissions -- ---------------------------- DROP TABLE IF EXISTS `permissions`; CREATE TABLE `permissions` ( `role` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL, `resource` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL, `action` varchar(8) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL, UNIQUE INDEX `uk_role_permission`(`role`, `resource`, `action`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for roles -- ---------------------------- DROP TABLE IF EXISTS `roles`; CREATE TABLE `roles` ( `username` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL, `role` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL, UNIQUE INDEX `idx_user_role`(`username`, `role`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for tenant_capacity -- ---------------------------- DROP TABLE IF EXISTS `tenant_capacity`; CREATE TABLE `tenant_capacity` ( `id` bigint(0) UNSIGNED NOT NULL AUTO_INCREMENT COMMENT '主键ID', `tenant_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '' COMMENT 'Tenant ID', `quota` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '配额，0表示使用默认值', `usage` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '使用量', `max_size` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '单个配置大小上限，单位为字节，0表示使用默认值', `max_aggr_count` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '聚合子配置最大个数', `max_aggr_size` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '单个聚合数据的子配置大小上限，单位为字节，0表示使用默认值', `max_history_count` int(0) UNSIGNED NOT NULL DEFAULT 0 COMMENT '最大变更历史数量', `gmt_create` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '创建时间', `gmt_modified` datetime(0) NOT NULL DEFAULT CURRENT_TIMESTAMP COMMENT '修改时间', PRIMARY KEY (`id`) USING BTREE, UNIQUE INDEX `uk_tenant_id`(`tenant_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = '租户容量信息表' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for tenant_info -- ---------------------------- DROP TABLE IF EXISTS `tenant_info`; CREATE TABLE `tenant_info` ( `id` bigint(0) NOT NULL AUTO_INCREMENT COMMENT 'id', `kp` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL COMMENT 'kp', `tenant_id` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT '' COMMENT 'tenant_id', `tenant_name` varchar(128) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT '' COMMENT 'tenant_name', `tenant_desc` varchar(256) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'tenant_desc', `create_source` varchar(32) CHARACTER SET utf8 COLLATE utf8_bin NULL DEFAULT NULL COMMENT 'create_source', `gmt_create` bigint(0) NOT NULL COMMENT '创建时间', `gmt_modified` bigint(0) NOT NULL COMMENT '修改时间', PRIMARY KEY (`id`) USING BTREE, UNIQUE INDEX `uk_tenant_info_kptenantid`(`kp`, `tenant_id`) USING BTREE, INDEX `idx_tenant_id`(`tenant_id`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_bin COMMENT = 'tenant_info' ROW_FORMAT = Dynamic; -- ---------------------------- -- Table structure for users -- ---------------------------- DROP TABLE IF EXISTS `users`; CREATE TABLE `users` ( `username` varchar(50) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL, `password` varchar(500) CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL, `enabled` tinyint(1) NOT NULL, PRIMARY KEY (`username`) USING BTREE ) ENGINE = InnoDB CHARACTER SET = utf8 COLLATE = utf8_general_ci ROW_FORMAT = Dynamic; SET FOREIGN_KEY_CHECKS = 1;

创建完的数据库

（2）nacos集群搭建

nacos8846

sudo docker run -d \ -e PREFER_HOST_MODE=hostname \ -e MODE=cluster \ -e NACOS_APPLICATION_PORT=8846 \ -e NACOS_SERVERS="39.96.22.34:8848 39.96.22.34:8847 39.96.22.34:8846" \ -e SPRING_DATASOURCE_PLATFORM=mysql \ -e MYSQL_SERVICE_HOST=39.96.22.34 \ -e MYSQL_SERVICE_PORT=3306 \ -e MYSQL_SERVICE_USER=root \ -e MYSQL_SERVICE_PASSWORD=123456 \ -e MYSQL_SERVICE_DB_NAME=nacos_config \ -e NACOS_SERVER_IP=39.96.22.34 \ -e JVM_XMS=256m \ -e JVM_XMX=256m \ -e JVM_XMN=256m \ -p 8846:8846 \ --name nacos8846 \ nacos/nacos-server:1.3.2

nacos8847

sudo docker run -d \ -e PREFER_HOST_MODE=hostname \ -e MODE=cluster \ -e NACOS_APPLICATION_PORT=8847 \ -e NACOS_SERVERS="39.96.22.34:8848 39.96.22.34:8847 39.96.22.34:8846" \ -e SPRING_DATASOURCE_PLATFORM=mysql \ -e MYSQL_SERVICE_HOST=39.96.22.34 \ -e MYSQL_SERVICE_PORT=3306 \ -e MYSQL_SERVICE_USER=root \ -e MYSQL_SERVICE_PASSWORD=123456 \ -e MYSQL_SERVICE_DB_NAME=nacos_config \ -e NACOS_SERVER_IP=39.96.22.34 \ -e JVM_XMS=256m \ -e JVM_XMX=256m \ -e JVM_XMN=256m \ -p 8847:8847 \ --name nacos8847 \ nacos/nacos-server:1.3.2

注意：上面的代码里面需要加下面几个参数，用来降低nacos的内存消耗，不然只能启动一台，内存就被耗完了，就无法启动第二台nacos

-e JVM_XMS=256m \ -e JVM_XMX=256m \ -e JVM_XMN=256m \

创建成功后可以看一下有没有成功启动两个都可以访问

（3）nginx配置

关于nginx容器的下载和创建看本人的菜鸟学习Docker实例这篇博客。

下面给出配置文件default.conf的配置

upstream my-server{ #ip_hash; server 39.96.22.34:8846 ;#服务器1(nacos8846) server 39.96.22.34:8847 ;#服务器2(nacos8847) } server { #监听的默认端口 listen 8080; #服务器的域名可以有多个，用空格隔开 server_name localhost; location / { proxy_pass http://my-server; } }

启动nginx容器访问nginx，实现了反向代理功能，而且也能代理到nacos集群

（4）集群测试

查看集群节点，8846和8847随便访问一个，都可以看到集群节点，这里本人创建了3个集群节点，另外一个是8848，但是由于服务器内存不足，只能启动其中两个，所以8848就处于宕机状态

首先在8846项目创建一个命名空间，然后刷新8847，发现两个都同时更新了命名空间，当然因为他们共用一个数据库，所以数据更新应该是一致的模拟其中一台服务器宕机的情况，先通过nginx访问集群，可以访问，再关掉8847容器，再访问nginx，多次访问都没有问题

四、微服务入住nacos集群

这次还是用上面创建的三个项目3377、9001和9002项目进行服务的入住以及服务配置，

首先在Nacos集群上创建一个配置文件，命名空间是Namespaces8846，小组名DEV_GROUP

首先的服务注册，以9001项目为例，修改配置文件，将其注册到Namespaces8846

server: port: 9001 spring: application: name: nacos-payment-provider cloud: nacos: discovery: # server-addr: 39.96.22.34:8848 #单机版配置Nacos地址 server-addr: 39.96.22.34:8080 #将服务注册进nginx代理的nacos集群 namespace: ffee2bbe-5ba5-4e6e-a822-6a00abe11769 #命名空间的id management: endpoints: web: exposure: include: "*"

8080端口是nginx代理的端口，通过nginx反向代理到nacos集群，启动9001项目，可以看到已经有服务入住了

然后是服务配置，这里用3377项目，修改其配置文件

server: port: 3377 spring: application: name: nacos-config-client cloud: nacos: discovery: server-addr: 39.96.22.34:8080 namespace: ffee2bbe-5ba5-4e6e-a822-6a00abe11769 #命名空间的id # server-addr: 39.96.22.34:8848 #单机版配置Nacos地址 #服务配置 config: server-addr: 39.96.22.34:8080 # server-addr: 39.96.22.34:8848 #单机版配置Nacos地址 file-extension: yaml namespace: ffee2bbe-5ba5-4e6e-a822-6a00abe11769 #命名空间的id group: DEV_GROUP #分组

启动3377项目，查看nacos集群，服务已经入住测试读取服务配置

配置文件的数据确实也已经读取到。

Processed: 0.026, SQL: 8