Service Mesh终极指南（第二版）：次世代微服务开发

{"type":"doc","content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在过去的几年里，服务网格（Service Mesh）技术取得了长足的进步。服务网格在不同组织采用云本地的过程中扮演着重要的角色。通过提供连接性、可靠性、可观察性和安全性这四种主要类型的功能，服务网格已经成为IT组织的技术和基础设施现代化工作的核心组件。服务网格使开发和运维团队能够在基础设施级别实现这些功能，因此在涉及到非功能需求切面时，应用程序团队不需要付出重复性劳动。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"自本文"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/service-mesh-ultimate-guide\/","title":"","type":null},"content":[{"type":"text","text":"第一版"}]},{"type":"text","text":"于2020年2月发表以来，服务网格技术经历了重大创新，并出现了一些新的架构趋势、技术能力，在不断发展的服务网格领域也不断涌现出新的服务网格项目。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在过去的一年里，服务网格产品的发展已经远远超过了Kubernetes-only解决方案，之前那些不在Kubernetes平台上托管的应用无法利用服务网格。并不是所有的组织都将他们的业务和IT应用程序转移到Kubernetes云平台。因此，自服务网格诞生以来，这种技术就需要能够应用于不同的IT基础设施环境中。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"随着微服务架构的日益普及，应用系统在云提供商、基础设施(Kubernetes、虚拟机、裸机服务器)、地理位置，甚至在服务网格集成环境中管理的工作负载类型等方面都已变得松耦合和分布式。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"让我们先来回顾一下服务网格是如何诞生的。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"2016年前后，“服务网格”一词出现在微服务、云计算和DevOps领域。2016年，Buoyant 团队用"},{"type":"link","attrs":{"href":"https:\/\/twitter.com\/wm\/status\/1383061764938469377?s=20","title":"","type":null},"content":[{"type":"text","text":"这个词"}]},{"type":"text","text":"来解释他们的产品Linkerd。与计算机的许多概念一样，相关的模式和技术实际上有很长的历史。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格的到来很大程度上是由于IT领域的一场完美风暴。开发人员开始使用多语言方法构建分布式系统，并需要动态的服务发现。运营开始使用临时基础设施，并希望可以优雅地处理那些不可避免的通信故障，以及实施网络策略。平台团队开始采用Kubernetes之类的容器编排系统，并希望使用现代API驱动的网络代理(如Envoy)动态地将流量路由到系统内部或周围。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"本文旨在回答针对软件架构师和技术领导者的相关问题，例如：什么是服务网格？我需要服务网吗？我如何评估不同的服务网供应？"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"您可以使用页面底部的导航目录来快速浏览本指南。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格模式"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格模式专注于管理分布式软件系统中服务到服务的所有通信。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"上下文"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"该模式的上下文有两个方面：第一，工程师已经采用了微服务体系结构模式，并且正在通过组合多个(理想情况下是单一用途和独立部署的)服务来构建他们的应用程序。第二，组织已经接受了云原生平台技术，如容器(如Docker)、协调器(如Kubernetes)和网关。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"意图"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格模式试图解决的问题包括："}]},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"无需将特定于语言的通信库编译为单个服务来处理服务发现、路由和应用程序级(第7层)非功能性通信需求。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"外化服务通信配置，包括外部服务的网络位置、安全凭据和服务质量目标。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"提供其他服务的被动和主动监视。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在分布式系统中分散政策的执行。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"提供可观察性默认值并标准化相关数据的收集。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":1,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"启用请求日志记录"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":1,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"配置分布式跟踪"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":1,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"收集度量指标"}]}]}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"结构"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格模式主要关注处理传统上称为“东-西”的基于远程过程调用(RPC)的流量：即起源于数据中心内部，并在服务到服务之间传播的请求\/响应类型的通信。这与API网关或边缘代理相反，API网关或边缘代理的设计目的是处理“南-北”流量：即从外部发出并进入数据中心内端点或服务的通信。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格的特性"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"一个服务网格实现通常会提供以下一个或多个特性："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"规范命名并添加逻辑路由(例如，将代码级名称“user-service”映射到特定于平平台的位置“AWS-us-east-1a\/prod\/users\/v4”)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"提供通讯成形和通讯变换"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"维持负载平衡，通常使用可配置的算法"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"提供服务释放控制(例如，金丝雀发布和流量分割)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"提供请求级路由(例如，流量跟踪、故障注入和调试重路由)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"添加基线可靠性，如运行状况检查、超时\/截止日期、电路断开和重试(预算)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"通过透明的双向传输层安全(TLS)和访问控制列表(ACL)等策略提高安全性"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"提供额外的可观察性和监视性，例如顶级指标(请求量、成功率和延迟)、对分布式跟踪的支持，以及“tap”和检查实时服务到服务通信的能力"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"允许平台团队配置“稳健的默认值”，以保护系统不会受到不良通信的影响"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格功能可以分为以下四个方面："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"连通性"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"可靠性"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"安全性"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"可观察性"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"让我们看看服务网格技术在这些领域中可以提供哪些特性。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"连通性："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"流量控制(路由、分割)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"网关(入口、出口)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务发现"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"A \/ B测试，金丝雀"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务超时，重试"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"可靠性："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"断路器"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"故障注入\/混沌测试"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"安全性："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务到服务的身份验证(MTL)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"证书管理"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"用户身份验证(JWT)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"用户授权(RBAC)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"加密"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"可观测性："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"监控"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"遥测、仪表、度量"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"分布式跟踪"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务图"}]}]}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格架构：引擎盖下的秘密"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格由两个高层次组件组成：数据面板和控制面板。"},{"type":"link","attrs":{"href":"https:\/\/www.envoyproxy.io\/","title":"","type":null},"content":[{"type":"text","text":"Envoy Proxy"}]},{"type":"text","text":"的创建者马特·克莱因(Matt Klein)对“"},{"type":"link","attrs":{"href":"https:\/\/blog.envoyproxy.io\/service-mesh-data-plane-vs-control-plane-2774e720f7fc","title":"","type":null},"content":[{"type":"text","text":"服务网格数据面板与控制面板"}]},{"type":"text","text":"”的主题进行了非常深入的研究。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"广义地说，数据面板“完成工作”，并负责“有条件地转换、转发和观察进出(网络端点)的每个网络数据包”。在现代系统中，数据面板通常被实现为代理(如Envoy、HAProxy或MOSN)，它与每个服务一起作为“边车”在进程外运行。Linkerd使用了一种针对服务网格边车用例进行优化的"},{"type":"link","attrs":{"href":"https:\/\/linkerd.io\/2020\/12\/03\/why-linkerd-doesnt-use-envoy\/","title":"","type":null},"content":[{"type":"text","text":"微代理"}]},{"type":"text","text":"方法。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"控制面板“监督工作”，并获取数据面板的所有独立实例(一组孤立的无状态边车代理)，并将它们转换为分布式系统。控制面板不接触系统中的任何数据包\/请求，但它允许运维人员为网格中所有运行的数据面板提供策略和配置。控制面板还可以收集和集中数据面板遥测数据，供运维人员使用。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"控制面板和数据面板的结合提供了两方面的优势，因为可以集中定义和管理策略，同时可以在Kubernetes集群的每个pod中以分布式方式执行相同的策略。策略可以关联到安全、路由、断路器或监控。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"下面的图表摘自Istio体系结构文档，尽管提到的技术是特定于Istio的，但组件对于所有服务网格实现都是通用的。"}]},{"type":"image","attrs":{"src":"https:\/\/static001.infoq.cn\/resource\/image\/db\/42\/db361e888845d1e02942179566b51c42.png","alt":null,"title":"","style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":"","fromPaste":false,"pastePass":false}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Istio架构，演示了控制面板和代理数据面板如何交互(由"},{"type":"link","attrs":{"href":"https:\/\/istio.io\/docs\/","title":"","type":null},"content":[{"type":"text","text":"Istio官方文档"}]},{"type":"text","marks":[{"type":"strong"}],"text":"提供)"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"用例"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格可以启用或支持各种用例。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"动态服务发现和路由"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格提供动态服务发现和流量管理，包括用于测试的流量镜像（traffic shadowing），以及用于金丝雀发布和A\/B类型试验的流量切分。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在服务网格中使用的代理通常是“应用层”感知的(在OSI网络堆栈的第7层操作)。这意味着流量路由决策和指标的标记可以利用HTTP头或其他应用层协议元数据中的数据。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"服务到服务的通信可靠性"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格支持横切如请求重试、超时、速率限制和断路等可靠性需求的实现和实施。服务网格通常用于针对"},{"type":"link","attrs":{"href":"https:\/\/en.wikipedia.org\/wiki\/Fallacies_of_distributed_computing","title":"","type":null},"content":[{"type":"text","text":"分布式计算的八种谬误"}]},{"type":"text","text":"进行补偿(或封装)处理。需要注意的是，服务网格只能提供连接级的可靠性支持(比如重试HTTP请求)，最终应该由服务负责所有业务相关的影响，比如避免多个(非幂等的)HTTP POST请求。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"流量的可观测性"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"由于服务网格位于系统正在处理的每个请求的关键路径上，因此它还可以提供额外的“可观察性”，例如对请求的分布式跟踪、HTTP错误码的频率以及全局和服务到服务的延迟。尽管这是一个在企业中被过度使用的词，但服务网格经常被提议作为一种捕获所有必要数据的方法，以实现整个系统内流量的“单窗格”视图。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"通信安全"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格还支持横切安全需求的实现和实施，例如提供服务身份(通过x509证书)，支持应用程序级服务\/网络分段(例如，“服务A”可以与“服务B”通信，而不是“服务C”)，确保所有通信都是加密的(通过TLS)，并确保持有有效的用户级身份令牌或“"},{"type":"link","attrs":{"href":"https:\/\/qconsf.com\/sf2019\/presentation\/user-device-identity-microservices-netflix-scale","title":"","type":null},"content":[{"type":"text","text":"护照"}]},{"type":"text","text":"”。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"反模式"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"反模式应用的出现，通常是技术成熟的标志。服务网格也不例外。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"太多的流量管理层级(一路龟行)"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"如果开发人员没有与平台或运维团队协调流通，直接在代码中复制现有的通信处理逻辑(现在正在通过服务网格实现)，就会出现此反模式。例如，除了服务网格配置提供的线路级重试策略外，应用程序还在代码中实现重试策略。此反模式可能会导致重复事务等问题。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"将服务网格视作银弹"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在IT领域没有所谓的“银弹”，但供应商有时会忍不住给新技术贴上这个标签。服务网格不能解决微服务、Kubernetes之类的容器协调器或云网络的所有通信问题。服务网格的目的只是促进服务到服务(东-西)的通信，部署和运行服务网格有明确的运维成本。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"企业服务总线(ESB) 2.0"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"在前微服务面向服务体系结构(SOA)时代，企业服务总线(ESB)实现了软件组件之间的通信系统。有些人担心，在使用服务网格时，ESB时代的许多错误会重复出现。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"很显然，通过ESB提供的通信集中控制是有价值的。然而，这些技术的开发是由供应商驱动的，这导致了许多问题，例如：ESB之间缺乏互操作性、行业标准的定制扩展(例如，将特定于供应商的配置添加到兼容WS-*的模式中)和高成本。ESB供应商未做什么去防止业务逻辑与通信总线的集成和紧密耦合。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"大爆炸式部署"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"IT界普遍存在一种诱惑，认为大规模部署方法是最容易管理的方法，但根据"},{"type":"link","attrs":{"href":"https:\/\/itrevolution.com\/book\/accelerate\/","title":"","type":null},"content":[{"type":"text","text":"Accelerate"}]},{"type":"text","text":"和"},{"type":"link","attrs":{"href":"https:\/\/puppet.com\/resources\/report\/state-of-devops-report\/","title":"","type":null},"content":[{"type":"text","text":"DevOps State报告"}]},{"type":"text","text":"的研究，情况并非如此。由于服务网格的全面推出意味着该技术处于处理所有终端用户请求的关键路径上，因此大爆炸部署风险很高。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"死星架构"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"当组织采用微服务体系结构，开发团队开始创建新的微服务或在其应用程序中利用现有服务时，服务到服务的通信就成为体系结构的关键部分。如果没有良好的治理模型，这可能导致不同服务之间的紧密耦合。当整个系统在生产中出现问题时，这也很难确定哪个服务出现了问题。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"缺乏服务通信策略和治理模型，该体系结构就变成了所谓的“死星架构”。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"有关此体系结构反模式的更多信息，请参阅关于采用云本地体系结构的第"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/cloud-native-architecture-adoption-part1\/","title":"","type":null},"content":[{"type":"text","text":"1"}]},{"type":"text","text":"、"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/cloud-native-architecture-adoption-part2\/","title":"","type":null},"content":[{"type":"text","text":"2"}]},{"type":"text","text":"和"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/cloud-native-architecture-adoption-part3\/","title":"","type":null},"content":[{"type":"text","text":"3"}]},{"type":"text","text":"部分文章。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"特定领域的服务网格"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"局部实现和过度优化服务网格有时会导致服务网格部署的范围过窄。开发人员可能更喜欢特定于他们自己业务领域的服务网格实例，但这种方法弊大于利。我们不想实现一个过于细粒度的服务网格范围，就像为组织中的每个业务或功能领域(例如，财务、人力资源、会计等)实现一个专用的服务网格。这与为企业级服务发现或跨域服务路由等功能使用公共服务编制解决方案(如服务网格)的目的不符。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格的实现和产品"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"以下是当前服务网格实现的非详尽列表："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/linkerd.io\/","title":"","type":null},"content":[{"type":"text","text":"Linkerd"}]},{"type":"text","text":"(CNCF毕业项目)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/istio.io\/","title":"","type":null},"content":[{"type":"text","text":"Istio"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.consul.io\/","title":"","type":null},"content":[{"type":"text","text":"Consul"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/kuma.io\/","title":"","type":null},"content":[{"type":"text","text":"Kuma"}]},{"type":"text","text":" (CNCF沙盒项目)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/aws.amazon.com\/app-mesh\/","title":"","type":null},"content":[{"type":"text","text":"AWS App Mesh"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.nginx.com\/products\/nginx-service-mesh\/","title":"","type":null},"content":[{"type":"text","text":"NGINX 服务网格"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/aspenmesh.io\/","title":"","type":null},"content":[{"type":"text","text":"AspenMesh"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/konghq.com\/kong-mesh\/","title":"","type":null},"content":[{"type":"text","text":"Kong"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.solo.io\/products\/gloo-mesh\/","title":"","type":null},"content":[{"type":"text","text":"Solo Gloo Mesh"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.tetrate.io\/tetrate-service-bridge\/","title":"","type":null},"content":[{"type":"text","text":"Tetrate Service Bridge"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"http:\/\/traefik.io\/traefik-mesh","title":"","type":null},"content":[{"type":"text","text":"Traefik Mesh"}]},{"type":"text","text":" (formerly Maesh)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"http:\/\/layer5.io\/meshery","title":"","type":null},"content":[{"type":"text","text":"Meshery"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"http:\/\/openservicemesh.io\/","title":"","type":null},"content":[{"type":"text","text":"Open 服务网格"}]},{"type":"text","text":"  (CNCF沙箱项目)"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"另外，"},{"type":"link","attrs":{"href":"https:\/\/www.datadoghq.com\/blog\/tag\/service-mesh\/","title":"","type":null},"content":[{"type":"text","text":"DataDog"}]},{"type":"text","text":"等其他产品也开始提供与Linkerd、Istio、Consul Connect和AWS App mesh等服务网格技术的集成。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格比较：选择哪款服务网格?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格领域的发展速度非常快，因此尝试做出的任何比较可能很快都会过时。但尽管如此，还是有人做了一些比较。要注意比较之间存在的偏差(如果有的话)和比较时的日期。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/layer5.io\/landscape","title":"","type":null},"content":[{"type":"text","text":"https：\/\/layer5.io\/landscape"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/kubedex.com\/istio-vs-linkerd-vs-linkerd2-vs-consul\/","title":"","type":null},"content":[{"type":"text","text":"https：\/\/kubedex.com\/istio-vs-linkerd-vs-linkerd2-vs-consul\/"}]},{"type":"text","text":" (截至2021年8月)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/platform9.com\/blog\/kubernetes-service-mesh-a-comparison-of-istio-linkerd-and-consul\/","title":"","type":null},"content":[{"type":"text","text":"https：\/\/platform9.com\/blog\/kubernetes-service-mesh-a-comparison-of-istio-linkerd-and-consul\/"}]},{"type":"text","text":"(截至2019年10月)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/servicemesh.es\/","title":"","type":null},"content":[{"type":"text","text":"https：\/\/servicemesh.es\/"}]},{"type":"text","text":" (最近的发布是2021年8月)"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格采用者自己对每个产品进行审慎的调查和试验是InfoQ一直不变的建议。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格教程"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"对于想要尝试多种服务网格的工程师或架构师来说，可以考虑以下教程、实训场和工具："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/layer5.io\/meshery","title":"","type":null},"content":[{"type":"text","text":"Layer 5 Meshery"}]},{"type":"text","text":"—一款多服务网格管理面板"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/github.com\/solo-io\/supergloo","title":"","type":null},"content":[{"type":"text","text":"Solo’s Gloo Mesh"}]},{"type":"text","text":"—一个服务网格编排平台"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.katacoda.com\/courses\/istio\/deploy-istio-on-kubernetes","title":"","type":null},"content":[{"type":"text","text":"KataCoda Istio 教程"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/learn.hashicorp.com\/consul","title":"","type":null},"content":[{"type":"text","text":"Consul 服务网格教程"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/linkerd.io\/2\/getting-started\/","title":"","type":null},"content":[{"type":"text","text":"Linkerd 教程"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/docs.nginx.com\/nginx-service-mesh\/tutorials\/","title":"","type":null},"content":[{"type":"text","text":"NGINX 服务网格教程"}]}]}]}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格的历史"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"自2013年末Airbnb发布"},{"type":"link","attrs":{"href":"https:\/\/medium.com\/airbnb-engineering\/smartstack-service-discovery-in-the-cloud-4b8a080de619","title":"","type":null},"content":[{"type":"text","text":"SmartStack"}]},{"type":"text","text":"以来，InfoQ一直在跟进我们现在称之为"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/servicemesh\/","title":"","type":null},"content":[{"type":"text","text":"服务网格"}]},{"type":"text","text":"的话题，SmartStack为新兴的“"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/microservices\/","title":"","type":null},"content":[{"type":"text","text":"微服务"}]},{"type":"text","text":"”风格架构提供了一种进程外服务发现机制(使用"},{"type":"link","attrs":{"href":"http:\/\/www.haproxy.org\/","title":"","type":null},"content":[{"type":"text","text":"HAProxy"}]},{"type":"text","text":")。在此之前，许多先前被称为“独角兽”的组织都在从事类似的技术。从21世纪初开始，谷歌就在开发它的"},{"type":"link","attrs":{"href":"https:\/\/grpc.io\/blog\/principles\/","title":"","type":null},"content":[{"type":"text","text":"Stubby "}]},{"type":"text","text":"RPC框架，并发展成为"},{"type":"link","attrs":{"href":"https:\/\/cloud.google.com\/blog\/products\/gcp\/grpc-a-true-internet-scale-rpc-framework-is-now-1-and-ready-for-production-deployments","title":"","type":null},"content":[{"type":"text","text":"gRPC"}]},{"type":"text","text":"，以及"},{"type":"link","attrs":{"href":"https:\/\/landing.google.com\/sre\/sre-book\/chapters\/production-environment\/","title":"","type":null},"content":[{"type":"text","text":"Google Frontend (GFE)"}]},{"type":"text","text":"和Global Software Load Balancer (GSLB)，在"},{"type":"link","attrs":{"href":"https:\/\/istio.io\/","title":"","type":null},"content":[{"type":"text","text":"Istio"}]},{"type":"text","text":"中可以看到这些特点。在2010年代早期，Twitter开始开发基于Scala的"},{"type":"link","attrs":{"href":"https:\/\/twitter.github.io\/finagle\/","title":"","type":null},"content":[{"type":"text","text":"Finagle"}]},{"type":"text","text":"， "},{"type":"link","attrs":{"href":"https:\/\/linkerd.io\/","title":"","type":null},"content":[{"type":"text","text":"Linkerd"}]},{"type":"text","text":"服务网络由此诞生。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"2014年底，Netflix发布了一整套"},{"type":"link","attrs":{"href":"https:\/\/netflix.github.io\/","title":"","type":null},"content":[{"type":"text","text":"基于JVM"}]},{"type":"text","text":"的实用程序，其中包括"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/news\/2014\/12\/netflix-prana\/","title":"","type":null},"content":[{"type":"text","text":"Prana"}]},{"type":"text","text":"，这是一个“边车”进程，允许用任何语言编写的应用程序服务通过HTTP与库的独立实例通信。2016年，NGINX团队开始讨论“"},{"type":"link","attrs":{"href":"https:\/\/www.nginx.com\/blog\/microservices-reference-architecture-nginx-fabric-model\/","title":"","type":null},"content":[{"type":"text","text":"Fabric模型"}]},{"type":"text","text":"”，它非常类似于服务网格，但需要使用他们的商业NGINX Plus产品来实现。此外，Linkerd v0.2是在2016年2月"},{"type":"link","attrs":{"href":"https:\/\/linkerd.io\/2016\/02\/18\/linkerd-twitter-style-operability-for-microservices\/","title":"","type":null},"content":[{"type":"text","text":"发布"}]},{"type":"text","text":"的，尽管团队后来才开始称其为服务网格。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格历史上的其他亮点包括2017年5月发布的"},{"type":"link","attrs":{"href":"https:\/\/istio.io\/","title":"","type":null},"content":[{"type":"text","text":"Istio"}]},{"type":"text","text":"， 2018年7月发布的"},{"type":"link","attrs":{"href":"https:\/\/linkerd.io\/2018\/09\/18\/announcing-linkerd-2-0\/","title":"","type":null},"content":[{"type":"text","text":"Linkerd 2.0"}]},{"type":"text","text":"， 2018年11月发布的"},{"type":"link","attrs":{"href":"https:\/\/www.hashicorp.com\/products\/consul\/service-mesh","title":"","type":null},"content":[{"type":"text","text":"Consul Connect"}]},{"type":"text","text":"和"},{"type":"link","attrs":{"href":"https:\/\/github.com\/solo-io\/supergloo","title":"","type":null},"content":[{"type":"text","text":"Gloo mesh"}]},{"type":"text","text":"， 2019年5月发布的"},{"type":"link","attrs":{"href":"https:\/\/smi-spec.io\/","title":"","type":null},"content":[{"type":"text","text":"服务网格接口(SMI)"}]},{"type":"text","text":"，以及2019年9月发布的Maesh(现在称为Traefik mesh)和Kuma。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"即使是在独角兽之外出现的服务网格，如HashiCorp的"},{"type":"link","attrs":{"href":"https:\/\/www.consul.io\/","title":"","type":null},"content":[{"type":"text","text":"Consul"}]},{"type":"text","text":"，也从上述技术中获得的灵感，通常旨在实现CoreOS创造的“"},{"type":"link","attrs":{"href":"https:\/\/github.com\/linearregression\/GIFEE","title":"","type":null},"content":[{"type":"text","text":"GIFEE"}]},{"type":"text","text":"”概念；针对其他所有人的谷歌基础设施。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"为了深入了解现代服务网格概念的发展历史，"},{"type":"link","attrs":{"href":"https:\/\/philcalcado.com\/","title":"","type":null},"content":[{"type":"text","text":"Phil Calçado"}]},{"type":"text","text":"写了一篇全面的文章“"},{"type":"link","attrs":{"href":"https:\/\/philcalcado.com\/2017\/08\/03\/pattern_service_mesh.html","title":"","type":null},"content":[{"type":"text","text":"模式：服务网格"}]},{"type":"text","text":"”。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格的标准"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"尽管服务网格技术在过去几年里经历了年复一年的重大变革，但服务网格的标准并没有跟上创新的步伐。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"使用服务网格解决方案的主要标准是服务网格接口(SMI)。服务网格接口是Kubernetes上运行的服务网格的规范。它本身并没有实现服务网格，而是定义了一个可以由各种服务网格提供者实现的公共标准。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"SMI API的目标是提供一组公共的、可移植的服务网格 API， Kubernetes用户可以以不可知的方式使用这些API。通过这种方式，人们可以定义使用服务网格技术的应用程序，而无需与任何特定的实现紧密绑定。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"SMI基本上是Kubernetes自定义资源定义(CRD)和扩展API服务器的集合。这些API可以安装到任何Kubernetes集群上，并使用标准工具进行运维。要激活这些API，需要在Kubernetes集群中运行SMI provider 。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"SMI规范既允许终端用户的标准化，也允许服务网格技术提供商的创新。SMI支持灵活性和互操作性，并涵盖了最常见的服务网格功能。当前的"},{"type":"link","attrs":{"href":"https:\/\/github.com\/servicemeshinterface\/smi-spec\/tree\/main\/apis","title":"","type":null},"content":[{"type":"text","text":"规范组件"}]},{"type":"text","text":"主要关注服务网格功能的连接性方面。API规范包括以下内容："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"流量访问控制"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"流量指标"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"流量规格"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"流量分割"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"当前的SMI"},{"type":"link","attrs":{"href":"https:\/\/github.com\/servicemeshinterface\/smi-spec","title":"","type":null},"content":[{"type":"text","text":"生态系统"}]},{"type":"text","text":"广泛包括Istio， Linkerd， Consul Connect， Gloo mesh等服务网格。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"SMI规范接受"},{"type":"link","attrs":{"href":"http:\/\/www.apache.org\/licenses\/","title":"","type":null},"content":[{"type":"text","text":"Apache License Version 2.0"}]},{"type":"text","text":"的许可。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"如果您想了解更多关于SMI规范及其API的细节，请查看以下链接。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/github.com\/servicemeshinterface\/smi-spec\/blob\/main\/SPEC_LATEST_STABLE.md","title":"","type":null},"content":[{"type":"text","text":"核心规范"}]},{"type":"text","text":"(当前版本：0.6.0)"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/github.com\/servicemeshinterface\/smi-spec","title":"","type":null},"content":[{"type":"text","text":"规范Github"}]},{"type":"link","attrs":{"href":"https:\/\/github.com\/servicemeshinterface\/smi-spec","title":"","type":null},"content":[{"type":"text","text":"项目"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/github.com\/servicemeshinterface\/smi-spec\/blob\/main\/CONTRIBUTING.md","title":"","type":null},"content":[{"type":"text","text":"如何做出贡献"}]}]}]}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"服务网格基准"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/smp-spec.io\/","title":"","type":null},"content":[{"type":"text","text":"服务网格性能"}]},{"type":"text","text":"是一个用于捕获基础设施容量、服务Mesh配置和工作负载元数据细节的标准。SMP规范用于捕获以下细节："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"环境和基础设施细节"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"节点的数量和大小，协调器"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格及其配置"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"工作负载\/应用程序细节"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"描述性能的统计分析"}]}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"来自Linkerd团队的William Morgan"},{"type":"link","attrs":{"href":"https:\/\/linkerd.io\/2021\/05\/27\/linkerd-vs-istio-benchmarks\/","title":"","type":null},"content":[{"type":"text","text":"写了一篇"}]},{"type":"text","text":"关于对Linkerd和Istio性能进行基准测试的文章。还有一篇2019年的"},{"type":"link","attrs":{"href":"https:\/\/istio.io\/latest\/blog\/2019\/performance-best-practices\/","title":"","type":null},"content":[{"type":"text","text":"文章"}]},{"type":"text","text":"是关于Istio对服务网格性能进行基准测试的最佳实践。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"重点是要记住，就像任何其他性能基准一样，您不应该把太多的精力放在任何外部发布的文章上，特别是产品供应商发布的。您应该在服务器环境中设计并执行自己的性能测试，以验证哪些特定产品适合你的应用程序的业务和非功能性需求。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"探索服务网格(可能)的未来"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/profile\/Kasun-Indrasiri\/","title":"","type":null},"content":[{"type":"text","text":"Kasun Indrasiri"}]},{"type":"text","text":"探讨了“"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/service-mesh-event-driven-messaging\/","title":"","type":null},"content":[{"type":"text","text":"使用服务网格进行事件驱动消息传递的潜力"}]},{"type":"text","text":"”，其中他讨论了在服务网格中实现消息传递支持的两种主要体系结构模式：协议代理边车和HTTP桥接边车。在服务网格社区中，这是一个活跃的开发领域，"},{"type":"link","attrs":{"href":"https:\/\/github.com\/envoyproxy\/envoy\/issues\/2852","title":"","type":null},"content":[{"type":"text","text":"Envoy致力于支持Apache Kafka"}]},{"type":"text","text":"的努力吸引了相当多的关注。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Christian Posta之前曾在“"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/service-mesh-api-federating\/","title":"","type":null},"content":[{"type":"text","text":"统一标准的服务网格API"}]},{"type":"text","text":"”中写过关于服务网格使用标准化的尝试。本文还讨论了2019年由微软和KubeCon EU合作伙伴宣布的"},{"type":"link","attrs":{"href":"https:\/\/cloudblogs.microsoft.com\/opensource\/2019\/05\/21\/service-mesh-interface-smi-release\/","title":"","type":null},"content":[{"type":"text","text":"服务网格接口(SMI)"}]},{"type":"text","text":"。SMI定义了一组通用和可移植的API，旨在为开发人员提供跨不同服务网格技术(包括Istio、Linkerd和Consul Connect)的互操作性。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"将服务网格与平台结构集成的主题可以进一步分为两个子主题。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"第一个，正在进行的工作是减少由服务网格数据面板引入的网络开销。这包括"},{"type":"link","attrs":{"href":"https:\/\/www.dpdk.org\/","title":"","type":null},"content":[{"type":"text","text":"数据面板开发工具包"}]},{"type":"text","text":"(DPDK)，它是一个"},{"type":"link","attrs":{"href":"https:\/\/www.linuxjournal.com\/content\/userspace-networking-dpdk","title":"","type":null},"content":[{"type":"text","text":"用户空间应用程序"}]},{"type":"text","text":"，“绕过Linux内核网络堆栈的厚重层次，直接与网络硬件对话。”"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/news\/2018\/03\/cilium-linux-bpf\/","title":"","type":null},"content":[{"type":"text","text":"Cilium团队"}]},{"type":"text","text":"也有一个基于Linux的BPF解决方案，它在Linux内核中利用了扩展的"},{"type":"link","attrs":{"href":"https:\/\/cilium.io\/blog\/istio\/","title":"","type":null},"content":[{"type":"text","text":"伯克利包过滤(eBPF)功能"}]},{"type":"text","text":"，以实现“非常高效的网络、策略执行和负载平衡功能”。另一个团队正在用"},{"type":"link","attrs":{"href":"https:\/\/github.com\/networkservicemesh\/networkservicemesh\/","title":"","type":null},"content":[{"type":"text","text":"网络服务网格"}]},{"type":"text","text":"将服务网格的概念映射到L2\/L3有效负载，试图“以云本地的方式重新想象网络功能虚拟化(NFV)”。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"第二个，将服务网格与公共云平台更紧密地集成的多个举措，如"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/news\/2019\/01\/aws-app-mesh\/","title":"","type":null},"content":[{"type":"text","text":"AWS App Mesh"}]},{"type":"text","text":"、"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/news\/2019\/04\/google-traffic-director\/","title":"","type":null},"content":[{"type":"text","text":"GCP Traffic Director"}]},{"type":"text","text":"和"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/azure-service-fabric-mesh\/","title":"","type":null},"content":[{"type":"text","text":"Azure service Fabric Mesh"}]},{"type":"text","text":"的引入。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Buoyant团队正在为服务网格技术开发有效的以人为中心的控制面板。他们最近发布了 "},{"type":"link","attrs":{"href":"https:\/\/buoyant.io\/cloud\/","title":"","type":null},"content":[{"type":"text","text":"Buoyant Cloud"}]},{"type":"text","text":"，这是一款基于saas的“团队控制平台”，面向运维Kubernetes的平台团队。下面一节将对此产品进行更详细的讨论。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"自去年以来，在服务网格领域也出现了一些创新。让我们来看看这些创新。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"多云、多集群、多租户服务网格"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"近年来，不同组织对云的采用已经从单一的云解决方案(私有或公有)转变为基于多个不同供应商(AWS、谷歌、Microsoft Azure等)支持的多云(私有、公有和混合)的新基础设施。此外，支持不同工作负载(事务性、批处理和流)的需求对于实现统一的云架构至关重要。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"这些业务和非功能需求反过来又导致需要在异构基础设施(裸机、虚拟机和Kubernetes)中部署服务网格解决方案。服务网格体系结构需要进行相应的转换，以支持这些不同的工作负载和基础设施。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"[Kuma](http:\/\/ Buoyant Cloud)等技术支持多网格控制面板，使业务应用程序能够在多集群和多云服务网格环境中工作。这些解决方案抽象了跨多个区域的服务网格策略的同步以及跨这些区域的服务连接(和服务发现)。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"多集群服务网格技术的另一个新兴趋势是需要从边缘计算层(物联网设备)到网格层的应用\/服务连接。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"媒体服务网格"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"由思科系统公司开发的"},{"type":"link","attrs":{"href":"https:\/\/www.ciscotechblog.com\/blog\/introducing-media-streaming-mesh\/","title":"","type":null},"content":[{"type":"text","text":"媒体流网格"}]},{"type":"text","text":"或媒体服务网格，在Kubernetes云平台上使用服务网格技术，用于编排实时应用程序，如多人游戏、多方视频会议或CCTV流媒体。这些应用程序正越来越多地从单片应用程序转向微服务体系结构。服务网格可以通过提供负载平衡、加密和可观察性等功能来帮助应用程序。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"混沌网格"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/chaos-mesh.org\/","title":"","type":null},"content":[{"type":"text","text":"混沌网格"}]},{"type":"text","text":"是"},{"type":"link","attrs":{"href":"https:\/\/community.cncf.io\/chaos-mesh-community\/","title":"","type":null},"content":[{"type":"text","text":"一个由CNCF托管的项目"}]},{"type":"text","text":"，是一个用于Kubernetes托管应用程序的开源云原生混沌工程平台。虽然混沌网格不是一个直接的服务网格实现，但它通过将错误注入行为编排到应用程序中来实现混沌工程实验。故障注入是服务网格技术的关键功能之一。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"混沌网格隐藏了底层的实现细节，因此应用程序开发人员可以专注于实际的混沌实验。混沌网格可以与服务网格一起使用。检出这个"},{"type":"link","attrs":{"href":"https:\/\/github.com\/sergioarmgpl\/operating-systems-usac-course\/blob\/master\/lang\/en\/projects\/project1v3\/project1.md","title":"","type":null},"content":[{"type":"text","text":"用例"}]},{"type":"text","text":"，看看团队是如何使用Linkerd和混沌来为他们的项目进行混沌实验的。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"服务网格即服务"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"一些服务网格供应商，如Buoyant，正在提供托管服务网格或“服务网格即服务”解决方案。今年早些时候，Buoyant"},{"type":"link","attrs":{"href":"https:\/\/buoyant.io\/newsroom\/buoyant-cloud-offers-managed-service-mesh\/","title":"","type":null},"content":[{"type":"text","text":"发布"}]},{"type":"text","text":"了一个名为"},{"type":"link","attrs":{"href":"http:\/\/buoyant.io\/cloud","title":"","type":null},"content":[{"type":"text","text":"Buoyant Cloud"}]},{"type":"text","text":"的SaaS应用的公开测试版，该应用允许客户组织利用托管服务网格和Linkerd服务网格的随需支持特性。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Buoyant Cloud解决方案提供的一些功能包括："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"Linkerd数据面板和控制面板健康的自动跟踪"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"管理Kubernetes平台上跨pod、代理和集群的服务网格生命周期和版本"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"以SRE为重点的工具，包括服务水平目标(SLO)、工作负载黄金度量跟踪和变更跟踪"}]}]}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"网络服务网格(NSM)，"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"网络服务网格("},{"type":"link","attrs":{"href":"https:\/\/networkservicemesh.io\/","title":"","type":null},"content":[{"type":"text","text":"NSM"}]},{"type":"text","text":")，另一个云本地计算基础沙箱项目，提供了一个混合的、多云的IP服务网格。NSM支持诸如网络服务连接性、安全性和可观察性等功能，这些都是服务网格的核心特性。NSM与现有的容器网络接口("},{"type":"link","attrs":{"href":"https:\/\/github.com\/containernetworking\/cni","title":"","type":null},"content":[{"type":"text","text":"CNI"}]},{"type":"text","text":")实现一起工作。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"服务网格扩展"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格扩展是另一个有很多创新的领域。近期服务网格扩展的发展包括："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"增强的身份管理，以保护微服务连接，包括自定义证书颁发插件"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"自适应路由特性，以提高服务的可用性和可伸缩性"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"加强边车代理"}]}]}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"服务网格运维"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"采用服务网格的另一个重要领域是服务网格生命周期的运维端。运维方面——比如配置多集群功能和将Kubernetes工作负载连接到虚拟机基础架构上的服务器，以及用于管理多集群服务网格安装中的所有特性和API的开发者门户，将在服务网格解决方案的总体部署和生产支持中发挥重要作用。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"常见问题解答"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"什么是服务网格?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格是一种管理分布式(潜在的基于微服务的)软件系统中所有服务到服务(东-西)流量的技术。它既提供以业务为中心的功能性操作(如路由)，也提供非功能性支持(如执行安全策略、服务质量和速率限制)。它通常(尽管不是唯一的)使用边车代理实现，所有服务都通过边车代理进行通信。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"服务网格与API网关有何不同?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"服务网格的有关定义，请参见上文。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"另一方面，API网关管理进入集群的所有入口(南-北)流量，并为跨功能通信需求提供额外支持。它充当进入系统的单一入口点，并允许多个API或服务内聚，向用户提供一致的体验。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"如果我正在部署微服务，我是否需要服务网格?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"不一定。服务网格增加了技术栈的运维复杂性，因此通常只在组织在扩展服务到服务通信方面遇到困难，或者有特定的用例需要解决时才部署。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"我是否需要服务网格来实现微服务的服务发现?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"不用。服务网格提供的是一种实现服务发现的方法。还有包括特定于语言的库(如Ribbon和Eureka或Finagle)的其他解决方案。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"服务网格是否增加了服务到服务通信的开销\/延迟?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"是的，当服务与另一个服务通信时，服务网格至少会增加两个额外的网络跳数(第一个是来自处理源出站连接的代理，第二个是来自处理目的地入站连接的代理)。但是，这种额外的网络跳通常发生在"},{"type":"link","attrs":{"href":"https:\/\/en.wikipedia.org\/wiki\/Localhost","title":"","type":null},"content":[{"type":"text","text":"本地主机或环回网络接口"}]},{"type":"text","text":"上，并且只增加少量延迟(量级为毫秒)。对服务网格进行分析和评估时，应试验和理解这对于目标用例来说是否构成问题。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"服务网格不应该是Kubernetes或部署应用程序的“云本地平台”的一部分吧?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"很可能。对于在云本地平台组件中保持关注点分离(例如，Kubernetes负责提供容器编排，而服务网格负责服务到服务的通信)存在争议。然而，将服务网状功能推进到现代的平台即服务(PaaS)产品中的工作正在进行中。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"如何实现、部署或推出服务网格?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"最好的方法是分析各种服务网格产品(见上文)，并遵循特定于所选网格的实现指南。一般来说，最好是与所有涉众一起协作，并将所有新技术逐步部署到生产中。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"我可以建立自己的服务网格吗?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"当然，但更重要的问题是，你应该这样做吗?建立服务网是您组织的核心竞争力吗?你能否以更有效的方式为客户提供价值?您是否也致力于维护自己的网格，为安全问题打补丁，并不断更新它以利用新技术?随着开放源码和商业服务网格产品的出现，使用现有的解决方案可能会更有效。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"在软件交付组织中，哪个团队拥有服务网格?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"通常情况下，平台或运营团队拥有服务网格，以及Kubernetes和连续交付管道基础设施。然而，将由开发人员配置服务网格参数，因此两个团队应该紧密合作。许多组织都在效仿云计算先锋，如Netflix、Spotify和谷歌，并创建内部平台团队，为"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/news\/2018\/06\/netflix-full-cycle-developers\/","title":"","type":null},"content":[{"type":"text","text":"全周期产品开发团队"}]},{"type":"text","text":"提供工具和服务。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"Envoy是服务网格吗?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"不。Envoy是一个云原生代理，最初是由Lyft团队设计和构建的。Envoy通常被用作使用服务网格的数据面板。然而，为了被认为是服务网格，Envoy必须与一个控制面板结合使用，以使这一系列技术成为服务网格。控制面板可以像集中式配置文件存储库和度量收集器那样简单，也可以像Istio那样全面\/复杂。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"“Istio”和“服务网格”可以互换使用吗?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"不行。Istio是一种服务网格。由于Istio的流行，当服务网格类别出现时，一些地方会把Istio和服务网格相提并论。这种问题并不是服务网格所独有的，Docker和容器技术也面临同样的挑战。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"我应该使用哪种服务网格?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"这个问题没有唯一解。工程师必须了解他们当前的需求，以及他们的实现团队可用的技能、资源和时间。你可以先看看上面所列的服务网格比较链接，它们是你开启探索的一个良好的起点，但我们强烈建议组织至少试验两个网格，以便了解哪些产品、技术和工作流最适合他们。"}]},{"type":"heading","attrs":{"align":null,"level":3},"content":[{"type":"text","text":"我可以使用Kubernetes之外的服务网格吗?"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"当然。许多服务网格允许在各种基础设施上安装和管理数据面板代理和相关的控制面板。最著名的例子是"},{"type":"link","attrs":{"href":"https:\/\/www.hashicorp.com\/resources\/consul-service-mesh-kubernetes-and-beyond","title":"","type":null},"content":[{"type":"text","text":"HashiCorp的Consul"}]},{"type":"text","text":"，Istio也被用于Cloud Foundry。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"额外的资源"}]},{"type":"bulletedlist","content":[{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/servicemesh\/","title":"","type":null},"content":[{"type":"text","text":"InfoQ 服务网格主页"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/minibooks\/service-mesh","title":"","type":null},"content":[{"type":"text","text":"InfoQ eMag-"}]},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/minibooks\/service-mesh","title":"","type":null},"content":[{"type":"text","text":"服务网格："}]},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/minibooks\/service-mesh","title":"","type":null},"content":[{"type":"text","text":"过去、现在和未来"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/servicemesh.io","title":"","type":null},"content":[{"type":"text","text":"服务网格"}]},{"type":"link","attrs":{"href":"https:\/\/servicemesh.io","title":"","type":null},"content":[{"type":"text","text":"："}]},{"type":"link","attrs":{"href":"https:\/\/servicemesh.io","title":"","type":null},"content":[{"type":"text","text":"关于这项世界上最被过度炒作的技术，每个软件工程师都需要知道什么"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/servicemesh.es\/","title":"","type":null},"content":[{"type":"text","text":"服务网格比较"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/softwareengineeringdaily.com\/2020\/01\/07\/service-meshes\/","title":"","type":null},"content":[{"type":"text","text":"服务网格"}]}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/cloud-native-architecture-adoption-part3","title":"","type":null},"content":[{"type":"text","text":"云本地架构采用，第3部分"}]},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/cloud-native-architecture-adoption-part3","title":"","type":null},"content":[{"type":"text","text":"："}]},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/cloud-native-architecture-adoption-part3","title":"","type":null},"content":[{"type":"text","text":"服务编排和服务网格"}]}]}]}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"术语表"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"API网关"},{"type":"text","text":"：管理进入集群的所有入口(南-北)流量，并为跨功能通信需求提供额外支持。它充当进入系统的单一入口点，并允许多个API或服务内聚并向用户提供统一的体验。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Consul："},{"type":"text","text":" HashiCorp的基于Go的服务网格。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"容器化"},{"type":"text","text":"：容器是一个标准的软件单元，它将代码及其所有依赖项打包，以便在一个计算环境运行的应用程序快速可靠地到另一个环境中运行。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"控制面板"},{"type":"text","text":"：获取数据面板(代理)的所有单独实例，并将它们转换为一个可由运维人员可视化和控制的分布式系统。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"断路器"},{"type":"text","text":"：处理连接到远程服务时的故障或超时。有助于提高应用程序的稳定性和弹性。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"数据面板"},{"type":"text","text":"：一个代理，有条件地转换、转发和观察每个来自服务网络端点的网络数据包。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Docker"},{"type":"text","text":"： Docker容器映像是一个轻量级的、独立的、可执行的软件包，包含了运行应用程序所需的所有东西：代码、运行环境、系统工具、系统库和设置。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"东-西流量"},{"type":"text","text":"：数据中心、网络或Kubernetes集群内的网络流量。传统的网络图是由服务到服务(数据中心间)流量从左到右(东到西)绘制的。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Envoy Proxy"},{"type":"text","text":"：开源边缘和服务代理，专为云本地应用设计。Envoy通常用作服务网格实现中的数据面板。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"入口流量"},{"type":"text","text":"：来自数据中心、网络或Kubernetes集群外部的网络流量。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Istio"},{"type":"text","text":"：基于c++(数据面板)和Go(控制面板)的服务网格，最初由谷歌和IBM与Lyft的Envoy团队合作创建。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Kubernetes"},{"type":"text","text":"：起源于谷歌的由cncf托管的容器编排和调度框架。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Kuma"},{"type":"text","text":"：一款来自于Kong的基于Go的服务网格。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Linkerd"},{"type":"text","text":"：一个由Rust(数据面板)和Go(控制面板)驱动的服务网格，源自Twitter早期基于jvm的通信框架。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Maesh"},{"type":"text","text":"： A Go-based 服务网格 from Containous， the maintainers of the Traefik API gateway."}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Maesh"},{"type":"text","text":"：来自Containous的基于go的服务网格，它是Traefik API网关的维护者。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"MOSN：蚂蚁金服团队的基于Go的代理，实现了(Envoy) xDS API。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"南-北流量"},{"type":"text","text":"：进入数据中心、网络或Kubernetes集群的网络流量。传统的网络图是这样绘制的：入口流量由页面的顶部进入数据中心，然后向下(从北到南)进入网络。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"代理"},{"type":"text","text":"：在端点组件之间充当中介的软件系统。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"分段"},{"type":"text","text":"：将一个网络或集群划分为多个子网络。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"服务网格"},{"type":"text","text":"：管理分布式(潜在的基于微服务的)软件系统中所有服务到服务(东-西)的流量。它既提供功能性操作(如路由)，也提供非功能性支持(如执行安全策略、服务质量和速率限制)。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"服务网格接口(SMI)"},{"type":"text","text":"：部署到Kubernetes上的服务网格的标准接口。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"服务网格策略"},{"type":"text","text":"：一个关于一组服务\/端点如何相互之间以及如何与其他网络端点通信的规范。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"边车"},{"type":"text","text":"： 一种部署模式，在这种模式中，附加的流程、服务或容器与现有的服务一起部署(想象一下摩托车的跨斗)。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Single pane of glass"},{"type":"text","text":"：一个UI或管理控制台，在一个统一的视图中显示来自于多个来源的数据。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"流量整形"},{"type":"text","text":"：修改网络中的流量，如限速、减载等。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"流量迁移"},{"type":"text","text":"：将流量从一个位置迁移到另一个位置。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"流量分割：允许用户在各种服务之间增量地分配流量百分比。由客户端(如入口控制器或服务网格边车)使用，将出站流量分割到不同的目的地。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"现代软件架构师的角色在不断变化。订阅InfoQ的《"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/architects-newsletter\/?utm_source=text&utm_medium=end&utm_campaign=pillarpage","title":"","type":null},"content":[{"type":"text","text":"软件架构师通讯"}]},{"type":"text","text":"》吧，保持在时代的前沿。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"作者简介："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"Srini Penchikala"},{"type":"text","text":"是德克萨斯州奥斯汀市的一位高级IT架构师。他在软件架构、设计和开发方面有超过25年的经验，目前专注于云本地架构、微服务和服务网格、云数据管道和持续交付。Penchikala编写了《使用Apache Spark进行大数据处理》，并参与编写了Manning的《"},{"type":"link","attrs":{"href":"http:\/\/www.manning.com\/SpringRooinAction","title":"","type":null},"content":[{"type":"text","text":"Spring Roo in Action"}]},{"type":"text","text":"》。他经常在大会上发表演讲，是一名大数据培训师，并在各种技术网站上发表过一些文章。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"原文链接："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/service-mesh-ultimate-guide-2e\/","title":"","type":null},"content":[{"type":"text","text":"Service Mesh Ultimate Guide - Second Edition: Next Generation Microservices Development"}]}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"译者简介："},{"type":"text","text":" 冬雨，小小技术宅一枚，从事研发过程改进及质量改进方面的工作，关注编程、软件工程、敏捷、DevOps、云计算等领域，非常乐意将国外新鲜的IT资讯和深度技术文章翻译分享给大家，已翻译出版《深入敏捷测试》、《持续交付实战》。"}]}]}