提供的先进的容器编排技术，服务网格产品开始进入开发者的视野，并得到了 广泛的关注，其中不乏有头部互联网公司已经将服务网格应用在生产环境中。在这些产品当中，由 Google，IBM 和 Lyft 团队合作开发的服务网格项目 Istio 最为流行，它提出了⼀整套标准的、声 明式的服务治理 API，效仿 Kubernetes 对底层基础设施的抽象做法来解决服务治理层面的疑难杂 症。 Nacos 作为众多注册中心产品中最受欢迎 之初，就紧跟技术时代的潮流，当然 不会错过云原生带来的技术红利。Nacos 已深度集成明星产品 Spring Boot、Spring Cloud、 Dubbo 等等，到现在积极融入服务网格 Istio 的生态，都在为开发者可以在各种业务场景中使用 Nacos 而演进。 什么是服务网格 要深入理解服务网格的概念，明确服务网格要解决的问题，以及认识服务网格带来的业务价值，需 要从应用架构的演进发展从头开始讲起。 写的服务，很难融入面向微服务的架构体系中，想因地制宜的用多种语言实现架构体系中的不同 模块也很难做到。 Nacos 生态 < 154 下⼀代微服务架构——服务网格 为了解决传统微服务体系架构的上述三种局限性，以 Istio，NginxMesh 为代表的代理模式（边车 模式）应运而生，这就是当前微服务架构领域比较火热的服务网格技术——Service Mesh，它将分 布式服务的通信层抽象为单独的⼀层，在这⼀层中实

network traffic overhead and the least burden on the client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarantees that

Documentation 220 Protocols and Interoperability client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarantees that

network traffic overhead and the least burden on the client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarentees that

network traffic overhead and the least burden on the client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarantees that

network traffic overhead and the least burden on the client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarantees that

network traffic overhead and the least burden on the client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarantees that

network traffic overhead and the least burden on the client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarantees that

network traffic overhead and the least burden on the client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarantees that

network traffic overhead and the least burden on the client and the broker and is often useful for telemetry data where it doesn't matter if some of the data is lost. QoS 1: AT LEAST ONCE: Guarantees that