archive-gh-me/microservices
1
0
Fork 0
mirror of https://github.com/DocsHome/microservices.git synced 2025-12-08 19:25:13 +00:00
Code Issues Projects Releases Wiki Activity
microservices/_book/2-using-an-api-gateway.html
Oopsguy 41ce752637 testing for new gitbook
2019-07-13 03:00:33 +08:00

1351 lines
206 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE HTML>
<html lang="zh-hans" >
<head>
<meta charset="UTF-8">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<title>2、使用 API 网关 · 微服务：从设计到部署</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge" />
<meta name="description" content="">
<meta name="generator" content="GitBook 3.2.3">
<meta name="author" content="oopsguy.com">
<link rel="stylesheet" href="gitbook/style.css">
<link rel="stylesheet" href="gitbook/gitbook-plugin-splitter/splitter.css">
<link rel="stylesheet" href="gitbook/gitbook-plugin-tbfed-pagefooter/footer.css">
<link rel="stylesheet" href="gitbook/gitbook-plugin-image-captions/image-captions.css">
<link rel="stylesheet" href="gitbook/gitbook-plugin-fontsettings/website.css">
<meta name="HandheldFriendly" content="true"/>
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black">
<link rel="apple-touch-icon-precomposed" sizes="152x152" href="gitbook/images/apple-touch-icon-precomposed-152.png">
<link rel="shortcut icon" href="gitbook/images/favicon.ico" type="image/x-icon">
<link rel="next" href="2-using-an-api-gateway.html" />
<link rel="prev" href="1-introduction-to-microservices.html" />
<style>
@media only screen and (max-width: 640px) {
.book-header .hidden-mobile {
display: none;
}
}
</style>
<script>
window["gitbook-plugin-github-buttons"] = {"repo":"oopsguy/microservices-from-design-to-deployment-chinese","types":["star","watch"],"size":"small"};
</script>
</head>
<body>
<div class="book">
<div class="book-summary">
<nav role="navigation">
<ul class="summary">
<li>
<a href="http://oopsguy.com" target="_blank" class="custom-link">Oopsguy 的博客</a>
</li>
<li>
<a href="https://github.com/oopsguy/microservices-from-design-to-deployment-chinese" target="_blank" class="custom-link">《微服务：从设计到部署》</a>
</li>
<li class="divider"></li>
<li class="chapter " data-level="1.1" data-path="./">
<a href="./">
Introduction
</a>
</li>
<li class="chapter " data-level="1.2" data-path="0-foreword.html">
<a href="0-foreword.html">
0、前言
</a>
</li>
<li class="chapter " data-level="1.3" data-path="1-introduction-to-microservices.html">
<a href="1-introduction-to-microservices.html">
1、微服务简介
</a>
<ul class="articles">
<li class="chapter " data-level="1.3.1" data-path="1-introduction-to-microservices.html">
<a href="1-introduction-to-microservices.html#building-monolithic-applications">
1.1、构建单体应用
</a>
</li>
<li class="chapter " data-level="1.3.2" data-path="1-introduction-to-microservices.html">
<a href="1-introduction-to-microservices.html#marching-toward-monolithic-hell">
1.2、走向单体地狱
</a>
</li>
<li class="chapter " data-level="1.3.3" data-path="1-introduction-to-microservices.html">
<a href="1-introduction-to-microservices.html#tackling-the-complexity">
1.3、微服务-解决复杂问题
</a>
</li>
<li class="chapter " data-level="1.3.4" data-path="1-introduction-to-microservices.html">
<a href="1-introduction-to-microservices.html#the-benefits-of-microservices">
1.4、微服务的优点
</a>
</li>
<li class="chapter " data-level="1.3.5" data-path="1-introduction-to-microservices.html">
<a href="1-introduction-to-microservices.html#the-drawbacks-of-microservices">
1.5、微服务的缺点
</a>
</li>
<li class="chapter " data-level="1.3.6" data-path="1-introduction-to-microservices.html">
<a href="1-introduction-to-microservices.html#summary">
1.6、总结
</a>
</li>
<li class="chapter " data-level="1.3.7" data-path="1-introduction-to-microservices.html">
<a href="1-introduction-to-microservices.html#microservices-in-action">
微服务实战：NGINX Plus 作为反向代理服务器
</a>
</li>
</ul>
</li>
<li class="chapter active" data-level="1.4" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html">
2、使用 API 网关
</a>
<ul class="articles">
<li class="chapter " data-level="1.4.1" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#introduction">
2.1、简介
</a>
</li>
<li class="chapter " data-level="1.4.2" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#direct-client-to-microservice-communication">
2.2、客户端与微服务直接通信
</a>
</li>
<li class="chapter " data-level="1.4.3" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#using-an-api-gateway">
2.3、使用 API 网关
</a>
</li>
<li class="chapter " data-level="1.4.4" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#benefits-and-drawbacks-of-an-api-gateway">
2.4、API 网关的优点与缺点
</a>
</li>
<li class="chapter " data-level="1.4.5" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#implementing-an-api-gateway">
2.5、实施 API 网关
</a>
<ul class="articles">
<li class="chapter " data-level="1.4.5.1" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#performance-and-scalability">
2.5.1、性能与扩展
</a>
</li>
<li class="chapter " data-level="1.4.5.2" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#using-a-reactive-programming-model">
2.5.2、使用响应式编程模型
</a>
</li>
<li class="chapter " data-level="1.4.5.3" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#service-invocation">
2.5.3、服务调用
</a>
</li>
<li class="chapter " data-level="1.4.5.4" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#service-discovery">
2.5.4、服务发现
</a>
</li>
<li class="chapter " data-level="1.4.5.5" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#handling-partial-failures">
2.5.5、处理局部故障
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.4.6" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#summary">
2.6、总结
</a>
</li>
<li class="chapter " data-level="1.4.7" data-path="2-using-an-api-gateway.html">
<a href="2-using-an-api-gateway.html#microservices-in-action">
微服务实战：NGINX Plus 作为 API 网关
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.5" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html">
3、进程间通信
</a>
<ul class="articles">
<li class="chapter " data-level="1.5.1" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#introduction">
3.1、简介
</a>
</li>
<li class="chapter " data-level="1.5.2" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#interaction-styles">
3.2、交互方式
</a>
</li>
<li class="chapter " data-level="1.5.3" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#defining-apis">
3.3、定义 API
</a>
</li>
<li class="chapter " data-level="1.5.4" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#evolving-apis">
3.4、演化 API
</a>
</li>
<li class="chapter " data-level="1.5.5" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#handling-partial-failure">
3.5、处理局部故障
</a>
</li>
<li class="chapter " data-level="1.5.6" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#ipc-technologies">
3.6、IPC 技术
</a>
</li>
<li class="chapter " data-level="1.5.7" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#asynchronous-message-based-communication">
3.7、异步、基于消息的通信
</a>
</li>
<li class="chapter " data-level="1.5.8" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#synchronous-request-response-ipc">
3.8、同步的请求/响应 IPC
</a>
<ul class="articles">
<li class="chapter " data-level="1.5.8.1" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#rest">
3.8.1、REST
</a>
</li>
<li class="chapter " data-level="1.5.8.2" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#thrift">
3.8.2、Thrift
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.5.9" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#message-formats">
3.9、消息格式
</a>
</li>
<li class="chapter " data-level="1.5.10" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#summary">
3.10、总结
</a>
</li>
<li class="chapter " data-level="1.5.11" data-path="3-inter-process-communication.html">
<a href="3-inter-process-communication.html#microservices-in-action">
微服务实战：NGINX 与应用程序架构
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.6" data-path="4-service-discovery.html">
<a href="4-service-discovery.html">
4、服务发现
</a>
<ul class="articles">
<li class="chapter " data-level="1.6.1" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#why-use-service-discovery">
4.1、为何使用服务发现
</a>
</li>
<li class="chapter " data-level="1.6.2" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#the-client-side-discovery-pattern">
4.2、客户端发现模式
</a>
</li>
<li class="chapter " data-level="1.6.3" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#the-server-side-discovery-pattern">
4.3、服务端发现模式
</a>
</li>
<li class="chapter " data-level="1.6.4" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#the-service-registry">
4.4、服务注册中心
</a>
</li>
<li class="chapter " data-level="1.6.5" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#service-registration-options">
4.5、服务注册方式
</a>
</li>
<li class="chapter " data-level="1.6.6" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#the-self-registration-pattern">
4.6、自注册模式
</a>
</li>
<li class="chapter " data-level="1.6.7" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#the-third-party-registration-pattern">
4.7、第三方注册模式
</a>
</li>
<li class="chapter " data-level="1.6.8" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#summary">
4.8、总结
</a>
</li>
<li class="chapter " data-level="1.6.9" data-path="4-service-discovery.html">
<a href="4-service-discovery.html#microservices-in-action">
微服务实战：灵活的 NGINX
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.7" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html">
5、事件驱动数据管理
</a>
<ul class="articles">
<li class="chapter " data-level="1.7.1" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management">
5.1、微服务与分布式数据管理问题
</a>
</li>
<li class="chapter " data-level="1.7.2" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html#event-driven-architecture">
5.2、事件驱动架构
</a>
</li>
<li class="chapter " data-level="1.7.3" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html#achieving-atomicity">
5.3、实现原子性
</a>
</li>
<li class="chapter " data-level="1.7.4" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions">
5.4、使用本地事务发布事件
</a>
</li>
<li class="chapter " data-level="1.7.5" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log">
5.5、挖掘数据库事务日志
</a>
</li>
<li class="chapter " data-level="1.7.6" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html#using-event-sourcing">
5.6、使用事件溯源
</a>
</li>
<li class="chapter " data-level="1.7.7" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html#summary">
5.7、总结
</a>
</li>
<li class="chapter " data-level="1.7.8" data-path="5-event-driven-data-management-for-microservices.html">
<a href="5-event-driven-data-management-for-microservices.html#microservices-in-action">
微服务实战：NGINX 与存储优化
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.8" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html">
6、选择部署策略
</a>
<ul class="articles">
<li class="chapter " data-level="1.8.1" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html#motivations">
6.1、动机
</a>
</li>
<li class="chapter " data-level="1.8.2" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html#multiple-service-instances-per-host-pattern">
6.2、单主机多服务实例模式
</a>
</li>
<li class="chapter " data-level="1.8.3" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html#service-instance-per-host-pattern">
6.3、每个主机一个服务实例模式
</a>
<ul class="articles">
<li class="chapter " data-level="1.8.3.1" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html#service-instance-per-virtual-machine-pattern">
6.3.1、每个虚拟机一个服务实例模式
</a>
</li>
<li class="chapter " data-level="1.8.3.2" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html#service-instance-per-container-pattern">
6.3.2、每个容器一个服务实例模式
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.8.4" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html#serverless-deployment">
6.4、Serverless 部署
</a>
</li>
<li class="chapter " data-level="1.8.5" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html#summary">
6.5、总结
</a>
</li>
<li class="chapter " data-level="1.8.6" data-path="6-choosing-deployment-strategy.html">
<a href="6-choosing-deployment-strategy.html#microservices-in-action">
微服务实战：使用 NGINX 在不同主机上部署微服务
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.9" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html">
7、重构单体应用为微服务
</a>
<ul class="articles">
<li class="chapter " data-level="1.9.1" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html#overview-of-refactoring-to-microservices">
7.1、微服务重构概述
</a>
</li>
<li class="chapter " data-level="1.9.2" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html#strategy-1-Stop-digging">
7.2、策略一：停止挖掘
</a>
</li>
<li class="chapter " data-level="1.9.3" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html#strategy-2-split-frontend-and-backend">
7.3、策略二：前后端分离
</a>
</li>
<li class="chapter " data-level="1.9.4" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html#strategy-3-extract-services">
7.4、策略三：提取服务
</a>
<ul class="articles">
<li class="chapter " data-level="1.9.4.1" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html#prioritizing-which-modules-to-convert-into-services">
7.4.1、优先将哪些模块转换为微服务
</a>
</li>
<li class="chapter " data-level="1.9.4.2" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html#how-to-extract-a-module">
7.4.2、如何提取模块
</a>
</li>
</ul>
</li>
<li class="chapter " data-level="1.9.5" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html#summary">
7.5、总结
</a>
</li>
<li class="chapter " data-level="1.9.6" data-path="7-refactoring-a-monolith-into-microservices.html">
<a href="7-refactoring-a-monolith-into-microservices.html#microservices-in-action">
微服务实战：使用 NGINX 征服单体
</a>
</li>
</ul>
</li>
<li class="divider"></li>
<li>
<a href="https://www.gitbook.com" target="blank" class="gitbook-link">
本书使用 GitBook 发布
</a>
</li>
</ul>
</nav>
</div>
<div class="book-body">
<div class="body-inner">
<div class="book-header" role="navigation">
<!-- Title -->
<h1>
<i class="fa fa-circle-o-notch fa-spin"></i>
<a href="." >2、使用 API 网关</a>
</h1>
</div>
<div class="page-wrapper" tabindex="-1" role="main">
<div class="page-inner">
<section class="normal markdown-section">
<h1 id="2&#x3001;&#x4F7F;&#x7528;-api-&#x7F51;&#x5173;">2&#x3001;&#x4F7F;&#x7528; API &#x7F51;&#x5173;</h1>
<p>&#x672C;&#x4E66;&#x7684;&#x4E03;&#x4E2A;&#x7AE0;&#x8282;&#x4ECB;&#x7ECD;&#x5982;&#x4F55;&#x8BBE;&#x8BA1;&#x3001;&#x6784;&#x5EFA;&#x548C;&#x90E8;&#x7F72;&#x5FAE;&#x670D;&#x52A1;&#x3002;<a href="1-introduction-to-microservices.html">&#x7B2C;&#x4E00;&#x7AE0;</a>&#x4ECB;&#x7ECD;&#x4E86;&#x5FAE;&#x670D;&#x52A1;&#x67B6;&#x6784;&#x6A21;&#x5F0F;&#x3002;&#x5B83;&#x9610;&#x8FF0;&#x4E86;&#x4F7F;&#x7528;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x4F18;&#x70B9;&#x4E0E;&#x7F3A;&#x70B9;&#xFF0C;&#x4EE5;&#x53CA;&#x5C3D;&#x7BA1;&#x5982;&#x6B64;&#xFF0C;&#x5FAE;&#x670D;&#x52A1;&#x901A;&#x5E38;&#x662F;&#x590D;&#x6742;&#x5E94;&#x7528;&#x7684;&#x7406;&#x60F3;&#x9009;&#x62E9;&#x3002;&#x8BE5;&#x7CFB;&#x5217;&#x7684;&#x7B2C;&#x4E8C;&#x7AE0;&#x5C06;&#x63A2;&#x8BA8;&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x6784;&#x5EFA;&#x5FAE;&#x670D;&#x52A1;&#x3002;</p>
<p>&#x5F53;&#x4F60;&#x9009;&#x62E9;&#x5C06;&#x5E94;&#x7528;&#x6784;&#x5EFA;&#x6210;&#x4E3A;&#x4E00;&#x7EC4;&#x5FAE;&#x670D;&#x52A1;&#x65F6;&#xFF0C;&#x4F60;&#x9700;&#x8981;&#x51B3;&#x5B9A;&#x5E94;&#x7528;&#x5BA2;&#x6237;&#x7AEF;&#x5C06;&#x5982;&#x4F55;&#x4E0E;&#x5FAE;&#x670D;&#x52A1;&#x8FDB;&#x884C;&#x4EA4;&#x4E92;&#x3002;&#x5355;&#x4F53;&#x5E94;&#x7528;&#x53EA;&#x6709;&#x4E00;&#x7EC4;&#x7AEF;&#x70B9;&#xFF08;endpoint&#xFF09;&#xFF0C;&#x901A;&#x5E38;&#x4F7F;&#x7528;&#x526F;&#x672C;&#xFF08;replicated&#xFF09;&#x7ED3;&#x5408;&#x8D1F;&#x8F7D;&#x5747;&#x8861;&#x6765;&#x5206;&#x914D;&#x6D41;&#x91CF;&#x3002;</p>
<p>&#x7136;&#x800C;&#xFF0C;&#x5728;&#x5FAE;&#x670D;&#x52A1;&#x67B6;&#x6784;&#x4E2D;&#xFF0C;&#x901A;&#x5E38;&#x6BCF;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x90FD;&#x66B4;&#x9732;&#x4E00;&#x7EC4;&#x6BD4;&#x8F83;&#x7EC6;&#x9897;&#x7C92;&#x7684;&#x7AEF;&#x70B9;&#x3002;&#x5728;&#x672C;&#x6587;&#x4E2D;&#xFF0C;&#x6211;&#x4EEC;&#x5C06;&#x7814;&#x7A76;&#x5982;&#x4F55;&#x6539;&#x8FDB;&#x5BA2;&#x6237;&#x7AEF;&#x901A;&#x4FE1;&#xFF0C;&#x5E76;&#x63D0;&#x51FA;&#x4E00;&#x4E2A;&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x7684;&#x65B9;&#x6848;&#x3002;</p>
<p><a id="introduction"></a></p>
<h2 id="21&#x3001;&#x7B80;&#x4ECB;">2.1&#x3001;&#x7B80;&#x4ECB;</h2>
<p>&#x6211;&#x4EEC;&#x5047;&#x8BBE;&#x4F60;&#x6B63;&#x5728;&#x4E3A;&#x4E00;&#x4E2A;&#x8D2D;&#x7269;&#x5E94;&#x7528;&#x5F00;&#x53D1;&#x4E00;&#x4E2A;&#x539F;&#x751F;&#x79FB;&#x52A8;&#x5BA2;&#x6237;&#x7AEF;&#x3002;&#x4F60;&#x53EF;&#x80FD;&#x9700;&#x8981;&#x5B9E;&#x73B0;&#x4E00;&#x4E2A;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x9875;&#x9762;&#xFF0C;&#x7528;&#x4E8E;&#x5C55;&#x793A;&#x5546;&#x54C1;&#x4FE1;&#x606F;&#x3002;</p>
<p>&#x4F8B;&#x5982;&#xFF0C;&#x56FE; 2-1 &#x5C55;&#x793A;&#x4E86;&#x5728; Amazon &#x7684; Android &#x79FB;&#x52A8;&#x5E94;&#x7528;&#x4E2D;&#x6EDA;&#x52A8;&#x4EA7;&#x54C1;&#x4FE1;&#x606F;&#x65F6;&#x6240;&#x770B;&#x5230;&#x7684;&#x5185;&#x5BB9;&#x3002;</p>
<figure id="fig1.4.1"><img src="resources/2-1.png" alt="&#x56FE; 2-1&#x3001;&#x4E00;&#x4E2A;&#x7B80;&#x5355;&#x7684;&#x8D2D;&#x7269;&#x5E94;&#x7528;"><figcaption>&#x56FE; 2-1&#x3001;&#x4E00;&#x4E2A;&#x7B80;&#x5355;&#x7684;&#x8D2D;&#x7269;&#x5E94;&#x7528;</figcaption></figure>
<p>&#x8FD9;&#x662F;&#x4E00;&#x4E2A;&#x667A;&#x80FD;&#x624B;&#x673A;&#x5E94;&#x7528;&#xFF0C;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x9875;&#x9762;&#x5C55;&#x793A;&#x4E86;&#x8BB8;&#x591A;&#x4FE1;&#x606F;&#x3002;&#x4E0D;&#x4EC5;&#x6709;&#x57FA;&#x672C;&#x7684;&#x4EA7;&#x54C1;&#x4FE1;&#x606F;&#xFF0C;&#x5982;&#x540D;&#x79F0;&#x3001;&#x63CF;&#x8FF0;&#x548C;&#x4EF7;&#x683C;&#xFF0C;&#x9875;&#x9762;&#x8FD8;&#x5C55;&#x793A;&#x4E86;&#xFF1A;</p>
<ol>
<li>&#x8D2D;&#x7269;&#x8F66;&#x4E2D;&#x7684;&#x7269;&#x54C1;&#x6570;&#x91CF;</li>
<li>&#x8BA2;&#x5355;&#x5386;&#x53F2;</li>
<li>&#x5BA2;&#x6237;&#x8BC4;&#x4EF7;</li>
<li>&#x4F4E;&#x5E93;&#x5B58;&#x8B66;&#x544A;</li>
<li>&#x914D;&#x9001;&#x9009;&#x9879;</li>
<li>&#x5404;&#x79CD;&#x63A8;&#x8350;&#xFF0C;&#x5305;&#x62EC;&#x4E86;&#x8D2D;&#x4E70;&#x6B64;&#x4EA7;&#x54C1;&#x7684;&#x5BA2;&#x6237;&#x8D2D;&#x4E70;&#x7684;&#x5176;&#x4ED6;&#x4EA7;&#x54C1;</li>
<li>&#x9009;&#x62E9;&#x6027;&#x8D2D;&#x4E70;&#x9009;&#x9879;</li>
</ol>
<p>&#x5728;&#x4F7F;&#x7528;&#x5355;&#x4F53;&#x5E94;&#x7528;&#x67B6;&#x6784;&#x7684;&#x60C5;&#x51B5;&#x4E0B;&#xFF0C;&#x79FB;&#x52A8;&#x5BA2;&#x6237;&#x7AEF;&#x901A;&#x8FC7;&#x5BF9;&#x5E94;&#x7528;&#x8FDB;&#x884C;&#x5355;&#x4E2A; REST &#x8C03;&#x7528;&#x6765;&#x68C0;&#x7D22;&#x6B64;&#x6570;&#x636E;&#xFF0C;&#x4F8B;&#x5982;&#xFF1A;</p>
<pre><code>GET api.company.com/productdetails/productId
</code></pre><p>&#x8D1F;&#x8F7D;&#x5747;&#x8861;&#x5668;&#x5C06;&#x8BF7;&#x6C42;&#x8DEF;&#x7531;&#x5230;&#x51E0;&#x4E2A;&#x76F8;&#x540C;&#x5E94;&#x7528;&#x5B9E;&#x4F8B;&#x4E2D;&#x7684;&#x5176;&#x4E2D;&#x4E00;&#x4E2A;&#x3002;&#x4E4B;&#x540E;&#xFF0C;&#x5E94;&#x7528;&#x67E5;&#x8BE2;&#x5404;&#x4E2A;&#x6570;&#x636E;&#x5E93;&#x8868;&#x5E76;&#x8FD4;&#x56DE;&#x54CD;&#x5E94;&#x7ED9;&#x5BA2;&#x6237;&#x7AEF;&#x3002;&#x76F8;&#x6BD4;&#x4E4B;&#x4E0B;&#xFF0C;&#x5F53;&#x4F7F;&#x7528;&#x5FAE;&#x670D;&#x52A1;&#x67B6;&#x6784;&#x65F6;&#xFF0C;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x9875;&#x9762;&#x4E0A;&#x5C55;&#x793A;&#x7684;&#x6570;&#x636E;&#x6765;&#x81EA;&#x591A;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x3002;&#x4EE5;&#x4E0B;&#x662F;&#x4E00;&#x4E9B;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x6570;&#x636E;&#x53EF;&#x80FD;&#x6D89;&#x53CA;&#x5230;&#x7684;&#x5FAE;&#x670D;&#x52A1;&#xFF1A;</p>
<ul>
<li><strong>&#x8BA2;&#x5355;&#x670D;&#x52A1;</strong> &#x2014; &#x8BA2;&#x5355;&#x5386;&#x53F2;</li>
<li><strong>&#x76EE;&#x5F55;&#xFF08;catalog&#xFF09;&#x670D;&#x52A1;</strong> &#x2014; &#x57FA;&#x672C;&#x7684;&#x4EA7;&#x54C1;&#x4FE1;&#x606F;&#xFF0C;&#x5982;&#x4EA7;&#x54C1;&#x540D;&#x79F0;&#x3001;&#x56FE;&#x7247;&#x548C;&#x4EF7;&#x683C;</li>
<li><strong>&#x8BC4;&#x4EF7;&#x670D;&#x52A1;</strong> &#x2014; &#x5BA2;&#x6237;&#x8BC4;&#x4EF7;</li>
<li><strong>&#x5E93;&#x5B58;&#x670D;&#x52A1;</strong> &#x2014; &#x4F4E;&#x5E93;&#x5B58;&#x8B66;&#x544A;</li>
<li><strong>&#x914D;&#x9001;&#x670D;&#x52A1;</strong> &#x2014; &#x914D;&#x9001;&#x9009;&#x9879;&#x3001;&#x671F;&#x9650;&#x548C;&#x8D39;&#x7528;&#xFF0C;&#x7531;&#x914D;&#x9001;&#x65B9;&#x7684; API &#x5355;&#x72EC;&#x63D0;&#x4F9B; </li>
<li><strong>&#x63A8;&#x8350;&#x670D;&#x52A1;</strong> &#x2014; &#x63A8;&#x8350;&#x7C7B;&#x76EE;</li>
</ul>
<figure id="fig1.4.2"><img src="resources/2-2.png" alt="&#x56FE; 2-2&#x3001;&#x5C06;&#x79FB;&#x52A8;&#x5BA2;&#x6237;&#x7AEF;&#x7684;&#x9700;&#x6C42;&#x6620;&#x5C04;&#x5230;&#x76F8;&#x5173;&#x5FAE;&#x670D;&#x52A1;"><figcaption>&#x56FE; 2-2&#x3001;&#x5C06;&#x79FB;&#x52A8;&#x5BA2;&#x6237;&#x7AEF;&#x7684;&#x9700;&#x6C42;&#x6620;&#x5C04;&#x5230;&#x76F8;&#x5173;&#x5FAE;&#x670D;&#x52A1;</figcaption></figure>
<p>&#x6211;&#x4EEC;&#x9700;&#x8981;&#x51B3;&#x5B9A;&#x79FB;&#x52A8;&#x5BA2;&#x6237;&#x7AEF;&#x5982;&#x4F55;&#x8BBF;&#x95EE;&#x8FD9;&#x4E9B;&#x670D;&#x52A1;&#x3002;&#x8BA9;&#x6211;&#x4EEC;&#x6765;&#x770B;&#x770B;&#x6709;&#x54EA;&#x4E9B;&#x65B9;&#x6CD5;&#x3002;</p>
<p><a id="direct-client-to-microservice-communication"></a></p>
<h2 id="22&#x3001;&#x5BA2;&#x6237;&#x7AEF;&#x4E0E;&#x5FAE;&#x670D;&#x52A1;&#x76F4;&#x63A5;&#x901A;&#x4FE1;">2.2&#x3001;&#x5BA2;&#x6237;&#x7AEF;&#x4E0E;&#x5FAE;&#x670D;&#x52A1;&#x76F4;&#x63A5;&#x901A;&#x4FE1;</h2>
<p>&#x7406;&#x8BBA;&#x4E0A;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x53EF;&#x4EE5;&#x76F4;&#x63A5;&#x5411;&#x6BCF;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x53D1;&#x9001;&#x8BF7;&#x6C42;&#x3002;&#x6BCF;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x90FD;&#x6709;&#x4E00;&#x4E2A;&#x516C;&#x5F00;&#x7684;&#x7AEF;&#x70B9;&#xFF1A;</p>
<pre><code>https://serviceName.api.company.name
</code></pre><p>&#x8BE5; URL &#x5C06;&#x6620;&#x5C04;&#x5230;&#x7528;&#x4E8E;&#x8DE8;&#x53EF;&#x7528;&#x5B9E;&#x4F8B;&#x5206;&#x53D1;&#x8BF7;&#x6C42;&#x7684;&#x5FAE;&#x670D;&#x52A1;&#x8D1F;&#x8F7D;&#x5747;&#x8861;&#x5668;&#x3002;&#x4E3A;&#x4E86;&#x68C0;&#x7D22;&#x7279;&#x5B9A;&#x7684;&#x4EA7;&#x54C1;&#x9875;&#x9762;&#x4FE1;&#x606F;&#xFF0C;&#x79FB;&#x52A8;&#x5BA2;&#x6237;&#x7AEF;&#x5C06;&#x5411;&#x4E0A;&#x8FF0;&#x7684;&#x6BCF;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x53D1;&#x9001;&#x8BF7;&#x6C42;&#x3002;</p>
<p>&#x4E0D;&#x5E78;&#x7684;&#x662F;&#xFF0C;&#x8FD9;&#x79CD;&#x65B9;&#x5F0F;&#x5B58;&#x5728;&#x7740;&#x6311;&#x6218;&#x4E0E;&#x9650;&#x5236;&#x3002;&#x7B2C;&#x4E00;&#x4E2A;&#x95EE;&#x9898;&#x662F;&#x5BA2;&#x6237;&#x7AEF;&#x7684;&#x9700;&#x6C42;&#x4E0E;&#x6BCF;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x66B4;&#x9732;&#x7684;&#x7EC6;&#x7C92;&#x5EA6;&#x7684; API &#x4E0D;&#x5339;&#x914D;&#x3002;&#x5728;&#x6B64;&#x793A;&#x4F8B;&#x4E2D;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x9700;&#x8981;&#x8FDB;&#x884C;&#x4E03;&#x6B21;&#x5355;&#x72EC;&#x7684;&#x8BF7;&#x6C42;&#x3002;&#x5982;&#x679C;&#x5728;&#x66F4;&#x52A0;&#x590D;&#x6742;&#x7684;&#x5E94;&#x7528;&#x4E2D;&#xFF0C;&#x5B83;&#x53EF;&#x80FD;&#x9700;&#x8981;&#x505A;&#x66F4;&#x591A;&#x7684;&#x5DE5;&#x4F5C;&#x3002;&#x4F8B;&#x5982;&#xFF0C;Amazon &#x7684;&#x4EA7;&#x54C1;&#x9875;&#x9762;&#x6E32;&#x67D3;&#x7275;&#x6D89;&#x5230;&#x6570;&#x767E;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x3002;&#x867D;&#x7136;&#x5BA2;&#x6237;&#x7AEF;&#x53EF;&#x4EE5;&#x901A;&#x8FC7; LAN &#x53D1;&#x9001;&#x8BB8;&#x591A;&#x8BF7;&#x6C42;&#xFF0C;&#x4F46;&#x5728;&#x516C;&#x5171;&#x4E92;&#x8054;&#x7F51;&#x4E0B;&#x6548;&#x7387;&#x5DF2;&#x7ECF;&#x4F4E;&#x4E0B;&#xFF0C;&#x5728;&#x79FB;&#x52A8;&#x7F51;&#x7EDC;&#x5FC5;&#x7136;&#x662F;&#x4E0D;&#x5207;&#x5B9E;&#x9645;&#x3002;</p>
<p>&#x5BA2;&#x6237;&#x7AEF;&#x76F4;&#x63A5;&#x8C03;&#x7528;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x53E6;&#x4E00;&#x4E2A;&#x95EE;&#x9898;&#x662F;&#x6709;&#x4E9B;&#x670D;&#x52A1;&#x53EF;&#x80FD;&#x4F7F;&#x7528;&#x4E86;&#x975E; web &#x53CB;&#x597D;&#x534F;&#x8BAE;&#x3002;&#x4E00;&#x4E2A;&#x670D;&#x52A1;&#x53EF;&#x80FD;&#x4F7F;&#x7528;&#x4E86; Thrift &#x4E8C;&#x8FDB;&#x5236; RPC&#xFF0C;&#x800C;&#x53E6;&#x4E00;&#x4E2A;&#x5219;&#x53EF;&#x80FD;&#x4F7F;&#x7528; AMQP &#x6D88;&#x606F;&#x534F;&#x8BAE;&#x3002;&#x8FD9;&#x4E24;&#x4E2A;&#x534F;&#x8BAE;&#x65E0;&#x8BBA;&#x662F;&#x5BF9;&#x6D4F;&#x89C8;&#x5668;&#x8FD8;&#x662F;&#x9632;&#x706B;&#x5899;&#x6765;&#x8BF4;&#x90FD;&#x662F;&#x4E0D;&#x53CB;&#x597D;&#x7684;&#xFF0C;&#x6700;&#x597D;&#x662F;&#x5728;&#x5185;&#x90E8;&#x4F7F;&#x7528;&#x3002;&#x5E94;&#x7528;&#x5728;&#x9632;&#x706B;&#x5899;&#x4E4B;&#x5916;&#x5E94;&#x8BE5;&#x4F7F;&#x7528; HTTP &#x6216;&#x8005; WebSocket &#x4E4B;&#x7C7B;&#x7684;&#x534F;&#x8BAE;&#x3002;</p>
<p>&#x8FD9;&#x79CD;&#x65B9;&#x6CD5;&#x7684;&#x53E6;&#x4E00;&#x4E2A;&#x7F3A;&#x70B9;&#x662F;&#x5B83;&#x96BE;&#x4EE5;&#x91CD;&#x6784;&#x5FAE;&#x670D;&#x52A1;&#x3002;&#x968F;&#x7740;&#x65F6;&#x95F4;&#x63A8;&#x79FB;&#xFF0C;&#x6211;&#x4EEC;&#x53EF;&#x80FD;&#x4F1A;&#x60F3;&#x6539;&#x53D8;&#x7CFB;&#x7EDF;&#x5212;&#x5206;&#x670D;&#x52A1;&#x3002;&#x4F8B;&#x5982;&#xFF0C;&#x6211;&#x4EEC;&#x53EF;&#x80FD;&#x4F1A;&#x5408;&#x5E76;&#x4E24;&#x4E2A;&#x670D;&#x52A1;&#x6216;&#x8005;&#x5C06;&#x670D;&#x52A1;&#x62C6;&#x5206;&#x4E3A;&#x4E24;&#x4E2A;&#x6216;&#x8005;&#x591A;&#x4E2A;&#x3002;&#x7136;&#x800C;&#xFF0C;&#x5982;&#x679C;&#x5BA2;&#x6237;&#x7AEF;&#x76F4;&#x63A5;&#x4E0E;&#x670D;&#x52A1;&#x8FDB;&#x884C;&#x901A;&#x4FE1;&#xFF0C;&#x5B9E;&#x65BD;&#x8FD9;&#x7C7B;&#x7684;&#x91CD;&#x6784;&#x5C06;&#x53D8;&#x5F97;&#x975E;&#x5E38;&#x56F0;&#x96BE;&#x3002;</p>
<p>&#x7531;&#x4E8E;&#x5B58;&#x5728;&#x8FD9;&#x4E9B;&#x95EE;&#x9898;&#xFF0C;&#x5F88;&#x5C11;&#x6709;&#x5BA2;&#x6237;&#x7AEF;&#x76F4;&#x63A5;&#x4E0E;&#x5FAE;&#x670D;&#x52A1;&#x8FDB;&#x884C;&#x901A;&#x4FE1;&#x3002;</p>
<p><a id="using-an-api-gateway"></a></p>
<h2 id="23&#x3001;&#x4F7F;&#x7528;-api-&#x7F51;&#x5173;">2.3&#x3001;&#x4F7F;&#x7528; API &#x7F51;&#x5173;</h2>
<p>&#x901A;&#x5E38;&#x66F4;&#x597D;&#x7684;&#x65B9;&#x5F0F;&#x662F;&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x3002;API &#x7F51;&#x5173;&#x662F;&#x4E00;&#x4E2A;&#x670D;&#x52A1;&#x5668;&#xFF0C;&#x662F;&#x7CFB;&#x7EDF;&#x7684;&#x5355;&#x5165;&#x53E3;&#x70B9;&#x3002;&#x5B83;&#x7C7B;&#x4F3C;&#x4E8E;&#x9762;&#x5411;&#x5BF9;&#x8C61;&#x8BBE;&#x8BA1;&#x6A21;&#x5F0F;&#x4E2D;&#x7684;&#x95E8;&#x9762;&#xFF08;Facade&#xFF09;&#x6A21;&#x5F0F;&#x3002;API &#x7F51;&#x5173;&#x5C01;&#x88C5;&#x4E86;&#x5185;&#x90E8;&#x7CFB;&#x7EDF;&#x67B6;&#x6784;&#xFF0C;&#x5E76;&#x9488;&#x5BF9;&#x6BCF;&#x4E2A;&#x5BA2;&#x6237;&#x7AEF;&#x63D0;&#x4F9B;&#x4E00;&#x4E2A;&#x5B9A;&#x5236; API&#x3002;&#x5B83;&#x8FD8;&#x53EF;&#x7528;&#x4E8E;&#x8BA4;&#x8BC1;&#x3001;&#x76D1;&#x63A7;&#x3001;&#x8D1F;&#x8F7D;&#x5747;&#x8861;&#x3001;&#x7F13;&#x5B58;&#x548C;&#x9759;&#x6001;&#x54CD;&#x5E94;&#x5904;&#x7406;&#x3002;</p>
<p>&#x56FE; 2-3 &#x5C55;&#x793A;&#x4E86; API &#x901A;&#x5E38;&#x5982;&#x4F55;&#x6574;&#x5408;&#x67B6;&#x6784;</p>
<figure id="fig1.4.3"><img src="resources/2-3.png" alt="&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x7684;&#x5FAE;&#x670D;&#x52A1;"><figcaption>&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x7684;&#x5FAE;&#x670D;&#x52A1;</figcaption></figure>
<p>API &#x7F51;&#x5173;&#x8D1F;&#x8D23;&#x8BF7;&#x6C42;&#x8DEF;&#x7531;&#x3001;&#x7EC4;&#x5408;&#x548C;&#x534F;&#x8BAE;&#x8F6C;&#x6362;&#x3002;&#x6240;&#x6709;&#x5BA2;&#x6237;&#x7AEF;&#x8BF7;&#x6C42;&#x9996;&#x5148;&#x8981;&#x901A;&#x8FC7; API &#x7F51;&#x5173;&#xFF0C;&#x4E4B;&#x540E;&#x8BF7;&#x6C42;&#x88AB;&#x8DEF;&#x7531;&#x5230;&#x9002;&#x5F53;&#x7684;&#x670D;&#x52A1;&#x3002;API &#x7F51;&#x5173;&#x901A;&#x5E38;&#x4F1A;&#x901A;&#x8FC7;&#x8C03;&#x7528;&#x591A;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x6765;&#x5904;&#x7406;&#x4E00;&#x4E2A;&#x8BF7;&#x6C42;&#x5E76;&#x805A;&#x5408;&#x7ED3;&#x679C;&#x3002;&#x5B83;&#x53EF;&#x4EE5;&#x5728; Web &#x534F;&#x8BAE;&#xFF08;&#x5982; HTTP &#x548C; WebSocket&#xFF09;&#x548C;&#x7528;&#x4E8E;&#x5185;&#x90E8;&#x7684;&#x975E; Web &#x53CB;&#x597D;&#x534F;&#x8BAE;&#x4E4B;&#x95F4;&#x8FDB;&#x884C;&#x8F6C;&#x6362;&#x3002;</p>
<p>API &#x7F51;&#x5173;&#x8FD8;&#x53EF;&#x4EE5;&#x4E3A;&#x6BCF;&#x4E2A;&#x5BA2;&#x6237;&#x7AEF;&#x63D0;&#x4F9B;&#x4E00;&#x4E2A;&#x5B9A;&#x5236; API&#x3002;&#x5B83;&#x901A;&#x5E38;&#x4F1A;&#x4E3A;&#x79FB;&#x52A8;&#x5BA2;&#x6237;&#x7AEF;&#x66B4;&#x9732;&#x4E00;&#x4E2A;&#x7C97;&#x7C92;&#x5EA6;&#x7684; API&#x3002;&#x4F8B;&#x5982;&#xFF0C;&#x8003;&#x8651;&#x4E00;&#x4E0B;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x573A;&#x666F;&#xFF0C;API &#x7F51;&#x5173;&#x53EF;&#x4EE5;&#x63D0;&#x4F9B;&#x4E00;&#x4E2A;&#x7AEF;&#x70B9; <code>/productdetails?productid=xxx</code>&#xFF0C;&#xFF08;&#x5982;&#x56FE; 2-3 &#x6240;&#x793A;&#xFF0C;&#x4E00;&#x4E2A;&#x4F7F;&#x7528;&#x4E86; API &#x7F51;&#x5173;&#x7684;&#x5FAE;&#x670D;&#x52A1;&#xFF09;&#x5141;&#x8BB8;&#x79FB;&#x52A8;&#x5BA2;&#x6237;&#x7AEF;&#x901A;&#x8FC7;&#x4E00;&#x4E2A;&#x5355;&#x72EC;&#x7684;&#x8BF7;&#x6C42;&#x6765;&#x68C0;&#x7D22;&#x6240;&#x6709;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x3002;API &#x7F51;&#x5173;&#x901A;&#x8FC7;&#x8C03;&#x7528;&#x5404;&#x79CD;&#x670D;&#x52A1;&#xFF08;&#x4EA7;&#x54C1;&#x4FE1;&#x606F;&#x3001;&#x63A8;&#x8350;&#x3001;&#x8BC4;&#x4EF7;&#x7B49;&#xFF09;&#x5E76;&#x7EC4;&#x5408;&#x7ED3;&#x679C;&#x3002;</p>
<p><a href="http://techblog.netflix.com/2013/02/rxjava-netflix-api.html" target="_blank">Netflix API &#x7F51;&#x5173;</a>&#x5C31;&#x662F;&#x4E00;&#x4E2A;&#x5F88;&#x597D;&#x7684; API &#x7F51;&#x5173;&#x6848;&#x4F8B;&#x3002;Netflix &#x6D41;&#x5A92;&#x4F53;&#x670D;&#x52A1;&#x53EF;&#x5728;&#x6570;&#x767E;&#x79CD;&#x4E0D;&#x540C;&#x7C7B;&#x578B;&#x7684;&#x8BBE;&#x5907;&#x4E0A;&#x4F7F;&#x7528;&#xFF0C;&#x5305;&#x62EC;&#x7535;&#x89C6;&#x673A;&#x3001;&#x673A;&#x9876;&#x76D2;&#x3001;&#x667A;&#x80FD;&#x624B;&#x673A;&#x3001;&#x6E38;&#x620F;&#x673A;&#x548C;&#x5E73;&#x677F;&#x7535;&#x8111;&#x7B49;&#x3002;&#x8D77;&#x521D;&#xFF0C;Netflix &#x5C1D;&#x8BD5;&#x4E3A;&#x4ED6;&#x4EEC;&#x7684;&#x6D41;&#x5A92;&#x4F53;&#x670D;&#x52A1;&#x63D0;&#x4F9B;&#x4E00;&#x4E2A;<a href="http://www.programmableweb.com/news/why-rest-keeps-me-night/2012/05/15" target="_blank">&#x901A;&#x7528;</a>&#x7684; API&#x3002;&#x540E;&#x6765;&#xFF0C;&#x4ED6;&#x4EEC;&#x53D1;&#x73B0;&#x7531;&#x4E8E;&#x8BBE;&#x5907;&#x79CD;&#x7C7B;&#x7E41;&#x591A;&#xFF0C;&#x5E76;&#x4E14;&#x4ED6;&#x4EEC;&#x5404;&#x81EA;&#x6709;&#x7740;&#x4E0D;&#x540C;&#x9700;&#x6C42;&#xFF0C;&#x6240;&#x4EE5;&#x5E76;&#x4E0D;&#x662F;&#x80FD;&#x5F88;&#x597D;&#x5730;&#x8FD0;&#x4F5C;&#x3002;&#x5982;&#x4ECA;&#xFF0C;&#x4ED6;&#x4EEC;&#x4F7F;&#x7528;&#x4E86; API &#x7F51;&#x5173;&#xFF0C;&#x901A;&#x8FC7;&#x8FD0;&#x884C;&#x7279;&#x5B9A;&#x8BBE;&#x5907;&#x9002;&#x914D;&#x4EE3;&#x7801;&#x6765;&#x4E3A;&#x6BCF;&#x4E2A;&#x8BBE;&#x5907;&#x63D0;&#x4F9B;&#x4E00;&#x4E2A;&#x5B9A;&#x5236; API&#x3002;</p>
<p><a id="benefits-and-drawbacks-of-an-api-gateway"></a></p>
<h2 id="24&#x3001;api-&#x7F51;&#x5173;&#x7684;&#x4F18;&#x70B9;&#x4E0E;&#x7F3A;&#x70B9;">2.4&#x3001;API &#x7F51;&#x5173;&#x7684;&#x4F18;&#x70B9;&#x4E0E;&#x7F3A;&#x70B9;</h2>
<p>&#x6B63;&#x5982;&#x4F60;&#x6240;&#x6599;&#xFF0C;&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x540C;&#x6837;&#x5B58;&#x5728;&#x597D;&#x5904;&#x4E0E;&#x574F;&#x5904;&#x3002;&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x7684;&#x4E3B;&#x8981;&#x597D;&#x5904;&#x662F;&#x5B83;&#x5C01;&#x88C5;&#x4E86;&#x5E94;&#x7528;&#x7684;&#x5185;&#x90E8;&#x7ED3;&#x6784;&#x3002;&#x5BA2;&#x6237;&#x7AEF;&#x53EA;&#x9700;&#x8981;&#x4E0E;&#x7F51;&#x5173;&#x901A;&#x4FE1;&#xFF0C;&#x800C;&#x4E0D;&#x5FC5;&#x8C03;&#x7528;&#x7279;&#x5B9A;&#x7684;&#x670D;&#x52A1;&#x3002;API &#x7F51;&#x5173;&#x4E3A;&#x6BCF;&#x79CD;&#x7C7B;&#x578B;&#x7684;&#x5BA2;&#x6237;&#x7AEF;&#x63D0;&#x4F9B;&#x4E86;&#x7279;&#x5B9A;&#x7684; API&#xFF0C;&#x51CF;&#x5C11;&#x4E86;&#x5BA2;&#x6237;&#x7AEF;&#x4E0E;&#x5E94;&#x7528;&#x4E4B;&#x95F4;&#x7684;&#x5F80;&#x8FD4;&#x6B21;&#x6570;&#x3002;&#x540C;&#x65F6;&#xFF0C;&#x5B83;&#x8FD8;&#x7B80;&#x5316;&#x4E86;&#x5BA2;&#x6237;&#x7AEF;&#x7684;&#x4EE3;&#x7801;&#x3002;</p>
<p>API &#x7F51;&#x5173;&#x4E5F;&#x5B58;&#x5728;&#x4E00;&#x4E9B;&#x7F3A;&#x70B9;&#xFF0C;&#x5B83;&#x672C;&#x8EAB;&#x4E5F;&#x662F;&#x4E00;&#x4E2A;&#x9AD8;&#x5EA6;&#x53EF;&#x7528;&#x7684;&#x7EC4;&#x4EF6;&#xFF0C;&#x9700;&#x8981;&#x5F00;&#x53D1;&#x3001;&#x90E8;&#x7F72;&#x548C;&#x7BA1;&#x7406;&#x3002;&#x53E6;&#x5916;&#xFF0C;&#x8FD8;&#x6709;&#x4E00;&#x4E2A;&#x98CE;&#x9669;&#x662F; API &#x7F51;&#x5173;&#x53EF;&#x80FD;&#x4F1A;&#x6210;&#x4E3A;&#x5F00;&#x53D1;&#x74F6;&#x9888;&#x3002;&#x5F00;&#x53D1;&#x4EBA;&#x5458;&#x5FC5;&#x987B;&#x66F4;&#x65B0; API &#x7F51;&#x5173;&#x6765;&#x66B4;&#x9732;&#x6BCF;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x7AEF;&#x70B9;&#x3002;</p>
<p>&#x91CD;&#x8981;&#x7684;&#x662F;&#x66F4;&#x65B0; API &#x7F51;&#x5173;&#x7684;&#x8FC7;&#x7A0B;&#x5E94;&#x5C3D;&#x53EF;&#x80FD;&#x5730;&#x653E;&#x7F13;&#x4E00;&#x4E9B;&#x3002;&#x5426;&#x5219;&#xFF0C;&#x5F00;&#x53D1;&#x4EBA;&#x5458;&#x5C06;&#x88AB;&#x8FEB;&#x6392;&#x961F;&#x7B49;&#x5F85;&#x7F51;&#x5173;&#x66F4;&#x65B0;&#x3002;&#x5C3D;&#x7BA1; API &#x7F51;&#x5173;&#x5B58;&#x5728;&#x8FD9;&#x4E9B;&#x7F3A;&#x70B9;&#xFF0C;&#x4F46;&#x5BF9;&#x4E8E;&#x5927;&#x591A;&#x6570;&#x7684;&#x771F;&#x5B9E;&#x5E94;&#x7528;&#x6765;&#x8BF4;&#xFF0C;&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x662F;&#x6B63;&#x786E;&#x7684;&#x3002;</p>
<p><a id="implementing-an-api-gateway"></a></p>
<h2 id="25&#x3001;&#x5B9E;&#x73B0;-api-&#x7F51;&#x5173;">2.5&#x3001;&#x5B9E;&#x73B0; API &#x7F51;&#x5173;</h2>
<p>&#x6211;&#x4EEC;&#x5DF2;&#x7ECF;&#x4E86;&#x89E3;&#x4E86;&#x4F7F;&#x7528; API &#x7F51;&#x5173;&#x7684;&#x52A8;&#x673A;&#x548C;&#x5229;&#x5F0A;&#xFF0C;&#x63A5;&#x4E0B;&#x6765;&#x8BA9;&#x6211;&#x4EEC;&#x770B;&#x770B;&#x4F60;&#x9700;&#x8981;&#x8003;&#x8651;&#x7684;&#x5404;&#x79CD;&#x8BBE;&#x8BA1;&#x95EE;&#x9898;&#x3002;</p>
<p><a id="performance-and-scalability"></a></p>
<h3 id="251&#x3001;&#x6027;&#x80FD;&#x4E0E;&#x53EF;&#x6269;&#x5C55;&#x6027;">2.5.1&#x3001;&#x6027;&#x80FD;&#x4E0E;&#x53EF;&#x6269;&#x5C55;&#x6027;</h3>
<p>&#x53EA;&#x6709;&#x5C11;&#x6570;&#x516C;&#x53F8;&#x80FD;&#x8FBE;&#x5230; Netflix &#x7684;&#x8FD0;&#x8425;&#x89C4;&#x6A21;&#xFF0C;&#x6BCF;&#x5929;&#x9700;&#x8981;&#x5904;&#x7406;&#x6570;&#x5341;&#x4EBF;&#x7684;&#x8BF7;&#x6C42;&#x3002;&#x4E0D;&#x7BA1;&#x600E;&#x6837;&#xFF0C;&#x5BF9;&#x4E8E;&#x5927;&#x591A;&#x6570;&#x5E94;&#x7528;&#x6765;&#x8BF4;&#xFF0C;API &#x7F51;&#x5173;&#x7684;&#x6027;&#x80FD;&#x548C;&#x53EF;&#x6269;&#x5C55;&#x6027;&#x662F;&#x76F8;&#x5F53;&#x91CD;&#x8981;&#x7684;&#x3002;&#x56E0;&#x6B64;&#xFF0C;&#x5728;&#x4E00;&#x4E2A;&#x652F;&#x6301;&#x5F02;&#x6B65;&#x3001;&#x975E;&#x963B;&#x585E; I/O &#x5E73;&#x53F0;&#x4E0A;&#x6784;&#x5EFA; API &#x7F51;&#x5173;&#x662F;&#x5F88;&#x6709;&#x5FC5;&#x8981;&#x7684;&#x3002;&#x5B9E;&#x73B0;&#x4E00;&#x4E2A;&#x53EF;&#x6269;&#x5C55;&#x7684; API &#x7F51;&#x5173;&#x7684;&#x6280;&#x672F;&#x591A;&#x79CD;&#x591A;&#x6837;&#x3002;&#x5728; JVM &#x4E0A;&#xFF0C;&#x4F60;&#x53EF;&#x4EE5;&#x4F7F;&#x7528;&#x57FA;&#x4E8E; NIO &#x7684;&#x6846;&#x67B6;&#xFF0C;&#x5982; Netty&#x3001;Vertx&#x3001;Spring Reactor &#x6216;&#x8005; JBoss Undertow&#x3002;&#x4E00;&#x4E2A;&#x6D41;&#x884C;&#x7684;&#x975E; JVM &#x9009;&#x62E9;&#x662F;&#x4F7F;&#x7528; Node.js&#xFF0C;&#x5B83;&#x662F;&#x4E00;&#x4E2A;&#x5EFA;&#x7ACB;&#x5728; Chrome &#x7684; JavaScript &#x5F15;&#x64CE;&#x4E4B;&#x4E0A;&#x7684;&#x5E73;&#x53F0;&#x3002;&#x6B64;&#x5916;&#xFF0C;&#x4F60;&#x8FD8;&#x53EF;&#x4EE5;&#x9009;&#x62E9;&#x4F7F;&#x7528; NGINX Plus&#x3002;</p>
<p><a href="https://www.nginx.com/solutions/api-gateway/" target="_blank">NGINX Plus</a> &#x63D0;&#x4F9B;&#x4E86;&#x4E00;&#x4E2A;&#x6210;&#x719F;&#x3001;&#x53EF;&#x6269;&#x5C55;&#x548C;&#x9AD8;&#x6027;&#x80FD;&#x7684; Web &#x670D;&#x52A1;&#x5668;&#x548C;&#x53CD;&#x5411;&#x4EE3;&#x7406;&#xFF0C;&#x5B83;&#x6613;&#x4E8E;&#x90E8;&#x7F72;&#x3001;&#x914D;&#x7F6E;&#x548C;&#x7F16;&#x7A0B;&#x3002;NGINX Plus &#x53EF;&#x4EE5;&#x7BA1;&#x7406;&#x8EAB;&#x4EFD;&#x9A8C;&#x8BC1;&#x3001;&#x8BBF;&#x95EE;&#x63A7;&#x5236;&#x3001;&#x8D1F;&#x8F7D;&#x5747;&#x8861;&#x8BF7;&#x6C42;&#x3001;&#x7F13;&#x5B58;&#x54CD;&#x5E94;&#xFF0C;&#x5E76;&#x4E14;&#x63D0;&#x4F9B;&#x4E86;&#x5E94;&#x7528;&#x5065;&#x5EB7;&#x68C0;&#x67E5;&#x548C;&#x76D1;&#x63A7;&#x529F;&#x80FD;&#x3002;</p>
<p><a id="using-a-reactive-programming-model"></a></p>
<h3 id="252&#x3001;&#x4F7F;&#x7528;&#x54CD;&#x5E94;&#x5F0F;&#x7F16;&#x7A0B;&#x6A21;&#x578B;">2.5.2&#x3001;&#x4F7F;&#x7528;&#x54CD;&#x5E94;&#x5F0F;&#x7F16;&#x7A0B;&#x6A21;&#x578B;</h3>
<p>API &#x7F51;&#x5173;&#x5904;&#x7406;&#x5927;&#x90E8;&#x5206;&#x8BF7;&#x6C42;&#x53EA;&#x662F;&#x7B80;&#x5355;&#x7684;&#x628A;&#x5B83;&#x4EEC;&#x8DEF;&#x7531;&#x5230;&#x4E0E;&#x4E4B;&#x5BF9;&#x5E94;&#x7684;&#x540E;&#x7AEF;&#x670D;&#x52A1;&#x3002;&#x5B83;&#x901A;&#x8FC7;&#x8C03;&#x7528;&#x591A;&#x4E2A;&#x540E;&#x7AEF;&#x670D;&#x52A1;&#x6765;&#x5904;&#x7406;&#x5176;&#x4ED6;&#x8BF7;&#x6C42;&#x5E76;&#x805A;&#x5408;&#x7ED3;&#x679C;&#x3002;&#x5BF9;&#x4E8E;&#x67D0;&#x4E9B;&#x8BF7;&#x6C42;&#xFF0C;&#x5982;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x8BF7;&#x6C42;&#xFF0C;&#x5BF9;&#x540E;&#x7AEF;&#x670D;&#x52A1;&#x8BF7;&#x6C42;&#x800C;&#x8A00;&#x662F;&#x5F7C;&#x6B64;&#x72EC;&#x7ACB;&#x7684;&#x3002;&#x4E3A;&#x4E86;&#x628A;&#x54CD;&#x5E94;&#x65F6;&#x95F4;&#x7F29;&#x77ED;&#x5230;&#x6700;&#x5C0F;&#xFF0C;API &#x7F51;&#x5173;&#x5E94;&#x8BE5;&#x5E76;&#x53D1;&#x6267;&#x884C;&#x72EC;&#x7ACB;&#x8BF7;&#x6C42;&#x3002;</p>
<p>&#x7136;&#x800C;&#xFF0C;&#x6709;&#x65F6;&#x5019;&#xFF0C;&#x8BF7;&#x6C42;&#x662F;&#x76F8;&#x4E92;&#x4F9D;&#x8D56;&#x7684;&#x3002;&#x9996;&#x5148;&#xFF0C;API &#x7F51;&#x5173;&#x53EF;&#x80FD;&#x9700;&#x8981;&#x5728;&#x5C06;&#x8BF7;&#x6C42;&#x8DEF;&#x7531;&#x5230;&#x540E;&#x7AEF;&#x670D;&#x52A1;&#x4E4B;&#x524D;&#xFF0C;&#x901A;&#x8FC7;&#x8C03;&#x7528;&#x9A8C;&#x8BC1;&#x670D;&#x52A1;&#x6765;&#x9A8C;&#x8BC1;&#x8BE5;&#x8BF7;&#x6C42;&#x3002;&#x540C;&#x6837;&#xFF0C;&#x4E3A;&#x4E86;&#x4ECE;&#x5BA2;&#x6237;&#x7684;&#x613F;&#x671B;&#x6E05;&#x5355;&#x4E2D;&#x83B7;&#x53D6;&#x4EA7;&#x54C1;&#x4FE1;&#x606F;&#xFF0C;API &#x7F51;&#x5173;&#x9996;&#x5148;&#x5FC5;&#x987B;&#x68C0;&#x7D22;&#x5305;&#x542B;&#x8BE5;&#x4FE1;&#x606F;&#x7684;&#x5BA2;&#x6237;&#x8D44;&#x6599;&#xFF0C;&#x7136;&#x540E;&#x68C0;&#x7D22;&#x6BCF;&#x4E2A;&#x4EA7;&#x54C1;&#x7684;&#x4FE1;&#x606F;&#x3002;&#x8FD8;&#x6709;&#x4E00;&#x4E2A;&#x6709;&#x8DA3;&#x7684; API &#x7EC4;&#x5408;&#x6848;&#x4F8B;&#x662F; <a href="http://techblog.netflix.com/2013/02/rxjava-netflix-api.html" target="_blank">Netflix &#x89C6;&#x9891;&#x7F51;&#x683C;</a>&#x3002;</p>
<p>&#x4F7F;&#x7528;&#x4F20;&#x7EDF;&#x7684;&#x5F02;&#x6B65;&#x56DE;&#x8C03;&#x65B9;&#x5F0F;&#x6765;&#x7F16;&#x5199; API &#x7EC4;&#x5408;&#x4EE3;&#x7801;&#x4F1A;&#x5F88;&#x5FEB;&#x4F7F;&#x4F60;&#x9677;&#x5165;&#x56DE;&#x8C03;&#x5730;&#x72F1;&#x3002;&#x4EE3;&#x7801;&#x5C06;&#x4F1A;&#x53D8;&#x5F97;&#x6742;&#x4E71;&#x3001;&#x96BE;&#x4EE5;&#x7406;&#x89E3;&#x5E76;&#x4E14;&#x5BB9;&#x6613;&#x51FA;&#x9519;&#x3002;&#x66F4;&#x597D;&#x7684;&#x65B9;&#x5F0F;&#x662F;&#x4F7F;&#x7528;&#x54CD;&#x5E94;&#x5F0F;&#x65B9;&#x6CD5;&#x4EE5;&#x58F0;&#x660E;&#x5F0F;&#x65B9;&#x5F0F;&#x7F16;&#x5199; API &#x7F51;&#x5173;&#x4EE3;&#x7801;&#x3002;&#x54CD;&#x5E94;&#x5F0F;&#x62BD;&#x8C61;&#x7684;&#x4F8B;&#x5B50;&#x5305;&#x62EC; Scala &#x7684; <a href="http://docs.scala-lang.org/overviews/core/futures.html" target="_blank">Future</a>&#x3001;Java 8 &#x4E2D;&#x7684; <a href="https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html" target="_blank">CompletableFuture</a> &#x548C; JavaScript &#x4E2D;&#x7684; <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise" target="_blank">Promise</a>&#x3002;&#x8FD8;&#x6709; <a href="http://reactivex.io/" target="_blank">Reactive Extensions</a>&#xFF08;&#x4E5F;&#x79F0;&#x4E3A; Rx &#x6216; ReactiveX&#xFF09;&#xFF0C;&#x6700;&#x521D;&#x7531; Microsoft &#x4E3A; .NET &#x5E73;&#x53F0;&#x5F00;&#x53D1;&#x3002;Netflix &#x4E3A; JVM &#x521B;&#x5EFA;&#x4E86; RxJava&#xFF0C;&#x4E13;&#x95E8;&#x5E94;&#x7528;&#x5728;&#x5B83;&#x7684; API &#x7F51;&#x5173;&#x3002;&#x8FD8;&#x6709;&#x7528;&#x4E8E; JavaScript &#x7684; RxJS&#xFF0C;&#x5B83;&#x53EF;&#x4EE5;&#x5728;&#x6D4F;&#x89C8;&#x5668;&#x548C; Node.js &#x4E2D;&#x8FD0;&#x884C;&#x3002;&#x4F7F;&#x7528;&#x54CD;&#x5E94;&#x5F0F;&#x53EF;&#x8BA9;&#x4F60;&#x80FD;&#x591F;&#x7F16;&#x5199;&#x51FA;&#x7B80;&#x5355;&#x800C;&#x9AD8;&#x6548;&#x7684; API &#x7F51;&#x5173;&#x4EE3;&#x7801;&#x3002;</p>
<p><a id="service-invocation"></a></p>
<h3 id="253&#x3001;&#x670D;&#x52A1;&#x8C03;&#x7528;">2.5.3&#x3001;&#x670D;&#x52A1;&#x8C03;&#x7528;</h3>
<p>&#x57FA;&#x4E8E;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x5E94;&#x7528;&#x662F;&#x4E00;&#x4E2A;&#x5206;&#x5E03;&#x5F0F;&#x7CFB;&#x7EDF;&#xFF0C;&#x5FC5;&#x987B;&#x4F7F;&#x7528;&#x8FDB;&#x7A0B;&#x95F4;&#xFF08;inter-process&#xFF09;&#x901A;&#x4FE1;&#x673A;&#x5236;&#x3002;&#x6709;&#x4E24;&#x79CD;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#x65B9;&#x6848;&#x3002;&#x4E00;&#x662F;&#x4F7F;&#x7528;&#x57FA;&#x4E8E;&#x6D88;&#x606F;&#x7684;&#x5F02;&#x6B65;&#x673A;&#x5236;&#x3002;&#x67D0;&#x4E9B;&#x5B9E;&#x73B0;&#x91C7;&#x7528;&#x4E86;&#x6D88;&#x606F;&#x4EE3;&#x7406;&#xFF0C;&#x5982; JMS &#x548C; AMQP&#x3002;&#x5176;&#x4ED6;&#x91C7;&#x7528;&#x65E0;&#x4EE3;&#x7406;&#x7684;&#x65B9;&#x5F0F;&#x76F4;&#x63A5;&#x4E0E;&#x670D;&#x52A1;&#x901A;&#x4FE1;&#xFF0C;&#x5982; Zeromq&#x3002;</p>
<p>&#x53E6;&#x4E00;&#x79CD;&#x7C7B;&#x578B;&#x7684;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#x91C7;&#x7528;&#x4E86;&#x540C;&#x6B65;&#x673A;&#x5236;&#xFF0C;&#x5982; HTTP &#x548C; Thrift&#x3002;&#x7CFB;&#x7EDF;&#x901A;&#x5E38;&#x4F1A;&#x540C;&#x65F6;&#x4F7F;&#x7528;&#x5F02;&#x6B65;&#x548C;&#x540C;&#x6B65;&#x65B9;&#x5F0F;&#x3002;&#x751A;&#x81F3;&#x53EF;&#x4EE5;&#x4E3A;&#x6BCF;&#x79CD;&#x65B9;&#x5F0F;&#x5E94;&#x7528;&#x591A;&#x4E2A;&#x5B9E;&#x73B0;&#x3002;&#x56E0;&#x6B64;&#xFF0C;API &#x7F51;&#x5173;&#x9700;&#x8981;&#x652F;&#x6301;&#x5404;&#x79CD;&#x901A;&#x4FE1;&#x673A;&#x5236;&#x3002;</p>
<p><a id="service-discovery"></a></p>
<h3 id="254&#x3001;&#x670D;&#x52A1;&#x53D1;&#x73B0;">2.5.4&#x3001;&#x670D;&#x52A1;&#x53D1;&#x73B0;</h3>
<p>API &#x7F51;&#x5173;&#x9700;&#x8981;&#x77E5;&#x9053;&#x4E0E;&#x5176;&#x901A;&#x4FE1;&#x7684;&#x6BCF;&#x4E2A;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x4F4D;&#x7F6E;&#xFF08;IP &#x5730;&#x5740;&#x548C;&#x7AEF;&#x53E3;&#xFF09;&#x3002;&#x5728;&#x4F20;&#x7EDF;&#x5E94;&#x7528;&#x4E2D;&#xFF0C;&#x4F60;&#x53EF;&#x4EE5;&#x5C06;&#x8FD9;&#x4E9B;&#x4F4D;&#x7F6E;&#x786C;&#x7F16;&#x7801;&#xFF0C;&#x4F46;&#x5728;&#x73B0;&#x4EE3;&#x57FA;&#x4E8E;&#x4E91;&#x7684;&#x5FAE;&#x670D;&#x52A1;&#x5E94;&#x7528;&#x4E2D;&#xFF0C;&#x627E;&#x5230;&#x6240;&#x9700;&#x7684;&#x4F4D;&#x7F6E;&#x4E0D;&#x662F;&#x4E00;&#x4EF6;&#x7B80;&#x5355;&#x7684;&#x4E8B;&#x60C5;&#x3002;</p>
<p>&#x57FA;&#x7840;&#x8BBE;&#x65BD;&#x670D;&#x52A1;&#xFF08;&#x6BD4;&#x5982;&#x6D88;&#x606F;&#x4EE3;&#x7406;&#xFF09;&#x901A;&#x5E38;&#x90FD;&#x6709;&#x4E00;&#x4E2A;&#x53EF;&#x4EE5;&#x901A;&#x8FC7;&#x7CFB;&#x7EDF;&#x73AF;&#x5883;&#x53D8;&#x91CF;&#x6765;&#x6307;&#x5B9A;&#x7684;&#x9759;&#x6001;&#x4F4D;&#x7F6E;&#x3002;&#x4F46;&#x662F;&#xFF0C;&#x8981;&#x786E;&#x5B9A;&#x5E94;&#x7528;&#x670D;&#x52A1;&#x7684;&#x4F4D;&#x7F6E;&#x5E76;&#x4E0D;&#x662F;&#x90A3;&#x4E48;&#x5BB9;&#x6613;&#x3002;</p>
<p>&#x5E94;&#x7528;&#x670D;&#x52A1;&#x53EF;&#x4EE5;&#x52A8;&#x6001;&#x5206;&#x914D;&#x4F4D;&#x7F6E;&#x3002;&#x6B64;&#x5916;&#xFF0C;&#x7531;&#x4E8E;&#x81EA;&#x52A8;&#x6269;&#x7F29;&#x548C;&#x5347;&#x7EA7;&#xFF0C;&#x4E00;&#x4E2A;&#x670D;&#x52A1;&#x7684;&#x6574;&#x7EC4;&#x5B9E;&#x4F8B;&#x53EF;&#x4EE5;&#x52A8;&#x6001;&#x53D8;&#x66F4;&#x3002;&#x56E0;&#x6B64;&#xFF0C;API &#x7F51;&#x5173;&#x4E0E;&#x7CFB;&#x7EDF;&#x4E2D;&#x7684;&#x4EFB;&#x4F55;&#x5176;&#x4ED6;&#x670D;&#x52A1;&#x5BA2;&#x6237;&#x7AEF;&#x4E00;&#x6837;&#xFF0C;&#x9700;&#x8981;&#x4F7F;&#x7528;&#x7CFB;&#x7EDF;&#x7684;&#x670D;&#x52A1;&#x53D1;&#x73B0;&#x673A;&#x5236;&#xFF1A;<a href="http://microservices.io/patterns/server-side-discovery.html" target="_blank">&#x670D;&#x52A1;&#x7AEF;&#x53D1;&#x73B0;</a>&#x6216;<a href="http://microservices.io/patterns/client-side-discovery.html" target="_blank">&#x5BA2;&#x6237;&#x7AEF;&#x53D1;&#x73B0;</a>&#x3002;<a href="4-service-discovery.html">&#x7B2C;&#x56DB;&#x7AE0;</a>&#x4E2D;&#x66F4;&#x8BE6;&#x7EC6;&#x5730;&#x63CF;&#x8FF0;&#x4E86;&#x670D;&#x52A1;&#x53D1;&#x73B0;&#x3002;&#x73B0;&#x5728;&#x9700;&#x8981;&#x6CE8;&#x610F;&#x7684;&#x662F;&#xFF0C;&#x5982;&#x679C;&#x7CFB;&#x7EDF;&#x4F7F;&#x7528;&#x5BA2;&#x6237;&#x7AEF;&#x53D1;&#x73B0;&#xFF0C;API &#x7F51;&#x5173;&#x5FC5;&#x987B;&#x80FD;&#x591F;&#x67E5;&#x8BE2;<a href="http://microservices.io/patterns/service-registry.html" target="_blank">&#x670D;&#x52A1;&#x6CE8;&#x518C;&#x4E2D;&#x5FC3;</a>&#xFF0C;&#x6CE8;&#x518C;&#x4E2D;&#x5FC3;&#x662F;&#x6240;&#x6709;&#x5FAE;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x53CA;&#x5176;&#x4F4D;&#x7F6E;&#x7684;&#x6570;&#x636E;&#x5E93;&#x3002;</p>
<p><a id="handling-partial-failures"></a></p>
<h3 id="255&#x3001;&#x5904;&#x7406;&#x5C40;&#x90E8;&#x6545;&#x969C;">2.5.5&#x3001;&#x5904;&#x7406;&#x5C40;&#x90E8;&#x6545;&#x969C;</h3>
<p>&#x5B9E;&#x73B0; API &#x7F51;&#x5173;&#x65F6;&#x5FC5;&#x987B;&#x89E3;&#x51B3;&#x7684;&#x53E6;&#x4E00;&#x4E2A;&#x95EE;&#x9898;&#x662F;&#x5C40;&#x90E8;&#x6545;&#x969C;&#x95EE;&#x9898;&#x3002;&#x5F53;&#x4E00;&#x4E2A;&#x670D;&#x52A1;&#x8C03;&#x7528;&#x53E6;&#x4E00;&#x4E2A;&#x54CD;&#x5E94;&#x7F13;&#x6162;&#x6216;&#x8005;&#x4E0D;&#x53EF;&#x7528;&#x7684;&#x670D;&#x52A1;&#x65F6;&#xFF0C;&#x6240;&#x6709;&#x5206;&#x5E03;&#x5F0F;&#x7CFB;&#x7EDF;&#x90FD;&#x4F1A;&#x51FA;&#x73B0;&#x6B64;&#x95EE;&#x9898;&#x3002;API &#x7F51;&#x5173;&#x4E0D;&#x5E94;&#x8BE5;&#x65E0;&#x671F;&#x9650;&#x5730;&#x7B49;&#x5F85;&#x4E0B;&#x6E38;&#x670D;&#x52A1;&#x3002;&#x4F46;&#x662F;&#xFF0C;&#x5982;&#x4F55;&#x5904;&#x7406;&#x6545;&#x969C;&#x53D6;&#x51B3;&#x4E8E;&#x7279;&#x5B9A;&#x7684;&#x65B9;&#x6848;&#x548C;&#x54EA;&#x4E9B;&#x670D;&#x52A1;&#x53D1;&#x751F;&#x6545;&#x969C;&#x3002;&#x4F8B;&#x5982;&#xFF0C;&#x5982;&#x679C;&#x63A8;&#x8350;&#x670D;&#x52A1;&#x5728;&#x83B7;&#x53D6;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x65F6;&#x6CA1;&#x6709;&#x54CD;&#x5E94;&#xFF0C;API &#x7F51;&#x5173;&#x5E94;&#x5C06;&#x5176;&#x4F59;&#x7684;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x8FD4;&#x56DE;&#x7ED9;&#x5BA2;&#x6237;&#x7AEF;&#xFF0C;&#x56E0;&#x4E3A;&#x8FD9;&#x4E9B;&#x4FE1;&#x606F;&#x5BF9;&#x7528;&#x6237;&#x4ECD;&#x7136;&#x6709;&#x7528;&#x3002;&#x5EFA;&#x8BAE;&#x53EF;&#x4EE5;&#x662F;&#x7A7A;&#x7684;&#xFF0C;&#x4E5F;&#x53EF;&#x4EE5;&#x7528;&#x5176;&#x5B83;&#x5185;&#x5BB9;&#x4EE3;&#x66FF;&#xFF0C;&#x4F8B;&#x5982;&#x786C;&#x7F16;&#x7801;&#x7684;&#x5341;&#x5F3A;&#x6392;&#x884C;&#x540D;&#x5355;&#x3002;&#x7136;&#x800C;&#xFF0C;&#x5982;&#x679C;&#x4EA7;&#x54C1;&#x4FE1;&#x606F;&#x670D;&#x52A1;&#x6CA1;&#x6709;&#x54CD;&#x5E94;&#xFF0C;&#x90A3;&#x4E48; API &#x7F51;&#x5173;&#x5E94;&#x8BE5;&#x5411;&#x5BA2;&#x6237;&#x7AEF;&#x8FD4;&#x56DE;&#x9519;&#x8BEF;&#x3002;</p>
<p>&#x5982;&#x679C;&#x53EF;&#x4EE5;&#xFF0C;API &#x7F51;&#x5173;&#x8FD8;&#x53EF;&#x4EE5;&#x8FD4;&#x56DE;&#x7F13;&#x5B58;&#x6570;&#x636E;&#x3002;&#x4F8B;&#x5982;&#xFF0C;&#x7531;&#x4E8E;&#x4EA7;&#x54C1;&#x4EF7;&#x683C;&#x53D8;&#x5316;&#x4E0D;&#x5927;&#xFF0C;&#x5F53;&#x4EF7;&#x683C;&#x670D;&#x52A1;&#x4E0D;&#x53EF;&#x7528;&#x65F6;&#xFF0C;API &#x7F51;&#x5173;&#x53EF;&#x4EE5;&#x8FD4;&#x56DE;&#x88AB;&#x7F13;&#x5B58;&#x7684;&#x4EF7;&#x683C;&#x6570;&#x636E;&#x3002;&#x6570;&#x636E;&#x53EF;&#x4EE5;&#x7531; API &#x7F51;&#x5173;&#x7F13;&#x5B58;&#x6216;&#x5B58;&#x50A8;&#x5728;&#x5916;&#x90E8;&#x7F13;&#x5B58;&#x4E2D;&#xFF0C;&#x5982; Redis &#x6216; Memcached&#x3002;API &#x7F51;&#x5173;&#x901A;&#x8FC7;&#x8FD4;&#x56DE;&#x9ED8;&#x8BA4;&#x6570;&#x636E;&#x6216;&#x7F13;&#x5B58;&#x6570;&#x636E;&#xFF0C;&#x786E;&#x4FDD;&#x7CFB;&#x7EDF;&#x53D1;&#x751F;&#x6545;&#x969C;&#x65F6;&#x6700;&#x5C0F;&#x7A0B;&#x5EA6;&#x4E0A;&#x5F71;&#x54CD;&#x5230;&#x7528;&#x6237;&#x4F53;&#x9A8C;&#x3002;</p>
<p><a href="https://github.com/Netflix/Hystrix" target="_blank">Netflix Hystrix</a> &#x662F;&#x4E00;&#x4E2A;&#x975E;&#x5E38;&#x6709;&#x7528;&#x7684;&#x5E93;&#xFF0C;&#x7528;&#x4E8E;&#x7F16;&#x5199;&#x8C03;&#x7528;&#x8FDC;&#x7A0B;&#x670D;&#x52A1;&#x4EE3;&#x7801;&#x3002;Hystrix &#x53EF;&#x4EE5;&#x4F7F;&#x8D85;&#x51FA;&#x6307;&#x5B9A;&#x9608;&#x503C;&#x7684;&#x8C03;&#x7528;&#x8D85;&#x65F6;&#x3002;&#x5B83;&#x5B9E;&#x73B0;&#x4E86;&#x65AD;&#x8DEF;&#x5668;&#x6A21;&#x5F0F;&#xFF0C;&#x9632;&#x6B62;&#x5BA2;&#x6237;&#x7AEF;&#x4E0D;&#x5FC5;&#x8981;&#x5730;&#x7B49;&#x5F85;&#x65E0;&#x54CD;&#x5E94;&#x7684;&#x670D;&#x52A1;&#x3002;&#x5982;&#x679C;&#x670D;&#x52A1;&#x7684;&#x9519;&#x8BEF;&#x7387;&#x8D85;&#x8FC7;&#x6307;&#x5B9A;&#x9608;&#x503C;&#xFF0C;Hystrix &#x5C06;&#x4F1A;&#x8DF3;&#x95F8;&#xFF0C;&#x6240;&#x6709;&#x8BF7;&#x6C42;&#x5C06;&#x5728;&#x6307;&#x5B9A;&#x7684;&#x65F6;&#x95F4;&#x5185;&#x7ACB;&#x5373;&#x5931;&#x8D25;&#x3002;Hystrix &#x5141;&#x8BB8;&#x4F60;&#x5728;&#x8BF7;&#x6C42;&#x5931;&#x8D25;&#x65F6;&#x5B9A;&#x4E49;&#x56DE;&#x9000;&#x64CD;&#x4F5C;&#xFF0C;&#x4F8B;&#x5982;&#x4ECE;&#x7F13;&#x5B58;&#x8BFB;&#x53D6;&#x6216;&#x8FD4;&#x56DE;&#x9ED8;&#x8BA4;&#x503C;&#x3002;&#x5982;&#x679C;&#x4F60;&#x6B63;&#x5728;&#x4F7F;&#x7528; JVM&#xFF0C;&#x90A3;&#x4E48;&#x4F60;&#x4E00;&#x5B9A;&#x8981;&#x8003;&#x8651;&#x4F7F;&#x7528; Hystrix&#x3002;&#x5982;&#x679C;&#x4F60;&#x662F;&#x5728;&#x975E; JVM &#x73AF;&#x5883;&#x4E2D;&#x8FD0;&#x884C;&#xFF0C;&#x5219;&#x5E94;&#x4F7F;&#x7528;&#x76F8;&#x540C;&#x529F;&#x80FD;&#x7684;&#x5E93;&#x3002;</p>
<p><a id="summary"></a></p>
<h2 id="26&#x3001;&#x603B;&#x7ED3;">2.6&#x3001;&#x603B;&#x7ED3;</h2>
<p>&#x5BF9;&#x4E8E;&#x5927;&#x591A;&#x6570;&#x57FA;&#x4E8E;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x5E94;&#x7528;&#x6765;&#x8BF4;&#xFF0C;&#x5B9E;&#x73B0;&#x4E00;&#x4E2A; API &#x7F51;&#x5173;&#x662F;&#x5F88;&#x6709;&#x5FC5;&#x8981;&#x7684;&#xFF0C;API &#x7F51;&#x5173;&#x4F5C;&#x4E3A;&#x7CFB;&#x7EDF;&#x7684;&#x5355;&#x5165;&#x53E3;&#x70B9;&#xFF0C;&#x5E76;&#x4E14;&#x8D1F;&#x8D23;&#x8BF7;&#x6C42;&#x8DEF;&#x7531;&#xFF0C;&#x7EC4;&#x5408;&#x548C;&#x534F;&#x8BAE;&#x8F6C;&#x6362;&#x3002;&#x5B83;&#x4E3A;&#x6BCF;&#x4E2A;&#x5E94;&#x7528;&#x5BA2;&#x6237;&#x7AEF;&#x63D0;&#x4F9B;&#x4E86;&#x4E00;&#x4E2A;&#x81EA;&#x5B9A;&#x4E49; API&#x3002;API &#x7F51;&#x5173;&#x8FD8;&#x53EF;&#x4EE5;&#x901A;&#x8FC7;&#x8FD4;&#x56DE;&#x7F13;&#x5B58;&#x6216;&#x9ED8;&#x8BA4;&#x6570;&#x636E;&#x6765;&#x63A9;&#x76D6;&#x540E;&#x7AEF;&#x670D;&#x52A1;&#x6545;&#x969C;&#x3002;&#x5728;&#x4E0B;&#x4E00;&#x7AE0;&#x4E2D;&#xFF0C;&#x6211;&#x4EEC;&#x5C06;&#x4ECB;&#x7ECD;&#x670D;&#x52A1;&#x95F4;&#x7684;&#x901A;&#x4FE1;&#x3002;</p>
<p><a id="microservices-in-action"></a></p>
<h2 id="&#x5FAE;&#x670D;&#x52A1;&#x5B9E;&#x6218;&#xFF1A;nginx-plus-&#x4F5C;&#x4E3A;-api-&#x7F51;&#x5173;">&#x5FAE;&#x670D;&#x52A1;&#x5B9E;&#x6218;&#xFF1A;NGINX Plus &#x4F5C;&#x4E3A; API &#x7F51;&#x5173;</h2>
<p>by Floyd Smith</p>
<p>&#x672C;&#x7AE0;&#x8BA8;&#x8BBA;&#x4E86;&#x5982;&#x4F55;&#x5C06; API &#x7F51;&#x5173;&#x4F5C;&#x4E3A;&#x7CFB;&#x7EDF;&#x7684;&#x5355;&#x5165;&#x53E3;&#x70B9;&#x3002;&#x5B83;&#x53EF;&#x4EE5;&#x5904;&#x7406;&#x8BF8;&#x5982;&#x8D1F;&#x8F7D;&#x5747;&#x8861;&#x3001;&#x7F13;&#x5B58;&#x3001;&#x76D1;&#x63A7;&#x548C;&#x534F;&#x8BAE;&#x8F6C;&#x6362;&#x7B49;&#x5176;&#x4ED6;&#x529F;&#x80FD; &#x2014;&#x2014; &#x5F53; NGINX &#x5145;&#x5F53;&#x53CD;&#x5411;&#x4EE3;&#x7406;&#x670D;&#x52A1;&#x5668;&#x65F6;&#xFF0C;&#x5176;&#x53EF;&#x4EE5;&#x4F5C;&#x4E3A;&#x7CFB;&#x7EDF;&#x7684;&#x5355;&#x5165;&#x53E3;&#x70B9;&#xFF0C;&#x5E76;&#x4E14;&#x652F;&#x6301;&#x6240;&#x6709;&#x63D0;&#x5230;&#x7684;&#x4E00;&#x4E2A; API &#x7F51;&#x5173;&#x5177;&#x6709;&#x7684;&#x9644;&#x52A0;&#x529F;&#x80FD;&#x3002;&#x56E0;&#x6B64;&#x4F7F;&#x7528; NGINX &#x4F5C;&#x4E3A; API &#x7F51;&#x5173;&#x7684;&#x4E3B;&#x673A;&#x53EF;&#x4EE5;&#x5F88;&#x597D;&#x5730;&#x5DE5;&#x4F5C;&#x3002;</p>
<p>&#x5C06; NGINX &#x4F5C;&#x4E3A; API &#x7F51;&#x5173;&#x5E76;&#x4E0D;&#x662F;&#x672C;&#x4E66;&#x6700;&#x5F00;&#x59CB;&#x7684;&#x60F3;&#x6CD5;&#x3002;<a href="https://www.nginx.com/products/" target="_blank">NGINX Plus</a> &#x662F;&#x4E00;&#x4E2A;&#x7528;&#x4E8E;&#x7BA1;&#x7406;&#x548C;&#x4FDD;&#x62A4;&#x57FA;&#x4E8E; HTTP &#x7684; API &#x6D41;&#x91CF;&#x7684;&#x9886;&#x5148;&#x5E73;&#x53F0;&#x3002;&#x4F60;&#x53EF;&#x4EE5;&#x5B9E;&#x73B0;&#x81EA;&#x5DF1;&#x7684; API &#x7F51;&#x5173;&#x6216;&#x4F7F;&#x7528;&#x73B0;&#x6709;&#x7684; API &#x7BA1;&#x7406;&#x5E73;&#x53F0;&#xFF0C;&#x5176;&#x4E2D;&#x8BB8;&#x591A;&#x4F7F;&#x7528;&#x4E86; NGINX&#x3002;</p>
<p>&#x4F7F;&#x7528; NGINX Plus &#x4F5C;&#x4E3A; <a href="https://www.nginx.com/solutions/api-gateway/" target="_blank">API &#x7F51;&#x5173;</a>&#x7684;&#x7406;&#x7531;&#x5305;&#x62EC;&#xFF1A;</p>
<ul>
<li><p><strong>&#x8BBF;&#x95EE;&#x7BA1;&#x7406;</strong></p>
<p> &#x4E0A;&#x81F3; Web &#x5E94;&#x7528;&#x7EA7;&#x522B;&#xFF0C;&#x4E0B;&#x81F3;&#x6BCF;&#x4E2A;&#x4E2A;&#x4F53;&#x5FAE;&#x670D;&#x52A1;&#x7EA7;&#x522B;&#xFF0C;&#x4F60;&#x90FD;&#x53EF;&#x4EE5;&#x4F7F;&#x7528;&#x5404;&#x79CD;&#x8BBF;&#x95EE;&#x63A7;&#x5236;&#x5217;&#x8868;&#xFF08;ACL&#xFF09;&#x65B9;&#x6CD5;&#xFF0C;&#x5E76;&#x4E14;&#x53EF;&#x4EE5;&#x8F7B;&#x677E;&#x5B9E;&#x73B0; SSL/TLS&#x3002;</p>
</li>
<li><p><strong>&#x53EF;&#x7BA1;&#x7406;&#x6027;&#x4E0E;&#x4F38;&#x7F29;&#x6027;</strong></p>
<p> &#x4F60;&#x53EF;&#x4EE5;&#x4F7F;&#x7528; NGINX &#x7684;&#x52A8;&#x6001;&#x91CD;&#x65B0;&#x914D;&#x7F6E; API&#x3001;Lua &#x6A21;&#x5757;&#x3001;Perl &#x6765;&#x66F4;&#x65B0;&#x57FA;&#x4E8E; NGINX Plus &#x7684; API &#x670D;&#x52A1;&#x5668;&#xFF0C;&#x4E5F;&#x53EF;&#x4EE5;&#x901A;&#x8FC7; Chef&#x3001;Puppet&#x3001;ZooKeeper &#x6216; DNS &#x6765;&#x6539;&#x53D8;&#x3002;</p>
</li>
<li><p><strong>&#x4E0E;&#x7B2C;&#x4E09;&#x65B9;&#x5DE5;&#x5177;&#x96C6;&#x6210;</strong></p>
<p> NGINX Plus &#x5DF2;&#x7ECF;&#x53EF;&#x4EE5;&#x4E0E;&#x90E8;&#x5206;&#x5148;&#x8FDB;&#x7684;&#x5DE5;&#x5177;&#x96C6;&#x6210;&#x5728;&#x4E00;&#x8D77;&#xFF0C;&#x5982; <a href="https://www.nginx.com/blog/manage-api-gateway-less-3scale-nginx-plus/" target="_blank">3scale</a>&#xFF0C;<a href="https://www.nginx.com/blog/nginx-powers-kong-api-management-solution/" target="_blank">Kong</a> &#x548C; <a href="https://www.nginx.com/blog/mulesoft-implements-nginx-plus/" target="_blank">MuleSoft</a> &#x96C6;&#x6210;&#x5E73;&#x53F0;&#xFF08;&#x4EC5;&#x5217;&#x4E3E;&#x5728; NGINX &#x7F51;&#x7AD9;&#x4E0A;&#x63D0;&#x53CA;&#x7684;&#x5DE5;&#x5177;&#xFF09;&#x3002;</p>
</li>
</ul>
<p>NGINX Plus &#x88AB;&#x5E7F;&#x6CDB;&#x7528;&#x4F5C; <a href="https://www.nginx.com/blog/introducing-the-nginx-microservices-reference-architecture/" target="_blank">NGINX &#x5FAE;&#x670D;&#x52A1;&#x53C2;&#x8003;&#x67B6;&#x6784;</a>&#x4E2D;&#x7684; API &#x7F51;&#x5173;&#x3002;&#x4F60;&#x53EF;&#x4EE5;&#x5229;&#x7528;&#x5728;&#x8FD9;&#x91CC;&#x6536;&#x96C6;&#x7684;&#x5185;&#x5BB9;&#x4EE5;&#x53CA; MRA&#xFF08;&#x5FAE;&#x670D;&#x52A1;&#x53C2;&#x8003;&#x67B6;&#x6784;&#xFF09;&#x6765;&#x4E86;&#x89E3;&#x5982;&#x4F55;&#x5728;&#x4F60;&#x81EA;&#x5DF1;&#x7684;&#x5E94;&#x7528;&#x4E2D;&#x5B9E;&#x73B0;&#x8FD9;&#x4E00;&#x70B9;&#x3002;</p>
<footer class="page-footer"><span class="copyright">Copyright &#xA9; <a style="font-weight: bold" href="http://oopsguy.com" target="_blank">Oopsguy.com</a> 2017 all right reserved&#xFF0C;powered by Gitbook</span><span class="footer-modification">&#x6700;&#x540E;&#x66F4;&#x65B0;&#x65F6;&#x95F4;&#xFF1A;
2019-06-26 19:25:49
</span></footer>
</section>
</div>
</div>
</div>
<a href="1-introduction-to-microservices.html#microservices-in-action" class="navigation navigation-prev " aria-label="Previous page: 微服务实战：NGINX Plus 作为反向代理服务器">
<i class="fa fa-angle-left"></i>
</a>
<a href="2-using-an-api-gateway.html#introduction" class="navigation navigation-next " aria-label="Next page: 2.1、简介">
<i class="fa fa-angle-right"></i>
</a>
</div>
<script>
var gitbook = gitbook || [];
gitbook.push(function() {
gitbook.page.hasChanged({"page":{"title":"2、使用 API 网关","level":"1.4","depth":1,"next":{"title":"2.1、简介","level":"1.4.1","depth":2,"anchor":"#introduction","path":"2-using-an-api-gateway.md","ref":"2-using-an-api-gateway.md#introduction","articles":[]},"previous":{"title":"微服务实战：NGINX Plus 作为反向代理服务器","level":"1.3.7","depth":2,"anchor":"#microservices-in-action","path":"1-introduction-to-microservices.md","ref":"1-introduction-to-microservices.md#microservices-in-action","articles":[]},"dir":"ltr"},"config":{"plugins":["github","splitter","tbfed-pagefooter","-lunr","-search","github-buttons","image-captions","-highlight","-livereload","livereload"],"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"pluginsConfig":{"github":{"url":"https://github.com/oopsguy/microservices-from-design-to-deployment-chinese"},"tbfed-pagefooter":{"copyright":"Copyright &copy <a style=\"font-weight: bold\" href=\"http://oopsguy.com\">Oopsguy.com</a> 2017","modify_label":"最后更新时间：","modify_format":"YYYY-MM-DD HH:mm:ss"},"github-buttons":{"repo":"oopsguy/microservices-from-design-to-deployment-chinese","types":["star","watch"],"size":"small"},"image-captions":{"caption":"_CAPTION_","variable_name":"_pictures"},"splitter":{},"sharing":{"facebook":true,"twitter":true,"google":false,"weibo":false,"instapaper":false,"vk":false,"all":["facebook","google","twitter","weibo","instapaper"]},"fontsettings":{"theme":"white","family":"sans","size":2},"theme-default":{"styles":{"website":"styles/website.css","pdf":"styles/pdf.css","epub":"styles/epub.css","mobi":"styles/mobi.css","ebook":"styles/ebook.css","print":"styles/print.css"},"showLevel":false}},"theme":"default","author":"oopsguy.com","pdf":{"pageNumbers":true,"fontSize":16,"fontFamily":"Microsoft yahei","paperSize":"a4","chapterMark":"pagebreak","pageBreaksBefore":"/","margin":{"right":62,"left":62,"top":36,"bottom":36}},"structure":{"langs":"LANGS.md","readme":"README.md","glossary":"GLOSSARY.md","summary":"SUMMARY.md"},"variables":{"_pictures":[{"backlink":"1-introduction-to-microservices.html#fig1.3.1","level":"1.3","list_caption":"Figure: 图 1-1、一个简单的打车应用","alt":"图 1-1、一个简单的打车应用","nro":1,"url":"resources/1-1.png","index":1,"caption_template":"_CAPTION_","label":"图 1-1、一个简单的打车应用","attributes":{},"skip":false,"key":"1.3.1"},{"backlink":"1-introduction-to-microservices.html#fig1.3.2","level":"1.3","list_caption":"Figure: 图 1-2、一个单体应用分解成微服务","alt":"图 1-2、一个单体应用分解成微服务","nro":2,"url":"resources/1-2.png","index":2,"caption_template":"_CAPTION_","label":"图 1-2、一个单体应用分解成微服务","attributes":{},"skip":false,"key":"1.3.2"},{"backlink":"1-introduction-to-microservices.html#fig1.3.3","level":"1.3","list_caption":"Figure: 图 1-3、开发和交付中的伸缩立方（Scale Cube）","alt":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","nro":3,"url":"resources/1-3.png","index":3,"caption_template":"_CAPTION_","label":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","attributes":{},"skip":false,"key":"1.3.3"},{"backlink":"1-introduction-to-microservices.html#fig1.3.4","level":"1.3","list_caption":"Figure: 图 1-4、使用 Docker 部署 Trip Management 服务","alt":"图 1-4、使用 Docker 部署 Trip Management 服务","nro":4,"url":"resources/1-4.png","index":4,"caption_template":"_CAPTION_","label":"图 1-4、使用 Docker 部署 Trip Management 服务","attributes":{},"skip":false,"key":"1.3.4"},{"backlink":"1-introduction-to-microservices.html#fig1.3.5","level":"1.3","list_caption":"Figure: 图 1-5、打车应用的数据库架构","alt":"图 1-5、打车应用的数据库架构","nro":5,"url":"resources/1-5.png","index":5,"caption_template":"_CAPTION_","label":"图 1-5、打车应用的数据库架构","attributes":{},"skip":false,"key":"1.3.5"},{"backlink":"1-introduction-to-microservices.html#building-monolithic-applications#fig1.3.1.1","level":"1.3.1","list_caption":"Figure: 图 1-1、一个简单的打车应用","alt":"图 1-1、一个简单的打车应用","nro":6,"url":"resources/1-1.png","index":1,"caption_template":"_CAPTION_","label":"图 1-1、一个简单的打车应用","attributes":{},"skip":false,"key":"1.3.1.1"},{"backlink":"1-introduction-to-microservices.html#building-monolithic-applications#fig1.3.1.2","level":"1.3.1","list_caption":"Figure: 图 1-2、一个单体应用分解成微服务","alt":"图 1-2、一个单体应用分解成微服务","nro":7,"url":"resources/1-2.png","index":2,"caption_template":"_CAPTION_","label":"图 1-2、一个单体应用分解成微服务","attributes":{},"skip":false,"key":"1.3.1.2"},{"backlink":"1-introduction-to-microservices.html#building-monolithic-applications#fig1.3.1.3","level":"1.3.1","list_caption":"Figure: 图 1-3、开发和交付中的伸缩立方（Scale Cube）","alt":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","nro":8,"url":"resources/1-3.png","index":3,"caption_template":"_CAPTION_","label":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","attributes":{},"skip":false,"key":"1.3.1.3"},{"backlink":"1-introduction-to-microservices.html#building-monolithic-applications#fig1.3.1.4","level":"1.3.1","list_caption":"Figure: 图 1-4、使用 Docker 部署 Trip Management 服务","alt":"图 1-4、使用 Docker 部署 Trip Management 服务","nro":9,"url":"resources/1-4.png","index":4,"caption_template":"_CAPTION_","label":"图 1-4、使用 Docker 部署 Trip Management 服务","attributes":{},"skip":false,"key":"1.3.1.4"},{"backlink":"1-introduction-to-microservices.html#building-monolithic-applications#fig1.3.1.5","level":"1.3.1","list_caption":"Figure: 图 1-5、打车应用的数据库架构","alt":"图 1-5、打车应用的数据库架构","nro":10,"url":"resources/1-5.png","index":5,"caption_template":"_CAPTION_","label":"图 1-5、打车应用的数据库架构","attributes":{},"skip":false,"key":"1.3.1.5"},{"backlink":"1-introduction-to-microservices.html#marching-toward-monolithic-hell#fig1.3.2.1","level":"1.3.2","list_caption":"Figure: 图 1-1、一个简单的打车应用","alt":"图 1-1、一个简单的打车应用","nro":11,"url":"resources/1-1.png","index":1,"caption_template":"_CAPTION_","label":"图 1-1、一个简单的打车应用","attributes":{},"skip":false,"key":"1.3.2.1"},{"backlink":"1-introduction-to-microservices.html#marching-toward-monolithic-hell#fig1.3.2.2","level":"1.3.2","list_caption":"Figure: 图 1-2、一个单体应用分解成微服务","alt":"图 1-2、一个单体应用分解成微服务","nro":12,"url":"resources/1-2.png","index":2,"caption_template":"_CAPTION_","label":"图 1-2、一个单体应用分解成微服务","attributes":{},"skip":false,"key":"1.3.2.2"},{"backlink":"1-introduction-to-microservices.html#marching-toward-monolithic-hell#fig1.3.2.3","level":"1.3.2","list_caption":"Figure: 图 1-3、开发和交付中的伸缩立方（Scale Cube）","alt":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","nro":13,"url":"resources/1-3.png","index":3,"caption_template":"_CAPTION_","label":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","attributes":{},"skip":false,"key":"1.3.2.3"},{"backlink":"1-introduction-to-microservices.html#marching-toward-monolithic-hell#fig1.3.2.4","level":"1.3.2","list_caption":"Figure: 图 1-4、使用 Docker 部署 Trip Management 服务","alt":"图 1-4、使用 Docker 部署 Trip Management 服务","nro":14,"url":"resources/1-4.png","index":4,"caption_template":"_CAPTION_","label":"图 1-4、使用 Docker 部署 Trip Management 服务","attributes":{},"skip":false,"key":"1.3.2.4"},{"backlink":"1-introduction-to-microservices.html#marching-toward-monolithic-hell#fig1.3.2.5","level":"1.3.2","list_caption":"Figure: 图 1-5、打车应用的数据库架构","alt":"图 1-5、打车应用的数据库架构","nro":15,"url":"resources/1-5.png","index":5,"caption_template":"_CAPTION_","label":"图 1-5、打车应用的数据库架构","attributes":{},"skip":false,"key":"1.3.2.5"},{"backlink":"1-introduction-to-microservices.html#tackling-the-complexity#fig1.3.3.1","level":"1.3.3","list_caption":"Figure: 图 1-1、一个简单的打车应用","alt":"图 1-1、一个简单的打车应用","nro":16,"url":"resources/1-1.png","index":1,"caption_template":"_CAPTION_","label":"图 1-1、一个简单的打车应用","attributes":{},"skip":false,"key":"1.3.3.1"},{"backlink":"1-introduction-to-microservices.html#tackling-the-complexity#fig1.3.3.2","level":"1.3.3","list_caption":"Figure: 图 1-2、一个单体应用分解成微服务","alt":"图 1-2、一个单体应用分解成微服务","nro":17,"url":"resources/1-2.png","index":2,"caption_template":"_CAPTION_","label":"图 1-2、一个单体应用分解成微服务","attributes":{},"skip":false,"key":"1.3.3.2"},{"backlink":"1-introduction-to-microservices.html#tackling-the-complexity#fig1.3.3.3","level":"1.3.3","list_caption":"Figure: 图 1-3、开发和交付中的伸缩立方（Scale Cube）","alt":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","nro":18,"url":"resources/1-3.png","index":3,"caption_template":"_CAPTION_","label":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","attributes":{},"skip":false,"key":"1.3.3.3"},{"backlink":"1-introduction-to-microservices.html#tackling-the-complexity#fig1.3.3.4","level":"1.3.3","list_caption":"Figure: 图 1-4、使用 Docker 部署 Trip Management 服务","alt":"图 1-4、使用 Docker 部署 Trip Management 服务","nro":19,"url":"resources/1-4.png","index":4,"caption_template":"_CAPTION_","label":"图 1-4、使用 Docker 部署 Trip Management 服务","attributes":{},"skip":false,"key":"1.3.3.4"},{"backlink":"1-introduction-to-microservices.html#tackling-the-complexity#fig1.3.3.5","level":"1.3.3","list_caption":"Figure: 图 1-5、打车应用的数据库架构","alt":"图 1-5、打车应用的数据库架构","nro":20,"url":"resources/1-5.png","index":5,"caption_template":"_CAPTION_","label":"图 1-5、打车应用的数据库架构","attributes":{},"skip":false,"key":"1.3.3.5"},{"backlink":"1-introduction-to-microservices.html#the-benefits-of-microservices#fig1.3.4.1","level":"1.3.4","list_caption":"Figure: 图 1-1、一个简单的打车应用","alt":"图 1-1、一个简单的打车应用","nro":21,"url":"resources/1-1.png","index":1,"caption_template":"_CAPTION_","label":"图 1-1、一个简单的打车应用","attributes":{},"skip":false,"key":"1.3.4.1"},{"backlink":"1-introduction-to-microservices.html#the-benefits-of-microservices#fig1.3.4.2","level":"1.3.4","list_caption":"Figure: 图 1-2、一个单体应用分解成微服务","alt":"图 1-2、一个单体应用分解成微服务","nro":22,"url":"resources/1-2.png","index":2,"caption_template":"_CAPTION_","label":"图 1-2、一个单体应用分解成微服务","attributes":{},"skip":false,"key":"1.3.4.2"},{"backlink":"1-introduction-to-microservices.html#the-benefits-of-microservices#fig1.3.4.3","level":"1.3.4","list_caption":"Figure: 图 1-3、开发和交付中的伸缩立方（Scale Cube）","alt":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","nro":23,"url":"resources/1-3.png","index":3,"caption_template":"_CAPTION_","label":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","attributes":{},"skip":false,"key":"1.3.4.3"},{"backlink":"1-introduction-to-microservices.html#the-benefits-of-microservices#fig1.3.4.4","level":"1.3.4","list_caption":"Figure: 图 1-4、使用 Docker 部署 Trip Management 服务","alt":"图 1-4、使用 Docker 部署 Trip Management 服务","nro":24,"url":"resources/1-4.png","index":4,"caption_template":"_CAPTION_","label":"图 1-4、使用 Docker 部署 Trip Management 服务","attributes":{},"skip":false,"key":"1.3.4.4"},{"backlink":"1-introduction-to-microservices.html#the-benefits-of-microservices#fig1.3.4.5","level":"1.3.4","list_caption":"Figure: 图 1-5、打车应用的数据库架构","alt":"图 1-5、打车应用的数据库架构","nro":25,"url":"resources/1-5.png","index":5,"caption_template":"_CAPTION_","label":"图 1-5、打车应用的数据库架构","attributes":{},"skip":false,"key":"1.3.4.5"},{"backlink":"1-introduction-to-microservices.html#the-drawbacks-of-microservices#fig1.3.5.1","level":"1.3.5","list_caption":"Figure: 图 1-1、一个简单的打车应用","alt":"图 1-1、一个简单的打车应用","nro":26,"url":"resources/1-1.png","index":1,"caption_template":"_CAPTION_","label":"图 1-1、一个简单的打车应用","attributes":{},"skip":false,"key":"1.3.5.1"},{"backlink":"1-introduction-to-microservices.html#the-drawbacks-of-microservices#fig1.3.5.2","level":"1.3.5","list_caption":"Figure: 图 1-2、一个单体应用分解成微服务","alt":"图 1-2、一个单体应用分解成微服务","nro":27,"url":"resources/1-2.png","index":2,"caption_template":"_CAPTION_","label":"图 1-2、一个单体应用分解成微服务","attributes":{},"skip":false,"key":"1.3.5.2"},{"backlink":"1-introduction-to-microservices.html#the-drawbacks-of-microservices#fig1.3.5.3","level":"1.3.5","list_caption":"Figure: 图 1-3、开发和交付中的伸缩立方（Scale Cube）","alt":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","nro":28,"url":"resources/1-3.png","index":3,"caption_template":"_CAPTION_","label":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","attributes":{},"skip":false,"key":"1.3.5.3"},{"backlink":"1-introduction-to-microservices.html#the-drawbacks-of-microservices#fig1.3.5.4","level":"1.3.5","list_caption":"Figure: 图 1-4、使用 Docker 部署 Trip Management 服务","alt":"图 1-4、使用 Docker 部署 Trip Management 服务","nro":29,"url":"resources/1-4.png","index":4,"caption_template":"_CAPTION_","label":"图 1-4、使用 Docker 部署 Trip Management 服务","attributes":{},"skip":false,"key":"1.3.5.4"},{"backlink":"1-introduction-to-microservices.html#the-drawbacks-of-microservices#fig1.3.5.5","level":"1.3.5","list_caption":"Figure: 图 1-5、打车应用的数据库架构","alt":"图 1-5、打车应用的数据库架构","nro":30,"url":"resources/1-5.png","index":5,"caption_template":"_CAPTION_","label":"图 1-5、打车应用的数据库架构","attributes":{},"skip":false,"key":"1.3.5.5"},{"backlink":"1-introduction-to-microservices.html#summary#fig1.3.6.1","level":"1.3.6","list_caption":"Figure: 图 1-1、一个简单的打车应用","alt":"图 1-1、一个简单的打车应用","nro":31,"url":"resources/1-1.png","index":1,"caption_template":"_CAPTION_","label":"图 1-1、一个简单的打车应用","attributes":{},"skip":false,"key":"1.3.6.1"},{"backlink":"1-introduction-to-microservices.html#summary#fig1.3.6.2","level":"1.3.6","list_caption":"Figure: 图 1-2、一个单体应用分解成微服务","alt":"图 1-2、一个单体应用分解成微服务","nro":32,"url":"resources/1-2.png","index":2,"caption_template":"_CAPTION_","label":"图 1-2、一个单体应用分解成微服务","attributes":{},"skip":false,"key":"1.3.6.2"},{"backlink":"1-introduction-to-microservices.html#summary#fig1.3.6.3","level":"1.3.6","list_caption":"Figure: 图 1-3、开发和交付中的伸缩立方（Scale Cube）","alt":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","nro":33,"url":"resources/1-3.png","index":3,"caption_template":"_CAPTION_","label":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","attributes":{},"skip":false,"key":"1.3.6.3"},{"backlink":"1-introduction-to-microservices.html#summary#fig1.3.6.4","level":"1.3.6","list_caption":"Figure: 图 1-4、使用 Docker 部署 Trip Management 服务","alt":"图 1-4、使用 Docker 部署 Trip Management 服务","nro":34,"url":"resources/1-4.png","index":4,"caption_template":"_CAPTION_","label":"图 1-4、使用 Docker 部署 Trip Management 服务","attributes":{},"skip":false,"key":"1.3.6.4"},{"backlink":"1-introduction-to-microservices.html#summary#fig1.3.6.5","level":"1.3.6","list_caption":"Figure: 图 1-5、打车应用的数据库架构","alt":"图 1-5、打车应用的数据库架构","nro":35,"url":"resources/1-5.png","index":5,"caption_template":"_CAPTION_","label":"图 1-5、打车应用的数据库架构","attributes":{},"skip":false,"key":"1.3.6.5"},{"backlink":"1-introduction-to-microservices.html#microservices-in-action#fig1.3.7.1","level":"1.3.7","list_caption":"Figure: 图 1-1、一个简单的打车应用","alt":"图 1-1、一个简单的打车应用","nro":36,"url":"resources/1-1.png","index":1,"caption_template":"_CAPTION_","label":"图 1-1、一个简单的打车应用","attributes":{},"skip":false,"key":"1.3.7.1"},{"backlink":"1-introduction-to-microservices.html#microservices-in-action#fig1.3.7.2","level":"1.3.7","list_caption":"Figure: 图 1-2、一个单体应用分解成微服务","alt":"图 1-2、一个单体应用分解成微服务","nro":37,"url":"resources/1-2.png","index":2,"caption_template":"_CAPTION_","label":"图 1-2、一个单体应用分解成微服务","attributes":{},"skip":false,"key":"1.3.7.2"},{"backlink":"1-introduction-to-microservices.html#microservices-in-action#fig1.3.7.3","level":"1.3.7","list_caption":"Figure: 图 1-3、开发和交付中的伸缩立方（Scale Cube）","alt":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","nro":38,"url":"resources/1-3.png","index":3,"caption_template":"_CAPTION_","label":"图 1-3、开发和交付中的伸缩立方（Scale Cube）","attributes":{},"skip":false,"key":"1.3.7.3"},{"backlink":"1-introduction-to-microservices.html#microservices-in-action#fig1.3.7.4","level":"1.3.7","list_caption":"Figure: 图 1-4、使用 Docker 部署 Trip Management 服务","alt":"图 1-4、使用 Docker 部署 Trip Management 服务","nro":39,"url":"resources/1-4.png","index":4,"caption_template":"_CAPTION_","label":"图 1-4、使用 Docker 部署 Trip Management 服务","attributes":{},"skip":false,"key":"1.3.7.4"},{"backlink":"1-introduction-to-microservices.html#microservices-in-action#fig1.3.7.5","level":"1.3.7","list_caption":"Figure: 图 1-5、打车应用的数据库架构","alt":"图 1-5、打车应用的数据库架构","nro":40,"url":"resources/1-5.png","index":5,"caption_template":"_CAPTION_","label":"图 1-5、打车应用的数据库架构","attributes":{},"skip":false,"key":"1.3.7.5"},{"backlink":"2-using-an-api-gateway.html#fig1.4.1","level":"1.4","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":41,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.1"},{"backlink":"2-using-an-api-gateway.html#fig1.4.2","level":"1.4","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":42,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.2"},{"backlink":"2-using-an-api-gateway.html#fig1.4.3","level":"1.4","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":43,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.3"},{"backlink":"2-using-an-api-gateway.html#introduction#fig1.4.1.1","level":"1.4.1","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":44,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.1.1"},{"backlink":"2-using-an-api-gateway.html#introduction#fig1.4.1.2","level":"1.4.1","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":45,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.1.2"},{"backlink":"2-using-an-api-gateway.html#introduction#fig1.4.1.3","level":"1.4.1","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":46,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.1.3"},{"backlink":"2-using-an-api-gateway.html#direct-client-to-microservice-communication#fig1.4.2.1","level":"1.4.2","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":47,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.2.1"},{"backlink":"2-using-an-api-gateway.html#direct-client-to-microservice-communication#fig1.4.2.2","level":"1.4.2","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":48,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.2.2"},{"backlink":"2-using-an-api-gateway.html#direct-client-to-microservice-communication#fig1.4.2.3","level":"1.4.2","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":49,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.2.3"},{"backlink":"2-using-an-api-gateway.html#using-an-api-gateway#fig1.4.3.1","level":"1.4.3","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":50,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.3.1"},{"backlink":"2-using-an-api-gateway.html#using-an-api-gateway#fig1.4.3.2","level":"1.4.3","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":51,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.3.2"},{"backlink":"2-using-an-api-gateway.html#using-an-api-gateway#fig1.4.3.3","level":"1.4.3","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":52,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.3.3"},{"backlink":"2-using-an-api-gateway.html#benefits-and-drawbacks-of-an-api-gateway#fig1.4.4.1","level":"1.4.4","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":53,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.4.1"},{"backlink":"2-using-an-api-gateway.html#benefits-and-drawbacks-of-an-api-gateway#fig1.4.4.2","level":"1.4.4","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":54,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.4.2"},{"backlink":"2-using-an-api-gateway.html#benefits-and-drawbacks-of-an-api-gateway#fig1.4.4.3","level":"1.4.4","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":55,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.4.3"},{"backlink":"2-using-an-api-gateway.html#implementing-an-api-gateway#fig1.4.5.1","level":"1.4.5","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":56,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.5.1"},{"backlink":"2-using-an-api-gateway.html#implementing-an-api-gateway#fig1.4.5.2","level":"1.4.5","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":57,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.5.2"},{"backlink":"2-using-an-api-gateway.html#implementing-an-api-gateway#fig1.4.5.3","level":"1.4.5","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":58,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.5.3"},{"backlink":"2-using-an-api-gateway.html#performance-and-scalability#fig1.4.5.1.1","level":"1.4.5.1","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":59,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.5.1.1"},{"backlink":"2-using-an-api-gateway.html#performance-and-scalability#fig1.4.5.1.2","level":"1.4.5.1","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":60,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.5.1.2"},{"backlink":"2-using-an-api-gateway.html#performance-and-scalability#fig1.4.5.1.3","level":"1.4.5.1","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":61,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.5.1.3"},{"backlink":"2-using-an-api-gateway.html#using-a-reactive-programming-model#fig1.4.5.2.1","level":"1.4.5.2","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":62,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.5.2.1"},{"backlink":"2-using-an-api-gateway.html#using-a-reactive-programming-model#fig1.4.5.2.2","level":"1.4.5.2","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":63,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.5.2.2"},{"backlink":"2-using-an-api-gateway.html#using-a-reactive-programming-model#fig1.4.5.2.3","level":"1.4.5.2","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":64,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.5.2.3"},{"backlink":"2-using-an-api-gateway.html#service-invocation#fig1.4.5.3.1","level":"1.4.5.3","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":65,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.5.3.1"},{"backlink":"2-using-an-api-gateway.html#service-invocation#fig1.4.5.3.2","level":"1.4.5.3","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":66,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.5.3.2"},{"backlink":"2-using-an-api-gateway.html#service-invocation#fig1.4.5.3.3","level":"1.4.5.3","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":67,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.5.3.3"},{"backlink":"2-using-an-api-gateway.html#service-discovery#fig1.4.5.4.1","level":"1.4.5.4","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":68,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.5.4.1"},{"backlink":"2-using-an-api-gateway.html#service-discovery#fig1.4.5.4.2","level":"1.4.5.4","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":69,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.5.4.2"},{"backlink":"2-using-an-api-gateway.html#service-discovery#fig1.4.5.4.3","level":"1.4.5.4","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":70,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.5.4.3"},{"backlink":"2-using-an-api-gateway.html#handling-partial-failures#fig1.4.5.5.1","level":"1.4.5.5","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":71,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.5.5.1"},{"backlink":"2-using-an-api-gateway.html#handling-partial-failures#fig1.4.5.5.2","level":"1.4.5.5","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":72,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.5.5.2"},{"backlink":"2-using-an-api-gateway.html#handling-partial-failures#fig1.4.5.5.3","level":"1.4.5.5","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":73,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.5.5.3"},{"backlink":"2-using-an-api-gateway.html#summary#fig1.4.6.1","level":"1.4.6","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":74,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.6.1"},{"backlink":"2-using-an-api-gateway.html#summary#fig1.4.6.2","level":"1.4.6","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":75,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.6.2"},{"backlink":"2-using-an-api-gateway.html#summary#fig1.4.6.3","level":"1.4.6","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":76,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.6.3"},{"backlink":"2-using-an-api-gateway.html#microservices-in-action#fig1.4.7.1","level":"1.4.7","list_caption":"Figure: 图 2-1、一个简单的购物应用","alt":"图 2-1、一个简单的购物应用","nro":77,"url":"resources/2-1.png","index":1,"caption_template":"_CAPTION_","label":"图 2-1、一个简单的购物应用","attributes":{},"skip":false,"key":"1.4.7.1"},{"backlink":"2-using-an-api-gateway.html#microservices-in-action#fig1.4.7.2","level":"1.4.7","list_caption":"Figure: 图 2-2、将移动客户端的需求映射到相关微服务","alt":"图 2-2、将移动客户端的需求映射到相关微服务","nro":78,"url":"resources/2-2.png","index":2,"caption_template":"_CAPTION_","label":"图 2-2、将移动客户端的需求映射到相关微服务","attributes":{},"skip":false,"key":"1.4.7.2"},{"backlink":"2-using-an-api-gateway.html#microservices-in-action#fig1.4.7.3","level":"1.4.7","list_caption":"Figure: 使用 API 网关的微服务","alt":"使用 API 网关的微服务","nro":79,"url":"resources/2-3.png","index":3,"caption_template":"_CAPTION_","label":"使用 API 网关的微服务","attributes":{},"skip":false,"key":"1.4.7.3"},{"backlink":"3-inter-process-communication.html#fig1.5.1","level":"1.5","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":80,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.1"},{"backlink":"3-inter-process-communication.html#fig1.5.2","level":"1.5","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":81,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.2"},{"backlink":"3-inter-process-communication.html#fig1.5.3","level":"1.5","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":82,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.3"},{"backlink":"3-inter-process-communication.html#fig1.5.4","level":"1.5","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":83,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.4"},{"backlink":"3-inter-process-communication.html#fig1.5.5","level":"1.5","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":84,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.5"},{"backlink":"3-inter-process-communication.html#introduction#fig1.5.1.1","level":"1.5.1","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":85,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.1.1"},{"backlink":"3-inter-process-communication.html#introduction#fig1.5.1.2","level":"1.5.1","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":86,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.1.2"},{"backlink":"3-inter-process-communication.html#introduction#fig1.5.1.3","level":"1.5.1","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":87,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.1.3"},{"backlink":"3-inter-process-communication.html#introduction#fig1.5.1.4","level":"1.5.1","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":88,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.1.4"},{"backlink":"3-inter-process-communication.html#introduction#fig1.5.1.5","level":"1.5.1","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":89,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.1.5"},{"backlink":"3-inter-process-communication.html#interaction-styles#fig1.5.2.1","level":"1.5.2","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":90,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.2.1"},{"backlink":"3-inter-process-communication.html#interaction-styles#fig1.5.2.2","level":"1.5.2","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":91,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.2.2"},{"backlink":"3-inter-process-communication.html#interaction-styles#fig1.5.2.3","level":"1.5.2","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":92,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.2.3"},{"backlink":"3-inter-process-communication.html#interaction-styles#fig1.5.2.4","level":"1.5.2","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":93,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.2.4"},{"backlink":"3-inter-process-communication.html#interaction-styles#fig1.5.2.5","level":"1.5.2","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":94,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.2.5"},{"backlink":"3-inter-process-communication.html#defining-apis#fig1.5.3.1","level":"1.5.3","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":95,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.3.1"},{"backlink":"3-inter-process-communication.html#defining-apis#fig1.5.3.2","level":"1.5.3","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":96,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.3.2"},{"backlink":"3-inter-process-communication.html#defining-apis#fig1.5.3.3","level":"1.5.3","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":97,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.3.3"},{"backlink":"3-inter-process-communication.html#defining-apis#fig1.5.3.4","level":"1.5.3","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":98,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.3.4"},{"backlink":"3-inter-process-communication.html#defining-apis#fig1.5.3.5","level":"1.5.3","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":99,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.3.5"},{"backlink":"3-inter-process-communication.html#evolving-apis#fig1.5.4.1","level":"1.5.4","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":100,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.4.1"},{"backlink":"3-inter-process-communication.html#evolving-apis#fig1.5.4.2","level":"1.5.4","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":101,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.4.2"},{"backlink":"3-inter-process-communication.html#evolving-apis#fig1.5.4.3","level":"1.5.4","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":102,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.4.3"},{"backlink":"3-inter-process-communication.html#evolving-apis#fig1.5.4.4","level":"1.5.4","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":103,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.4.4"},{"backlink":"3-inter-process-communication.html#evolving-apis#fig1.5.4.5","level":"1.5.4","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":104,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.4.5"},{"backlink":"3-inter-process-communication.html#handling-partial-failure#fig1.5.5.1","level":"1.5.5","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":105,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.5.1"},{"backlink":"3-inter-process-communication.html#handling-partial-failure#fig1.5.5.2","level":"1.5.5","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":106,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.5.2"},{"backlink":"3-inter-process-communication.html#handling-partial-failure#fig1.5.5.3","level":"1.5.5","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":107,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.5.3"},{"backlink":"3-inter-process-communication.html#handling-partial-failure#fig1.5.5.4","level":"1.5.5","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":108,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.5.4"},{"backlink":"3-inter-process-communication.html#handling-partial-failure#fig1.5.5.5","level":"1.5.5","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":109,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.5.5"},{"backlink":"3-inter-process-communication.html#ipc-technologies#fig1.5.6.1","level":"1.5.6","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":110,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.6.1"},{"backlink":"3-inter-process-communication.html#ipc-technologies#fig1.5.6.2","level":"1.5.6","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":111,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.6.2"},{"backlink":"3-inter-process-communication.html#ipc-technologies#fig1.5.6.3","level":"1.5.6","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":112,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.6.3"},{"backlink":"3-inter-process-communication.html#ipc-technologies#fig1.5.6.4","level":"1.5.6","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":113,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.6.4"},{"backlink":"3-inter-process-communication.html#ipc-technologies#fig1.5.6.5","level":"1.5.6","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":114,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.6.5"},{"backlink":"3-inter-process-communication.html#asynchronous-message-based-communication#fig1.5.7.1","level":"1.5.7","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":115,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.7.1"},{"backlink":"3-inter-process-communication.html#asynchronous-message-based-communication#fig1.5.7.2","level":"1.5.7","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":116,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.7.2"},{"backlink":"3-inter-process-communication.html#asynchronous-message-based-communication#fig1.5.7.3","level":"1.5.7","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":117,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.7.3"},{"backlink":"3-inter-process-communication.html#asynchronous-message-based-communication#fig1.5.7.4","level":"1.5.7","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":118,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.7.4"},{"backlink":"3-inter-process-communication.html#asynchronous-message-based-communication#fig1.5.7.5","level":"1.5.7","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":119,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.7.5"},{"backlink":"3-inter-process-communication.html#synchronous-request-response-ipc#fig1.5.8.1","level":"1.5.8","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":120,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.8.1"},{"backlink":"3-inter-process-communication.html#synchronous-request-response-ipc#fig1.5.8.2","level":"1.5.8","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":121,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.8.2"},{"backlink":"3-inter-process-communication.html#synchronous-request-response-ipc#fig1.5.8.3","level":"1.5.8","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":122,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.8.3"},{"backlink":"3-inter-process-communication.html#synchronous-request-response-ipc#fig1.5.8.4","level":"1.5.8","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":123,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.8.4"},{"backlink":"3-inter-process-communication.html#synchronous-request-response-ipc#fig1.5.8.5","level":"1.5.8","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":124,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.8.5"},{"backlink":"3-inter-process-communication.html#rest#fig1.5.8.1.1","level":"1.5.8.1","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":125,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.8.1.1"},{"backlink":"3-inter-process-communication.html#rest#fig1.5.8.1.2","level":"1.5.8.1","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":126,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.8.1.2"},{"backlink":"3-inter-process-communication.html#rest#fig1.5.8.1.3","level":"1.5.8.1","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":127,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.8.1.3"},{"backlink":"3-inter-process-communication.html#rest#fig1.5.8.1.4","level":"1.5.8.1","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":128,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.8.1.4"},{"backlink":"3-inter-process-communication.html#rest#fig1.5.8.1.5","level":"1.5.8.1","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":129,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.8.1.5"},{"backlink":"3-inter-process-communication.html#thrift#fig1.5.8.2.1","level":"1.5.8.2","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":130,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.8.2.1"},{"backlink":"3-inter-process-communication.html#thrift#fig1.5.8.2.2","level":"1.5.8.2","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":131,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.8.2.2"},{"backlink":"3-inter-process-communication.html#thrift#fig1.5.8.2.3","level":"1.5.8.2","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":132,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.8.2.3"},{"backlink":"3-inter-process-communication.html#thrift#fig1.5.8.2.4","level":"1.5.8.2","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":133,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.8.2.4"},{"backlink":"3-inter-process-communication.html#thrift#fig1.5.8.2.5","level":"1.5.8.2","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":134,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.8.2.5"},{"backlink":"3-inter-process-communication.html#message-formats#fig1.5.9.1","level":"1.5.9","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":135,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.9.1"},{"backlink":"3-inter-process-communication.html#message-formats#fig1.5.9.2","level":"1.5.9","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":136,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.9.2"},{"backlink":"3-inter-process-communication.html#message-formats#fig1.5.9.3","level":"1.5.9","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":137,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.9.3"},{"backlink":"3-inter-process-communication.html#message-formats#fig1.5.9.4","level":"1.5.9","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":138,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.9.4"},{"backlink":"3-inter-process-communication.html#message-formats#fig1.5.9.5","level":"1.5.9","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":139,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.9.5"},{"backlink":"3-inter-process-communication.html#summary#fig1.5.10.1","level":"1.5.10","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":140,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.10.1"},{"backlink":"3-inter-process-communication.html#summary#fig1.5.10.2","level":"1.5.10","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":141,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.10.2"},{"backlink":"3-inter-process-communication.html#summary#fig1.5.10.3","level":"1.5.10","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":142,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.10.3"},{"backlink":"3-inter-process-communication.html#summary#fig1.5.10.4","level":"1.5.10","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":143,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.10.4"},{"backlink":"3-inter-process-communication.html#summary#fig1.5.10.5","level":"1.5.10","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":144,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.10.5"},{"backlink":"3-inter-process-communication.html#microservices-in-action#fig1.5.11.1","level":"1.5.11","list_caption":"Figure: 使用进程间通信交互的微服务","alt":"使用进程间通信交互的微服务","nro":145,"url":"resources/3-1.png","index":1,"caption_template":"_CAPTION_","label":"使用进程间通信交互的微服务","attributes":{},"skip":false,"key":"1.5.11.1"},{"backlink":"3-inter-process-communication.html#microservices-in-action#fig1.5.11.2","level":"1.5.11","list_caption":"Figure: 使用了多种 IPC 机制的服务交互","alt":"使用了多种 IPC 机制的服务交互","nro":146,"url":"resources/3-2.png","index":2,"caption_template":"_CAPTION_","label":"使用了多种 IPC 机制的服务交互","attributes":{},"skip":false,"key":"1.5.11.2"},{"backlink":"3-inter-process-communication.html#microservices-in-action#fig1.5.11.3","level":"1.5.11","list_caption":"Figure: 因无响应服务引起的线程阻塞","alt":"因无响应服务引起的线程阻塞","nro":147,"url":"resources/3-3.png","index":3,"caption_template":"_CAPTION_","label":"因无响应服务引起的线程阻塞","attributes":{},"skip":false,"key":"1.5.11.3"},{"backlink":"3-inter-process-communication.html#microservices-in-action#fig1.5.11.4","level":"1.5.11","list_caption":"Figure: 使用了发布/订阅通道的打车应用","alt":"使用了发布/订阅通道的打车应用","nro":148,"url":"resources/3-4.png","index":4,"caption_template":"_CAPTION_","label":"使用了发布/订阅通道的打车应用","attributes":{},"skip":false,"key":"1.5.11.4"},{"backlink":"3-inter-process-communication.html#microservices-in-action#fig1.5.11.5","level":"1.5.11","list_caption":"Figure: 使用了 RESTful 交互的打车应用","alt":"使用了 RESTful 交互的打车应用","nro":149,"url":"resources/3-5.png","index":5,"caption_template":"_CAPTION_","label":"使用了 RESTful 交互的打车应用","attributes":{},"skip":false,"key":"1.5.11.5"},{"backlink":"4-service-discovery.html#fig1.6.1","level":"1.6","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":150,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.1"},{"backlink":"4-service-discovery.html#fig1.6.2","level":"1.6","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":151,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.2"},{"backlink":"4-service-discovery.html#fig1.6.3","level":"1.6","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":152,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.3"},{"backlink":"4-service-discovery.html#fig1.6.4","level":"1.6","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":153,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.4"},{"backlink":"4-service-discovery.html#fig1.6.5","level":"1.6","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":154,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.5"},{"backlink":"4-service-discovery.html#why-use-service-discovery#fig1.6.1.1","level":"1.6.1","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":155,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.1.1"},{"backlink":"4-service-discovery.html#why-use-service-discovery#fig1.6.1.2","level":"1.6.1","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":156,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.1.2"},{"backlink":"4-service-discovery.html#why-use-service-discovery#fig1.6.1.3","level":"1.6.1","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":157,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.1.3"},{"backlink":"4-service-discovery.html#why-use-service-discovery#fig1.6.1.4","level":"1.6.1","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":158,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.1.4"},{"backlink":"4-service-discovery.html#why-use-service-discovery#fig1.6.1.5","level":"1.6.1","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":159,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.1.5"},{"backlink":"4-service-discovery.html#the-client-side-discovery-pattern#fig1.6.2.1","level":"1.6.2","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":160,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.2.1"},{"backlink":"4-service-discovery.html#the-client-side-discovery-pattern#fig1.6.2.2","level":"1.6.2","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":161,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.2.2"},{"backlink":"4-service-discovery.html#the-client-side-discovery-pattern#fig1.6.2.3","level":"1.6.2","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":162,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.2.3"},{"backlink":"4-service-discovery.html#the-client-side-discovery-pattern#fig1.6.2.4","level":"1.6.2","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":163,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.2.4"},{"backlink":"4-service-discovery.html#the-client-side-discovery-pattern#fig1.6.2.5","level":"1.6.2","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":164,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.2.5"},{"backlink":"4-service-discovery.html#the-server-side-discovery-pattern#fig1.6.3.1","level":"1.6.3","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":165,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.3.1"},{"backlink":"4-service-discovery.html#the-server-side-discovery-pattern#fig1.6.3.2","level":"1.6.3","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":166,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.3.2"},{"backlink":"4-service-discovery.html#the-server-side-discovery-pattern#fig1.6.3.3","level":"1.6.3","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":167,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.3.3"},{"backlink":"4-service-discovery.html#the-server-side-discovery-pattern#fig1.6.3.4","level":"1.6.3","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":168,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.3.4"},{"backlink":"4-service-discovery.html#the-server-side-discovery-pattern#fig1.6.3.5","level":"1.6.3","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":169,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.3.5"},{"backlink":"4-service-discovery.html#the-service-registry#fig1.6.4.1","level":"1.6.4","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":170,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.4.1"},{"backlink":"4-service-discovery.html#the-service-registry#fig1.6.4.2","level":"1.6.4","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":171,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.4.2"},{"backlink":"4-service-discovery.html#the-service-registry#fig1.6.4.3","level":"1.6.4","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":172,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.4.3"},{"backlink":"4-service-discovery.html#the-service-registry#fig1.6.4.4","level":"1.6.4","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":173,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.4.4"},{"backlink":"4-service-discovery.html#the-service-registry#fig1.6.4.5","level":"1.6.4","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":174,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.4.5"},{"backlink":"4-service-discovery.html#service-registration-options#fig1.6.5.1","level":"1.6.5","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":175,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.5.1"},{"backlink":"4-service-discovery.html#service-registration-options#fig1.6.5.2","level":"1.6.5","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":176,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.5.2"},{"backlink":"4-service-discovery.html#service-registration-options#fig1.6.5.3","level":"1.6.5","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":177,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.5.3"},{"backlink":"4-service-discovery.html#service-registration-options#fig1.6.5.4","level":"1.6.5","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":178,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.5.4"},{"backlink":"4-service-discovery.html#service-registration-options#fig1.6.5.5","level":"1.6.5","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":179,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.5.5"},{"backlink":"4-service-discovery.html#the-self-registration-pattern#fig1.6.6.1","level":"1.6.6","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":180,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.6.1"},{"backlink":"4-service-discovery.html#the-self-registration-pattern#fig1.6.6.2","level":"1.6.6","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":181,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.6.2"},{"backlink":"4-service-discovery.html#the-self-registration-pattern#fig1.6.6.3","level":"1.6.6","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":182,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.6.3"},{"backlink":"4-service-discovery.html#the-self-registration-pattern#fig1.6.6.4","level":"1.6.6","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":183,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.6.4"},{"backlink":"4-service-discovery.html#the-self-registration-pattern#fig1.6.6.5","level":"1.6.6","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":184,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.6.5"},{"backlink":"4-service-discovery.html#the-third-party-registration-pattern#fig1.6.7.1","level":"1.6.7","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":185,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.7.1"},{"backlink":"4-service-discovery.html#the-third-party-registration-pattern#fig1.6.7.2","level":"1.6.7","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":186,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.7.2"},{"backlink":"4-service-discovery.html#the-third-party-registration-pattern#fig1.6.7.3","level":"1.6.7","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":187,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.7.3"},{"backlink":"4-service-discovery.html#the-third-party-registration-pattern#fig1.6.7.4","level":"1.6.7","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":188,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.7.4"},{"backlink":"4-service-discovery.html#the-third-party-registration-pattern#fig1.6.7.5","level":"1.6.7","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":189,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.7.5"},{"backlink":"4-service-discovery.html#summary#fig1.6.8.1","level":"1.6.8","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":190,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.8.1"},{"backlink":"4-service-discovery.html#summary#fig1.6.8.2","level":"1.6.8","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":191,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.8.2"},{"backlink":"4-service-discovery.html#summary#fig1.6.8.3","level":"1.6.8","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":192,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.8.3"},{"backlink":"4-service-discovery.html#summary#fig1.6.8.4","level":"1.6.8","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":193,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.8.4"},{"backlink":"4-service-discovery.html#summary#fig1.6.8.5","level":"1.6.8","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":194,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.8.5"},{"backlink":"4-service-discovery.html#microservices-in-action#fig1.6.9.1","level":"1.6.9","list_caption":"Figure: 图 4-1、需要服务寻找帮助的客户端或 API 网关","alt":"图 4-1、需要服务寻找帮助的客户端或 API 网关","nro":195,"url":"resources/4-1.png","index":1,"caption_template":"_CAPTION_","label":"图 4-1、需要服务寻找帮助的客户端或 API 网关","attributes":{},"skip":false,"key":"1.6.9.1"},{"backlink":"4-service-discovery.html#microservices-in-action#fig1.6.9.2","level":"1.6.9","list_caption":"Figure: 客户端可以承担发现服务任务","alt":"客户端可以承担发现服务任务","nro":196,"url":"resources/4-2.png","index":2,"caption_template":"_CAPTION_","label":"客户端可以承担发现服务任务","attributes":{},"skip":false,"key":"1.6.9.2"},{"backlink":"4-service-discovery.html#microservices-in-action#fig1.6.9.3","level":"1.6.9","list_caption":"Figure: 服务器间也可以处理服务发现","alt":"服务器间也可以处理服务发现","nro":197,"url":"resources/4-3.png","index":3,"caption_template":"_CAPTION_","label":"服务器间也可以处理服务发现","attributes":{},"skip":false,"key":"1.6.9.3"},{"backlink":"4-service-discovery.html#microservices-in-action#fig1.6.9.4","level":"1.6.9","list_caption":"Figure: 图 4-4、服务可以自我处理注册","alt":"图 4-4、服务可以自我处理注册","nro":198,"url":"resources/4-4.png","index":4,"caption_template":"_CAPTION_","label":"图 4-4、服务可以自我处理注册","attributes":{},"skip":false,"key":"1.6.9.4"},{"backlink":"4-service-discovery.html#microservices-in-action#fig1.6.9.5","level":"1.6.9","list_caption":"Figure: 图 4-5、一个单独的服务注册器可负责注册其他服务","alt":"图 4-5、一个单独的服务注册器可负责注册其他服务","nro":199,"url":"resources/4-5.png","index":5,"caption_template":"_CAPTION_","label":"图 4-5、一个单独的服务注册器可负责注册其他服务","attributes":{},"skip":false,"key":"1.6.9.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#fig1.7.1","level":"1.7","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":200,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#fig1.7.2","level":"1.7","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":201,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#fig1.7.3","level":"1.7","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":202,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#fig1.7.4","level":"1.7","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":203,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#fig1.7.5","level":"1.7","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":204,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#fig1.7.6","level":"1.7","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":205,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#fig1.7.7","level":"1.7","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":206,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#fig1.7.8","level":"1.7","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":207,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.8"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management#fig1.7.1.1","level":"1.7.1","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":208,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.1.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management#fig1.7.1.2","level":"1.7.1","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":209,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.1.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management#fig1.7.1.3","level":"1.7.1","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":210,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.1.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management#fig1.7.1.4","level":"1.7.1","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":211,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.1.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management#fig1.7.1.5","level":"1.7.1","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":212,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.1.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management#fig1.7.1.6","level":"1.7.1","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":213,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.1.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management#fig1.7.1.7","level":"1.7.1","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":214,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.1.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-and-the-problem-of-distributed-data-management#fig1.7.1.8","level":"1.7.1","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":215,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.1.8"},{"backlink":"5-event-driven-data-management-for-microservices.html#event-driven-architecture#fig1.7.2.1","level":"1.7.2","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":216,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.2.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#event-driven-architecture#fig1.7.2.2","level":"1.7.2","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":217,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.2.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#event-driven-architecture#fig1.7.2.3","level":"1.7.2","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":218,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.2.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#event-driven-architecture#fig1.7.2.4","level":"1.7.2","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":219,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.2.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#event-driven-architecture#fig1.7.2.5","level":"1.7.2","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":220,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.2.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#event-driven-architecture#fig1.7.2.6","level":"1.7.2","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":221,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.2.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#event-driven-architecture#fig1.7.2.7","level":"1.7.2","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":222,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.2.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#event-driven-architecture#fig1.7.2.8","level":"1.7.2","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":223,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.2.8"},{"backlink":"5-event-driven-data-management-for-microservices.html#achieving-atomicity#fig1.7.3.1","level":"1.7.3","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":224,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.3.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#achieving-atomicity#fig1.7.3.2","level":"1.7.3","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":225,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.3.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#achieving-atomicity#fig1.7.3.3","level":"1.7.3","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":226,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.3.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#achieving-atomicity#fig1.7.3.4","level":"1.7.3","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":227,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.3.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#achieving-atomicity#fig1.7.3.5","level":"1.7.3","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":228,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.3.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#achieving-atomicity#fig1.7.3.6","level":"1.7.3","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":229,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.3.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#achieving-atomicity#fig1.7.3.7","level":"1.7.3","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":230,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.3.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#achieving-atomicity#fig1.7.3.8","level":"1.7.3","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":231,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.3.8"},{"backlink":"5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions#fig1.7.4.1","level":"1.7.4","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":232,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.4.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions#fig1.7.4.2","level":"1.7.4","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":233,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.4.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions#fig1.7.4.3","level":"1.7.4","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":234,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.4.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions#fig1.7.4.4","level":"1.7.4","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":235,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.4.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions#fig1.7.4.5","level":"1.7.4","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":236,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.4.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions#fig1.7.4.6","level":"1.7.4","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":237,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.4.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions#fig1.7.4.7","level":"1.7.4","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":238,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.4.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#publishing-events-using-local-transactions#fig1.7.4.8","level":"1.7.4","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":239,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.4.8"},{"backlink":"5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log#fig1.7.5.1","level":"1.7.5","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":240,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.5.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log#fig1.7.5.2","level":"1.7.5","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":241,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.5.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log#fig1.7.5.3","level":"1.7.5","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":242,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.5.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log#fig1.7.5.4","level":"1.7.5","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":243,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.5.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log#fig1.7.5.5","level":"1.7.5","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":244,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.5.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log#fig1.7.5.6","level":"1.7.5","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":245,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.5.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log#fig1.7.5.7","level":"1.7.5","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":246,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.5.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#mining-a-database-transaction-log#fig1.7.5.8","level":"1.7.5","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":247,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.5.8"},{"backlink":"5-event-driven-data-management-for-microservices.html#using-event-sourcing#fig1.7.6.1","level":"1.7.6","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":248,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.6.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#using-event-sourcing#fig1.7.6.2","level":"1.7.6","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":249,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.6.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#using-event-sourcing#fig1.7.6.3","level":"1.7.6","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":250,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.6.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#using-event-sourcing#fig1.7.6.4","level":"1.7.6","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":251,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.6.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#using-event-sourcing#fig1.7.6.5","level":"1.7.6","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":252,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.6.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#using-event-sourcing#fig1.7.6.6","level":"1.7.6","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":253,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.6.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#using-event-sourcing#fig1.7.6.7","level":"1.7.6","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":254,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.6.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#using-event-sourcing#fig1.7.6.8","level":"1.7.6","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":255,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.6.8"},{"backlink":"5-event-driven-data-management-for-microservices.html#summary#fig1.7.7.1","level":"1.7.7","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":256,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.7.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#summary#fig1.7.7.2","level":"1.7.7","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":257,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.7.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#summary#fig1.7.7.3","level":"1.7.7","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":258,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.7.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#summary#fig1.7.7.4","level":"1.7.7","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":259,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.7.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#summary#fig1.7.7.5","level":"1.7.7","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":260,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.7.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#summary#fig1.7.7.6","level":"1.7.7","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":261,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.7.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#summary#fig1.7.7.7","level":"1.7.7","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":262,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.7.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#summary#fig1.7.7.8","level":"1.7.7","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":263,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.7.8"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-in-action#fig1.7.8.1","level":"1.7.8","list_caption":"Figure: 图 5-1、每个微服务都有各自的数据","alt":"图 5-1、每个微服务都有各自的数据","nro":264,"url":"./resources/5-1.png","index":1,"caption_template":"_CAPTION_","label":"图 5-1、每个微服务都有各自的数据","attributes":{},"skip":false,"key":"1.7.8.1"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-in-action#fig1.7.8.2","level":"1.7.8","list_caption":"Figure: 图 5-2、Order Service 发布一个事件","alt":"图 5-2、Order Service 发布一个事件","nro":265,"url":"resources/5-2.png","index":2,"caption_template":"_CAPTION_","label":"图 5-2、Order Service 发布一个事件","attributes":{},"skip":false,"key":"1.7.8.2"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-in-action#fig1.7.8.3","level":"1.7.8","list_caption":"Figure: 图 5.3、Customer Service 响应","alt":"图 5.3、Customer Service 响应","nro":266,"url":"resources/5-3.png","index":3,"caption_template":"_CAPTION_","label":"图 5.3、Customer Service 响应","attributes":{},"skip":false,"key":"1.7.8.3"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-in-action#fig1.7.8.4","level":"1.7.8","list_caption":"Figure: 图 5-4、Order Service 作用于响应","alt":"图 5-4、Order Service 作用于响应","nro":267,"url":"resources/5-4.png","index":4,"caption_template":"_CAPTION_","label":"图 5-4、Order Service 作用于响应","attributes":{},"skip":false,"key":"1.7.8.4"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-in-action#fig1.7.8.5","level":"1.7.8","list_caption":"Figure: 图 5-5 Customer Order View 被两个服务访问","alt":"图 5-5 Customer Order View 被两个服务访问","nro":268,"url":"resources/5-5.png","index":5,"caption_template":"_CAPTION_","label":"图 5-5 Customer Order View 被两个服务访问","attributes":{},"skip":false,"key":"1.7.8.5"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-in-action#fig1.7.8.6","level":"1.7.8","list_caption":"Figure: 图 5-6、本地事务实现原子性","alt":"图 5-6、本地事务实现原子性","nro":269,"url":"resources/5-6.png","index":6,"caption_template":"_CAPTION_","label":"图 5-6、本地事务实现原子性","attributes":{},"skip":false,"key":"1.7.8.6"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-in-action#fig1.7.8.7","level":"1.7.8","list_caption":"Figure: 图 5-7、Message Broker 可以公断数据事务","alt":"图 5-7、Message Broker 可以公断数据事务","nro":270,"url":"resources/5-7.png","index":7,"caption_template":"_CAPTION_","label":"图 5-7、Message Broker 可以公断数据事务","attributes":{},"skip":false,"key":"1.7.8.7"},{"backlink":"5-event-driven-data-management-for-microservices.html#microservices-in-action#fig1.7.8.8","level":"1.7.8","list_caption":"Figure: 图 5-8、事件有完整的数据","alt":"图 5-8、事件有完整的数据","nro":271,"url":"resources/5-8.png","index":8,"caption_template":"_CAPTION_","label":"图 5-8、事件有完整的数据","attributes":{},"skip":false,"key":"1.7.8.8"},{"backlink":"6-choosing-deployment-strategy.html#fig1.8.1","level":"1.8","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":272,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.1"},{"backlink":"6-choosing-deployment-strategy.html#fig1.8.2","level":"1.8","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":273,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.2"},{"backlink":"6-choosing-deployment-strategy.html#fig1.8.3","level":"1.8","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":274,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.3"},{"backlink":"6-choosing-deployment-strategy.html#motivations#fig1.8.1.1","level":"1.8.1","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":275,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.1.1"},{"backlink":"6-choosing-deployment-strategy.html#motivations#fig1.8.1.2","level":"1.8.1","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":276,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.1.2"},{"backlink":"6-choosing-deployment-strategy.html#motivations#fig1.8.1.3","level":"1.8.1","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":277,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.1.3"},{"backlink":"6-choosing-deployment-strategy.html#multiple-service-instances-per-host-pattern#fig1.8.2.1","level":"1.8.2","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":278,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.2.1"},{"backlink":"6-choosing-deployment-strategy.html#multiple-service-instances-per-host-pattern#fig1.8.2.2","level":"1.8.2","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":279,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.2.2"},{"backlink":"6-choosing-deployment-strategy.html#multiple-service-instances-per-host-pattern#fig1.8.2.3","level":"1.8.2","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":280,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.2.3"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-host-pattern#fig1.8.3.1","level":"1.8.3","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":281,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.3.1"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-host-pattern#fig1.8.3.2","level":"1.8.3","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":282,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.3.2"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-host-pattern#fig1.8.3.3","level":"1.8.3","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":283,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.3.3"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-virtual-machine-pattern#fig1.8.3.1.1","level":"1.8.3.1","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":284,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.3.1.1"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-virtual-machine-pattern#fig1.8.3.1.2","level":"1.8.3.1","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":285,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.3.1.2"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-virtual-machine-pattern#fig1.8.3.1.3","level":"1.8.3.1","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":286,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.3.1.3"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-container-pattern#fig1.8.3.2.1","level":"1.8.3.2","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":287,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.3.2.1"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-container-pattern#fig1.8.3.2.2","level":"1.8.3.2","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":288,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.3.2.2"},{"backlink":"6-choosing-deployment-strategy.html#service-instance-per-container-pattern#fig1.8.3.2.3","level":"1.8.3.2","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":289,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.3.2.3"},{"backlink":"6-choosing-deployment-strategy.html#serverless-deployment#fig1.8.4.1","level":"1.8.4","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":290,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.4.1"},{"backlink":"6-choosing-deployment-strategy.html#serverless-deployment#fig1.8.4.2","level":"1.8.4","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":291,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.4.2"},{"backlink":"6-choosing-deployment-strategy.html#serverless-deployment#fig1.8.4.3","level":"1.8.4","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":292,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.4.3"},{"backlink":"6-choosing-deployment-strategy.html#summary#fig1.8.5.1","level":"1.8.5","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":293,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.5.1"},{"backlink":"6-choosing-deployment-strategy.html#summary#fig1.8.5.2","level":"1.8.5","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":294,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.5.2"},{"backlink":"6-choosing-deployment-strategy.html#summary#fig1.8.5.3","level":"1.8.5","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":295,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.5.3"},{"backlink":"6-choosing-deployment-strategy.html#microservices-in-action#fig1.8.6.1","level":"1.8.6","list_caption":"Figure: 图 6-1、主机可支持多个服务实例","alt":"图 6-1、主机可支持多个服务实例","nro":296,"url":"resources/6-1.png","index":1,"caption_template":"_CAPTION_","label":"图 6-1、主机可支持多个服务实例","attributes":{},"skip":false,"key":"1.8.6.1"},{"backlink":"6-choosing-deployment-strategy.html#microservices-in-action#fig1.8.6.2","level":"1.8.6","list_caption":"Figure: 图 6-2、服务可以各自运行在自己的虚拟机中","alt":"图 6-2、服务可以各自运行在自己的虚拟机中","nro":297,"url":"resources/6-2.png","index":2,"caption_template":"_CAPTION_","label":"图 6-2、服务可以各自运行在自己的虚拟机中","attributes":{},"skip":false,"key":"1.8.6.2"},{"backlink":"6-choosing-deployment-strategy.html#microservices-in-action#fig1.8.6.3","level":"1.8.6","list_caption":"Figure: 图 6-3、服务可以各自运行在自己的容器中","alt":"图 6-3、服务可以各自运行在自己的容器中","nro":298,"url":"resources/6-3.png","index":3,"caption_template":"_CAPTION_","label":"图 6-3、服务可以各自运行在自己的容器中","attributes":{},"skip":false,"key":"1.8.6.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#fig1.9.1","level":"1.9","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":299,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#fig1.9.2","level":"1.9","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":300,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#fig1.9.3","level":"1.9","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":301,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#fig1.9.4","level":"1.9","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":302,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.4"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#overview-of-refactoring-to-microservices#fig1.9.1.1","level":"1.9.1","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":303,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.1.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#overview-of-refactoring-to-microservices#fig1.9.1.2","level":"1.9.1","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":304,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.1.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#overview-of-refactoring-to-microservices#fig1.9.1.3","level":"1.9.1","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":305,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.1.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#overview-of-refactoring-to-microservices#fig1.9.1.4","level":"1.9.1","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":306,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.1.4"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-1-Stop-digging#fig1.9.2.1","level":"1.9.2","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":307,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.2.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-1-Stop-digging#fig1.9.2.2","level":"1.9.2","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":308,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.2.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-1-Stop-digging#fig1.9.2.3","level":"1.9.2","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":309,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.2.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-1-Stop-digging#fig1.9.2.4","level":"1.9.2","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":310,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.2.4"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-2-split-frontend-and-backend#fig1.9.3.1","level":"1.9.3","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":311,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.3.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-2-split-frontend-and-backend#fig1.9.3.2","level":"1.9.3","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":312,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.3.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-2-split-frontend-and-backend#fig1.9.3.3","level":"1.9.3","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":313,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.3.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-2-split-frontend-and-backend#fig1.9.3.4","level":"1.9.3","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":314,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.3.4"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-3-extract-services#fig1.9.4.1","level":"1.9.4","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":315,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.4.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-3-extract-services#fig1.9.4.2","level":"1.9.4","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":316,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.4.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-3-extract-services#fig1.9.4.3","level":"1.9.4","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":317,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.4.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#strategy-3-extract-services#fig1.9.4.4","level":"1.9.4","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":318,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.4.4"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#prioritizing-which-modules-to-convert-into-services#fig1.9.4.1.1","level":"1.9.4.1","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":319,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.4.1.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#prioritizing-which-modules-to-convert-into-services#fig1.9.4.1.2","level":"1.9.4.1","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":320,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.4.1.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#prioritizing-which-modules-to-convert-into-services#fig1.9.4.1.3","level":"1.9.4.1","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":321,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.4.1.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#prioritizing-which-modules-to-convert-into-services#fig1.9.4.1.4","level":"1.9.4.1","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":322,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.4.1.4"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#how-to-extract-a-module#fig1.9.4.2.1","level":"1.9.4.2","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":323,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.4.2.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#how-to-extract-a-module#fig1.9.4.2.2","level":"1.9.4.2","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":324,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.4.2.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#how-to-extract-a-module#fig1.9.4.2.3","level":"1.9.4.2","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":325,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.4.2.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#how-to-extract-a-module#fig1.9.4.2.4","level":"1.9.4.2","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":326,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.4.2.4"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#summary#fig1.9.5.1","level":"1.9.5","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":327,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.5.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#summary#fig1.9.5.2","level":"1.9.5","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":328,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.5.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#summary#fig1.9.5.3","level":"1.9.5","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":329,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.5.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#summary#fig1.9.5.4","level":"1.9.5","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":330,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.5.4"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#microservices-in-action#fig1.9.6.1","level":"1.9.6","list_caption":"Figure: 葡萄树","alt":"葡萄树","nro":331,"url":"resources/7.png","index":1,"caption_template":"_CAPTION_","label":"葡萄树","attributes":{},"skip":false,"key":"1.9.6.1"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#microservices-in-action#fig1.9.6.2","level":"1.9.6","list_caption":"Figure: 图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","alt":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","nro":332,"url":"resources/7-1.png","index":2,"caption_template":"_CAPTION_","label":"图 7-1、将新功能实现为单独的服务，而不是将模块添加到单体","attributes":{},"skip":false,"key":"1.9.6.2"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#microservices-in-action#fig1.9.6.3","level":"1.9.6","list_caption":"Figure: 图 7-2、重构现有的应用程序","alt":"图 7-2、重构现有的应用程序","nro":333,"url":"resources/7-2.png","index":3,"caption_template":"_CAPTION_","label":"图 7-2、重构现有的应用程序","attributes":{},"skip":false,"key":"1.9.6.3"},{"backlink":"7-refactoring-a-monolith-into-microservices.html#microservices-in-action#fig1.9.6.4","level":"1.9.6","list_caption":"Figure: 图7-3、单体模块可转换为微服务","alt":"图7-3、单体模块可转换为微服务","nro":334,"url":"resources/7-3.png","index":4,"caption_template":"_CAPTION_","label":"图7-3、单体模块可转换为微服务","attributes":{},"skip":false,"key":"1.9.6.4"}]},"title":"微服务：从设计到部署","language":"zh-hans","links":{"sharing":{"all":true,"facebook":true,"google":true,"twitter":true,"weibo":true},"sidebar":{"Oopsguy 的博客":"http://oopsguy.com","《微服务：从设计到部署》":"https://github.com/oopsguy/microservices-from-design-to-deployment-chinese"}},"gitbook":"*","description":"Nginx 经典微服务电子书中文翻译版本","extension":null},"file":{"path":"2-using-an-api-gateway.md","mtime":"2019-06-26T11:25:49.557Z","type":"markdown"},"gitbook":{"version":"3.2.3","time":"2019-06-26T15:12:13.860Z"},"basePath":".","book":{"language":""}});
});
</script>
</div>
<script src="gitbook/gitbook.js"></script>
<script src="gitbook/theme.js"></script>
<script src="gitbook/gitbook-plugin-github/plugin.js"></script>
<script src="gitbook/gitbook-plugin-splitter/splitter.js"></script>
<script src="gitbook/gitbook-plugin-github-buttons/plugin.js"></script>
<script src="gitbook/gitbook-plugin-sharing/buttons.js"></script>
<script src="gitbook/gitbook-plugin-fontsettings/fontsettings.js"></script>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink