Nacos 作为微服务核心的服务注册与发现中心,对比Eureka。
Raft 协议强依赖 Leader 节点来确保集群数据一致性。即 client 发送过来的数据均先到达 Leader 节点,Leader 接收到数据后,
先将数据标记为 uncommitted 状态,随后 Leader 开始向所有 Follower 复制数据并等待响应,在获得集群中大于 N/2 个 Follower
的已成功接收数据完毕的响应后,Leader 将数据的状态标记为 committed,随后向 client 发送数据已接收确认,在向 client 发送
出已数据接收后,再向所有 Follower 节点发送通知表明该数据状态为committed。
Nacos作为微服务配置中心对比Spring Cloud Config
在使用Nacos之前需要先下载Nacos Server,下载地址:
github下载
Nacos Server有两种运行模式
1.standalone模式
此模式一般用于demo和测试。命令如下。
bin/startup.sh -m standalone # linux
bin/startup.cmd -m standalone # windows
或者修改配置文件startup.cmd,代码如下,默认为cluster,然后直接运行startup.cmd
set MODE="standalone"
2. cluster模式
cluster 模式需要依赖 MySQL,然后改两个配置文件:
cluster模式配置如下。
(1)cluster.conf,填入要运行 Nacos Server 机器的 ip
192.168.100.xxx
192.168.100.xxx
(2)修改NACOS_PATH/conf/application.properties,加入 MySQL 配置
db.num=1
db.url.0=jdbc:mysql://localhost:3306/nacos_config?characterEncoding=utf8&connectTimeout=1000&socketTimeout=3000&autoReconnect=true
db.user=root
db.password=root
创建一个名为nacos_config的 database,将NACOS_PATH/conf/nacos-mysql.sql中的表结构导入刚才创建的库中。
问题来了: Nacos Server 的配置数据是存在哪里呢?我们没有对 Nacos Server 做任何配置,那么数据只有两个位置可以存储:
随便创建一个配置文件,重启nacos,配置文件还在,说明不是内存存储的。
这时候我们打开NACOS_PATH/data,会发现里边有个derby-data目录,我们的配置数据现在就存储在这个库中。
Derby 是 Java 编写的数据库,属于 Apache 的一个开源项目
Nacos Server 的数据源是用 Derby 还是 MySQL 完全是由其运行模式决定的:
注意:不支持 MySQL 8.0 版本
使用订单和支付服务,在订单微服务中调用支付微服务,演示Nacos作为注册中心的用法,如图所示
父工程统一管理spring boot,spring cloud和spring cloud alibaba版本号,注意参考版本对应关系。
本文演示中使用版本如下
注意:spring-cloud-starter-bootstrap组件,在Spring Boot 2.4.X版本中,不在加载bootstrap.yml,需要spring-cloud-starter-bootstrap组件,才能加载bootstrap.yml配置文件。
<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.0modelVersion>
<groupId>com.cave.demogroupId>
<artifactId>cloud-alibaba-demoartifactId>
<version>1.0-SNAPSHOTversion>
<modules>
<module>paymentmodule>
<module>ordermodule>
modules>
<packaging>pompackaging>
<parent>
<groupId>org.springframework.bootgroupId>
<artifactId>spring-boot-starter-parentartifactId>
<version>2.6.3version>
<relativePath/>
parent>
<properties>
<java.version>1.8java.version>
<alibaba-cloud.version>2021.0.1.0alibaba-cloud.version>
<springcloud.version>2021.0.1springcloud.version>
properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.cloudgroupId>
<artifactId>spring-cloud-dependenciesartifactId>
<version>${springcloud.version}version>
<type>pomtype>
<scope>importscope>
dependency>
<dependency>
<groupId>com.alibaba.cloudgroupId>
<artifactId>spring-cloud-alibaba-dependenciesartifactId>
<version>${alibaba-cloud.version}version>
<type>pomtype>
<scope>importscope>
dependency>
dependencies>
dependencyManagement>
<dependencies>
<dependency>
<groupId>org.springframework.bootgroupId>
<artifactId>spring-boot-starter-actuatorartifactId>
dependency>
<dependency>
<groupId>org.springframework.cloudgroupId>
<artifactId>spring-cloud-starter-bootstrapartifactId>
dependency>
<dependency>
<groupId>org.springframework.bootgroupId>
<artifactId>spring-boot-devtoolsartifactId>
<scope>runtimescope>
<optional>trueoptional>
dependency>
<dependency>
<groupId>org.projectlombokgroupId>
<artifactId>lombokartifactId>
<optional>trueoptional>
dependency>
<dependency>
<groupId>org.springframework.bootgroupId>
<artifactId>spring-boot-starter-testartifactId>
<scope>testscope>
dependency>
<dependency>
<groupId>org.apache.commonsgroupId>
<artifactId>commons-lang3artifactId>
<version>3.9version>
dependency>
dependencies>
<build>
<plugins>
<plugin>
<groupId>org.springframework.bootgroupId>
<artifactId>spring-boot-maven-pluginartifactId>
<configuration>
<excludes>
<exclude>
<groupId>org.projectlombokgroupId>
<artifactId>lombokartifactId>
exclude>
excludes>
configuration>
plugin>
plugins>
build>
project>
<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">
<parent>
<artifactId>cloud-alibaba-demoartifactId>
<groupId>com.cave.demogroupId>
<version>1.0-SNAPSHOTversion>
parent>
<modelVersion>4.0.0modelVersion>
<artifactId>paymentartifactId>
<dependencies>
<dependency>
<groupId>org.springframework.bootgroupId>
<artifactId>spring-boot-starter-webartifactId>
dependency>
<dependency>
<groupId>com.alibaba.cloudgroupId>
<artifactId>spring-cloud-starter-alibaba-nacos-discoveryartifactId>
dependency>
dependencies>
project>
server:
port: ${port:9001}
spring:
application:
name: payment-service
cloud:
nacos:
discovery:
server-addr: localhost:8848 #配置Nacos地址
@SpringBootApplication
@EnableDiscoveryClient
public class PaymentApplication
{
public static void main(String[] args) {
SpringApplication.run(PaymentApplication.class, args);
}
}
@RestController
@RequestMapping("/payment")
public class PaymentController {
@Value("${server.port}")
private String serverPort;
@GetMapping("/{id}")
public ResponseEntity<String> payment(@PathVariable("id") Long id) {
return ResponseEntity.ok("订单号 = " + id + ",支付成功,server.port" + serverPort);
}
}
启动两个服务实例端口号分别为9001和9002,注册到nacos中
配置文件port: ${port:9001}表示,没有port参数,使用9001端口,有port参数则使用port参数指定的端口,使用9002端口的支付服务,如图所示。
使用9001端口支付服务,如图所示
访问nacos查看服务列表,如图所示
注意:必须依赖spring-cloud-starter-loadbalancer组件,spring-cloud-starter-alibaba-nacos-discovery,不在默认继承ribbon,而是使用Spring Cloud Common总的loadbalancer组件,实现负载均衡
<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">
<parent>
<artifactId>cloud-alibaba-demoartifactId>
<groupId>com.cave.demogroupId>
<version>1.0-SNAPSHOTversion>
parent>
<modelVersion>4.0.0modelVersion>
<artifactId>orderartifactId>
<dependencies>
<dependency>
<groupId>org.springframework.bootgroupId>
<artifactId>spring-boot-starter-webartifactId>
dependency>
<dependency>
<groupId>com.alibaba.cloudgroupId>
<artifactId>spring-cloud-starter-alibaba-nacos-discoveryartifactId>
dependency>
<dependency>
<groupId>org.springframework.cloudgroupId>
<artifactId>spring-cloud-starter-openfeignartifactId>
dependency>
<dependency>
<groupId>org.springframework.cloudgroupId>
<artifactId>spring-cloud-starter-loadbalancerartifactId>
dependency>
dependencies>
project>
server:
port: 9003
spring:
application:
name: order-service
cloud:
nacos:
discovery:
server-addr: localhost:8848
@EnableDiscoveryClient
@SpringBootApplication
@EnableFeignClients
public class OrderApplication
{
public static void main(String[] args) {
SpringApplication.run(OrderApplication.class, args);
}
}
Nacos底层使用Spring Cloud Common中的Spring Cloud LoadBalancer组件实现负载均衡,注入RestTemplate,使用注解@LoadBalanced开启负载均衡功能。
@Configuration
public class ApplicationContextConfig {
@Bean
@LoadBalanced
public RestTemplate getRestTemplate(){
return new RestTemplate();
}
}
(1)PaymentFallbackService
@Component
public class PaymentFallbackService implements PaymentService {
@Override
public ResponseEntity<String> payment(Long id) {
return new ResponseEntity<String>("feign调用,异常降级方法", HttpStatus.INTERNAL_SERVER_ERROR);
}
}
(2) PaymentService
@FeignClient(value = "payment-service", fallback = PaymentFallbackService.class)
public interface PaymentService {
@GetMapping("/payment/{id}")
public ResponseEntity<String> payment(@PathVariable("id") Long id);
}
@RestController
@RequestMapping("/order")
public class OrderController {
public static final String SERVICE_URL = "http://payment-service";
@Resource
private RestTemplate restTemplate;
@GetMapping("/lb/{id}")
public ResponseEntity<String> consumer_ribbon(@PathVariable("id") Integer id){
String result = restTemplate.getForObject("http://payment-service" + "/payment/" + id, String.class);
return ResponseEntity.ok(result);
}
//OpenFeign
@Resource
private PaymentService paymentService;
@GetMapping(value = "/feign/{id}")
public ResponseEntity<String> consumer_feign(@PathVariable("id") Long id) {
return paymentService.payment(id);
}
}
访问http://localhost:9003/order/lb/2地址,可以看到9001和9002端口交替执行,因为nacos底层也是采用Spring Cloud Loadbalancer进行负载均衡处理