深入浅出云原生架构（三）：服务编排和服务网格

{"type":"doc","content":[{"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":"第一部分"}]},{"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":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/cloud-native-architecture-adoption-part2\/","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":"微服务架构带来了不少好处，但也带来了一些挑战。我们会将这些挑战视为架构机会，探讨如何通过服务编排来克服它们。"}]},{"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":"本文讨论的设计模式适用于像AWS、VMware Tanzu Application Service（之前的Pivotal Cloud Foundry）或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":"在不少组织中，Kubernetes已经成为事实上的云平台。服务网格框架提供了一种让我们得以在云上充分利用Kubernetes的卓越方法，不管你现在已经在使用Kubernetes，还是计划将来对它做些研究。本文将介绍服务网格如何帮助我们管理生产环境的服务部署。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1box-1-business-logic-1630320217028.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"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":"挑战1：筒仓式开发"}]},{"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":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1Figure-1-siloed-development-example-updated-1630320217028.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"图1、筒仓式开发示例"}]},{"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":"这个例子中有两个客户端应用程序（App 1和App2）和三个业务服务（Service 1、Service 2和Service 3）。App 1和Service 1以及Service 2交互。App 2只和Service 2交互。Service 2还会与Service 3交互。"}]},{"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":"让我们仔细分析下App 1，看看这个应用程序里发生了什么。"}]},{"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":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1Figure-2-Application-and-service-functionality-under-the-hood-1630320217028.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"图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":"上面的示例应用程序包含了关键的业务逻辑，也混合了非业务逻辑任务，所有功能都嵌在了应用程序代码里："}]},{"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","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":"8个功能中仅有1个是应用特有的逻辑，其他7个功能不应该和应用程序逻辑耦合在一起。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1box-2-architecture-artifacts-1630320217028.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"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":"从Service 1、2、3中可以看到类似的模式。每个服务的业务逻辑都混合了非功能性的平台任务，和我们前面看到的一样，它们不应该包含在服务里。我们看到了一些共有的非功能性服务，如身份验证、授权、客户通知等。还有一些所有业务应用程序共有的平台服务，如路由、服务发现、服务监控和跟踪，这些服务托管在云平台上。当我们仔细查看每个组件时，这个包含2个应用、3个服务的分布式系统的简单例子似乎看上去就不那么简单了，如下所示："}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1Figure-3-Distributed-systems-example-with-common-functionality-duplicated-in-each-app-and-service-1630320217028.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"图3、分布式系统示例，这些应用和服务之间有一些共有的重复的功能"}]},{"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":"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:\/\/spring.io\/projects\/spring-cloud-gateway","title":"","type":null},"content":[{"type":"text","text":"Spring Cloud Gateway"}]},{"type":"text","text":"和"},{"type":"link","attrs":{"href":"https:\/\/zipkin.io\/","title":"","type":null},"content":[{"type":"text","text":"Zipkin"}]},{"type":"text","text":"或"},{"type":"link","attrs":{"href":"https:\/\/www.jaegertracing.io\/","title":"","type":null},"content":[{"type":"text","text":"Jaeger"}]},{"type":"text","text":"实现路由和跟踪。底层技术的任何升级都需要修改应用程序，重新构建和部署，导致停机和中断。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1box-3-business-logic-common-functions-updated-1630327861021.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"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":"由于网络越来越稳定和可靠，可以开始将“进程内”调用（如图3所示）转换为“通过网络”通信了。"}]},{"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":"对于嵌入在每个应用程序里的代码，我们的处理方式是将每个公共功能封装到自己的服务里，并托管在云中一个中央服务器（也许是VM）上或容器中。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1Figure-4-Common-functionality-encapsulated-in-independent-microservices-1630327861021.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"图4、封装在独立微服务中的公共功能"}]},{"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":"当应用需要执行公共功能时，客户端应用程序就会调用这些远程服务。如图4所示，公共逻辑不再嵌入到每个应用程序或业务服务中。"}]},{"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:\/\/12factor.net\/","title":"","type":null},"content":[{"type":"text","text":"12要素应用"}]},{"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":"我们可以使用开源框架来开发这些公共服务，如用于Java应用程序的"},{"type":"link","attrs":{"href":"https:\/\/spring.io\/projects\/spring-boot","title":"","type":null},"content":[{"type":"text","text":"Spring Boot"}]},{"type":"text","text":"和"},{"type":"link","attrs":{"href":"https:\/\/spring.io\/projects\/spring-cloud","title":"","type":null},"content":[{"type":"text","text":"Spring Cloud"}]},{"type":"text","text":"，用于ASP.NET应用程序的"},{"type":"link","attrs":{"href":"https:\/\/docs.microsoft.com\/en-us\/aspnet\/core\/fundamentals\/middleware\/?view=aspnetcore-5.0","title":"","type":null},"content":[{"type":"text","text":"Asp.Net Core"}]},{"type":"link","attrs":{"href":"https:\/\/docs.microsoft.com\/en-us\/aspnet\/core\/fundamentals\/middleware\/?view=aspnetcore-5.0","title":"","type":null},"content":[{"type":"text","text":"中间件"}]},{"type":"text","text":"。在理想情况下，这些服务都是12要素应用程序，都可以比较容易地部署到任何云平台上。在生产环境中管理和监控也比较容易。"}]},{"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":"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":"link","attrs":{"href":"https:\/\/aws.amazon.com\/","title":"","type":null},"content":[{"type":"text","text":"AWS"}]},{"type":"text","text":"、"},{"type":"link","attrs":{"href":"https:\/\/azure.microsoft.com\/en-us\/","title":"","type":null},"content":[{"type":"text","text":"Azure"}]},{"type":"text","text":"、"},{"type":"link","attrs":{"href":"https:\/\/kubernetes.io\/","title":"","type":null},"content":[{"type":"text","text":"Kubernetes"}]},{"type":"text","text":"或"},{"type":"link","attrs":{"href":"https:\/\/tanzu.vmware.com\/application-service","title":"","type":null},"content":[{"type":"text","text":"VMWare Tanzu Application Service"}]},{"type":"text","text":"，之前叫Pivotal Cloud Foundry）。这些平台对自动扩展、监控、快捷部署等特性提供了良好的支持。"}]},{"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":"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":"挑战2：应用与服务以及服务与服务之间的通信"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"随着我们将大型应用程序分解成细粒度的服务，部署的组件总量在增加，这使得这些组件之间的交互变得越来越复杂。图5说明了这种复杂性。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1Figure-5-Application-to-service-communication-challenges-1630328963068.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"图5、应用程序与服务之间通信的挑战"}]},{"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":"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":"从图5服务之间的通信可以看出，不同的服务之间仍然是紧耦合的，当整个系统变慢或是出现中断时，还是很难准确定位哪个服务有问题。"}]},{"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":"我们可能会想，其他采用微服务的公司同样也会面临交互模型复杂这样的挑战。他们确实遇到了。像Netflix、Amazon、Twitter这些公司都经历过同样的挑战，原因是任何应用程序或服务调用其他的服务时缺少一个有效的服务通信模型或治理流程。正如"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/articles\/cloud-native-architecture-adoption-part2\/#theCommentsSection","title":"","type":null},"content":[{"type":"text","text":"本系列文章第二部分"}]},{"type":"text","text":"指出的那样，这种架构挑战在行业里相当普遍，它被定义成一个反模式“"},{"type":"link","attrs":{"href":"https:\/\/mrtortoise.github.io\/architecture\/lean\/design\/patterns\/ddd\/2018\/03\/18\/deathstar-architecture.html","title":"","type":null},"content":[{"type":"text","text":"死星架构"}]},{"type":"text","text":"“。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1box-4-death-start-architecture-1630328963068.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"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}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1Figure-6-Service-orchestration-improved-service-to-service-interaction-1630328963068.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"图6、利用服务编排改进服务间通信"}]},{"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":"在图6所示的服务编排模型中，我们对于公共服务的处理还是像之前的架构一样，在客户端应用程序之外，它们会单独部署，有自己的生命周期和扩展性要求。"}]},{"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":"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":"这些策略可以是安全相关的，如身份验证和授权，可以是SLA相关的，如服务重试和断路器规则，还可以是可观测性和监控相关的。"}]}]},{"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":"客户端应用程序可以是Web应用程序、移动App、IoT设备或其他服务。"}]}]},{"type":"listitem","attrs":{"listStyle":null},"content":[{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null},"content":[{"type":"text","text":"后端服务可以是单体应用、微服务或"},{"type":"link","attrs":{"href":"https:\/\/aws.amazon.com\/lambda\/","title":"","type":null},"content":[{"type":"text","text":"无服务器函数"}]},{"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":"在服务编排架构中，消费者应用程序团队只需要关注用户界面和应用程序特有的服务，保护业务逻辑和IP不受技术变化和公共基础能力（非应用程序特有的能力）的影响。所有的公共服务——不管是业务服务，非功能性服务，还是平台服务——都托管在云平台上供路由服务调用，路由服务充当了服务编排器的角色。"}]},{"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":"如图7所示，公共服务中使用的所有技术和框架完全是从消费者应用程序中抽象出来的。"}]},{"type":"heading","attrs":{"align":null,"level":2},"content":[{"type":"text","text":"技术抽象"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1Figure-7-Service-orchestrator-based-solutions-abstract-technologies-from-client-applications-1630329480308.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"图7、基于服务编排的解决方案从客户端应用程序中抽象出来的技术"}]},{"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":"使用图7所示的中心化服务编排器，客户端应用程序不需要知道这些技术中的任何一项。此外，这些技术中的任何一项升级都不会影响客户端应用。"}]},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1box-5-seamless-updates-1630329480308.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"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":"截至目前，我们前面讨论的3种不同的架构（传统的分布式系统、基于微服务的架构和基于服务编排的应用程序）都面临一些挑战。现在，让我们探讨下两种新兴的云原生设计模式："},{"type":"link","attrs":{"href":"https:\/\/philcalcado.com\/2017\/08\/03\/pattern_service_mesh.html","title":"","type":null},"content":[{"type":"text","text":"服务网格"}]},{"type":"text","text":"和挎斗（sidecar）。"}]},{"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":"在本文最后，我们将探讨基于服务网格和挎斗设计模式的架构模型。Kubernetes对挎斗模式提供了开箱即用的支持，所以这个模型很适合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":"该架构模型如图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":"挎斗容器（数据平面的一部分）会在运行时自动注入业务服务。这些挎斗代理会执行在控制平面中定义的策略，并将其复制到数据平面。"}]},{"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":"paragraph","attrs":{"indent":0,"number":0,"align":null,"origin":null}},{"type":"image","attrs":{"src":"https:\/\/imgopt.infoq.com\/fit-in\/625x1000\/filters:quality(80)\/filters:no_upscale()\/articles\/cloud-native-architecture-adoption-part3\/en\/resources\/1Figure-8-Service-mesh-and-sidecars-for-Kubernetes-hosted-apps-1630329480308.jpg","alt":null,"title":null,"style":[{"key":"width","value":"75%"},{"key":"bordertype","value":"none"}],"href":null,"fromPaste":true,"pastePass":true}},{"type":"paragraph","attrs":{"indent":0,"number":0,"align":"center","origin":null},"content":[{"type":"text","marks":[{"type":"strong"}],"text":"图8、面向Kubernetes托管应用的服务网格和挎斗"}]},{"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","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":"服务间身份验证（mTLS）"}]}]},{"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":"用户身份验证（JSON Web Tokens）"}]}]},{"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":"监控"}]}]},{"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":"link","attrs":{"href":"https:\/\/istio.io\/","title":"","type":null},"content":[{"type":"text","text":"Istio"}]},{"type":"text","text":"、"},{"type":"link","attrs":{"href":"https:\/\/linkerd.io\/","title":"","type":null},"content":[{"type":"text","text":"Linkerd"}]},{"type":"text","text":"、"},{"type":"link","attrs":{"href":"https:\/\/www.consul.io\/docs\/connect","title":"","type":null},"content":[{"type":"text","text":"Consul Connect"}]},{"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\/minibooks\/service-mesh-guide\/","title":"","type":null},"content":[{"type":"text","text":"InfoQ迷你书《服务网格终极指南》"}]},{"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":"微服务之间的交互和通信有多种不同的实现方式。服务编排可以通过将API网关作为架构核心组件来实现。如果我们需要的能力超出了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":"在云原生应用程序架构中，一件很重要的事情是设计层次之间的交互，包括如何在建模工作中把数据、服务和事件作为一等公民。"}]},{"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":"在本系列文章的第4部分中，我们将讨论最后一部分内容：云原生DevOps。我们将看下DevOps实践（CI\/CD、容器华、Kubernetes云平台、微服务和服务编排模式）如何帮助组织上云。"}]},{"type":"heading","attrs":{"align":null,"level":2}},{"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\/articles\/cloud-native-architecture-adoption-part1\/","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-part2\/","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:\/\/philcalcado.com\/2017\/08\/03\/pattern_service_mesh.html","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\/vp-microservices-communication-governance-using-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:\/\/www.infoq.com\/articles\/vp-microservices-orchestration-choreography\/","title":"","type":null},"content":[{"type":"text","text":"服务交互和治理模型：Orchestration vs Choreography"}]}]}]},{"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\/multi-runtime-microservice-architecture\/","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\/presentations\/microservices-factors\/","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:\/\/developers.redhat.com\/books\/introducing-istio-service-mesh-microservices","title":"","type":null},"content":[{"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","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部门的高级IT架构师。他在软件架构、设计和开发方面有超过25年的经验，目前专注于云原生架构、微服务和服务网格、云数据管道和持续交付。Penchikala在组织中是企业云原生服务网格解决方案的共同创建者和首席架构师。 Penchikala写了"},{"type":"link","attrs":{"href":"https:\/\/www.infoq.com\/minibooks\/apache-spark\/","title":"","type":null},"content":[{"type":"text","text":"Big-Data Processing with Apache Spark"}]},{"type":"text","text":"一书，并与人合著了"},{"type":"link","attrs":{"href":"https:\/\/www.manning.com\/books\/spring-roo-in-action","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":"Marcio Esteves"},{"type":"text","text":"是德克萨斯州休斯顿东京海运HCC的应用开发总监，他领导解决方案架构、质量保证和开发团队，协调企业和业务IT部门开展合作，推动通用技术的采用，其重点关注的是创造收入、全球部署、基于云的系统。在此之前，Esteves是通用汽车IT全球制造部的首席架构师，领导架构师和云原生工程师团队，主要负责数字化转型技术，如机器学习、大数据、物联网和人工智能\/云优先的微服务架构。Esteves制定了愿景和战略，并领导了通用汽车企业云原生服务网格解决方案的实施，其中包括供多个关键业务应用程序使用的可自动扩展的微服务。他还担任了位于奥斯汀市中心VertifyData的董事会技术顾问。"}]},{"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\/cloud-native-architecture-adoption-part3\/","title":"","type":null},"content":[{"type":"text","text":"Adoption of Cloud Native Architecture, Part 3: Service Orchestration and Service Mesh"}]}]}]}