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/3-inter-process-communication.html
Oopsguy 41ce752637 testing for new gitbook
2019-07-13 03:00:33 +08:00

1469 lines
227 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>3、进程间通信 · 微服务：从设计到部署</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="3-inter-process-communication.html" />
<link rel="prev" href="2-using-an-api-gateway.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 " 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 active" 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="." >3、进程间通信</a>
</h1>
</div>
<div class="page-wrapper" tabindex="-1" role="main">
<div class="page-inner">
<section class="normal markdown-section">
<h1 id="3&#x3001;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;">3&#x3001;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;</h1>
<p>&#x672C;&#x4E66;&#x4E3B;&#x8981;&#x4ECB;&#x7ECD;&#x5982;&#x4F55;&#x4F7F;&#x7528;&#x5FAE;&#x670D;&#x52A1;&#x67B6;&#x6784;&#x6784;&#x5EFA;&#x5E94;&#x7528;&#xFF0C;&#x8FD9;&#x662F;&#x672C;&#x4E66;&#x7684;&#x7B2C;&#x4E09;&#x7AE0;&#x3002;<a href="1-introduction-to-microservices.html">&#x7B2C;&#x4E00;&#x7AE0;</a>&#x4ECB;&#x7ECD;&#x4E86;<a href="http://microservices.io/patterns/microservices.html" target="_blank">&#x5FAE;&#x670D;&#x52A1;&#x67B6;&#x6784;&#x6A21;&#x5F0F;</a>&#xFF0C;&#x4E0E;&#x5355;&#x4F53;&#x67B6;&#x6784;&#x6A21;&#x5F0F;&#x505A;&#x4E86;&#x5BF9;&#x6BD4;&#xFF0C;&#x5E76;&#x8BA8;&#x8BBA;&#x4E86;&#x4F7F;&#x7528;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x4F18;&#x70B9;&#x4E0E;&#x7F3A;&#x70B9;&#x3002;<a href="2-using-an-api-gateway.html">&#x7B2C;&#x4E8C;&#x7AE0;</a>&#x4ECB;&#x7ECD;&#x4E86;&#x5E94;&#x7528;&#x5BA2;&#x6237;&#x7AEF;&#x901A;&#x8FC7;&#x626E;&#x6F14;&#x4E2D;&#x95F4;&#x4EBA;&#x89D2;&#x8272;&#x7684; <a href="http://microservices.io/patterns/apigateway.html" target="_blank">API &#x7F51;&#x5173;</a>&#x4E0E;&#x5FAE;&#x670D;&#x52A1;&#x8FDB;&#x884C;&#x901A;&#x4FE1;&#x3002;&#x5728;&#x672C;&#x7AE0;&#x4E2D;&#xFF0C;&#x6211;&#x4EEC;&#x6765;&#x4E86;&#x89E3;&#x4E00;&#x4E0B;&#x7CFB;&#x7EDF;&#x4E2D;&#x7684;&#x670D;&#x52A1;&#x662F;&#x5982;&#x4F55;&#x76F8;&#x4E92;&#x901A;&#x4FE1;&#x7684;&#x3002;<a href="4-service-discovery.html">&#x7B2C;&#x56DB;&#x7AE0;</a>&#x5C06;&#x8BE6;&#x7EC6;&#x63A2;&#x8BA8;&#x670D;&#x52A1;&#x53D1;&#x73B0;&#x65B9;&#x9762;&#x7684;&#x5185;&#x5BB9;&#x3002;</p>
<p><a id="introduction"></a></p>
<h2 id="31&#x3001;&#x7B80;&#x4ECB;">3.1&#x3001;&#x7B80;&#x4ECB;</h2>
<p>&#x5728;&#x5355;&#x4F53;&#x5E94;&#x7528;&#x4E2D;&#xFF0C;&#x7EC4;&#x4EF6;&#x53EF;&#x901A;&#x8FC7;&#x8BED;&#x8A00;&#x7EA7;&#x65B9;&#x6CD5;&#x6216;&#x8005;&#x51FD;&#x6570;&#x76F8;&#x4E92;&#x8C03;&#x7528;&#x3002;&#x76F8;&#x6BD4;&#x4E4B;&#x4E0B;&#xFF0C;&#x57FA;&#x4E8E;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x5E94;&#x7528;&#x662F;&#x4E00;&#x4E2A;&#x8FD0;&#x884C;&#x5728;&#x591A;&#x53F0;&#x673A;&#x5668;&#x4E0A;&#x7684;&#x5206;&#x5E03;&#x5F0F;&#x7CFB;&#x7EDF;&#x3002;&#x901A;&#x5E38;&#xFF0C;&#x6BCF;&#x4E2A;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x90FD;&#x662F;&#x4E00;&#x4E2A;&#x8FDB;&#x7A0B;&#x3002;</p>
<p>&#x56E0;&#x6B64;&#xFF0C;&#x5982;&#x56FE; 3-1 &#x6240;&#x793A;&#xFF0C;&#x670D;&#x52A1;&#x5FC5;&#x987B;&#x4F7F;&#x7528;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#xFF08;IPC&#xFF09;&#x673A;&#x5236;&#x8FDB;&#x884C;&#x4EA4;&#x4E92;&#x3002;</p>
<p>&#x7A0D;&#x540E;&#x6211;&#x4EEC;&#x5C06;&#x4E86;&#x89E3;&#x5230;&#x591A;&#x79CD; IPC &#x6280;&#x672F;&#xFF0C;&#x4F46;&#x5728;&#x6B64;&#x4E4B;&#x524D;&#xFF0C;&#x6211;&#x4EEC;&#x5148;&#x6765;&#x63A2;&#x8BA8;&#x4E00;&#x4E0B;&#x6D89;&#x53CA;&#x5230;&#x7684;&#x5404;&#x79CD;&#x8BBE;&#x8BA1;&#x95EE;&#x9898;&#x3002;</p>
<figure id="fig1.5.1"><img src="resources/3-1.png" alt="&#x4F7F;&#x7528;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#x4EA4;&#x4E92;&#x7684;&#x5FAE;&#x670D;&#x52A1;"><figcaption>&#x4F7F;&#x7528;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#x4EA4;&#x4E92;&#x7684;&#x5FAE;&#x670D;&#x52A1;</figcaption></figure>
<p><a id="interaction-styles"></a></p>
<h2 id="32&#x3001;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;">3.2&#x3001;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;</h2>
<p>&#x5F53;&#x4E3A;&#x670D;&#x52A1;&#x9009;&#x62E9;&#x4E00;&#x79CD; IPC &#x673A;&#x5236;&#x65F6;&#xFF0C;&#x9996;&#x5148;&#x9700;&#x8981;&#x8003;&#x8651;&#x670D;&#x52A1;&#x5982;&#x4F55;&#x4EA4;&#x4E92;&#x3002;&#x6709;&#x8BB8;&#x591A;&#x79CD;&#x5BA2;&#x6237;&#x7AEF;/&#x670D;&#x52A1;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#x3002;&#x53EF;&#x4EE5;&#x4ECE;&#x4E24;&#x65B9;&#x9762;&#x5BF9;&#x5B83;&#x4EEC;&#x8FDB;&#x884C;&#x5206;&#x7C7B;&#x3002;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#x662F;&#x4E00;&#x5BF9;&#x4E00;&#x8FD8;&#x662F;&#x4E00;&#x5BF9;&#x591A;&#xFF1A;</p>
<ul>
<li><strong>&#x4E00;&#x5BF9;&#x4E00;</strong> &#x2014; &#x6BCF;&#x4E2A;&#x5BA2;&#x6237;&#x7AEF;&#x8BF7;&#x6C42;&#x90FD;&#x7531;&#x4E00;&#x4E2A;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x5904;&#x7406;&#x3002;</li>
<li><strong>&#x4E00;&#x5BF9;&#x591A;</strong> &#x2014; &#x6BCF;&#x4E2A;&#x8BF7;&#x6C42;&#x7531;&#x591A;&#x4E2A;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x5904;&#x7406;&#x3002;</li>
</ul>
<p>&#x4EA4;&#x4E92;&#x662F;&#x540C;&#x6B65;&#x7684;&#x8FD8;&#x662F;&#x5F02;&#x6B65;&#x7684;&#xFF1A;</p>
<ul>
<li><strong>&#x540C;&#x6B65;</strong> &#x2014; &#x5BA2;&#x6237;&#x7AEF;&#x8981;&#x6C42;&#x670D;&#x52A1;&#x53CA;&#x65F6;&#x54CD;&#x5E94;&#xFF0C;&#x5728;&#x7B49;&#x5F85;&#x8FC7;&#x7A0B;&#x4E2D;&#x53EF;&#x80FD;&#x4F1A;&#x53D1;&#x751F;&#x963B;&#x585E;&#x3002;</li>
<li><strong>&#x5F02;&#x6B65;</strong> &#x2014; &#x5BA2;&#x6237;&#x7AEF;&#x5728;&#x7B49;&#x5F85;&#x54CD;&#x5E94;&#x65F6;&#x4E0D;&#x4F1A;&#x53D1;&#x751F;&#x963B;&#x585E;&#xFF0C;&#x4F46;&#x54CD;&#x5E94;&#xFF08;&#x5982;&#x679C;&#x6709;&#xFF09;&#x4E0D;&#x4E00;&#x5B9A;&#x7ACB;&#x5373;&#x8FD4;&#x56DE;&#x3002;</li>
</ul>
<p>&#x4E0B;&#x8868;&#x5C55;&#x793A;&#x4E86;&#x5404;&#x79CD;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#x3002;</p>
<table>
<thead>
<tr>
<th>-</th>
<th>&#x4E00;&#x5BF9;&#x4E00;</th>
<th>&#x4E00;&#x5BF9;&#x591A;</th>
</tr>
</thead>
<tbody>
<tr>
<td>&#x540C;&#x6B65;</td>
<td>&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;</td>
<td>-</td>
</tr>
<tr>
<td>&#x5F02;&#x6B65;</td>
<td>&#x901A;&#x77E5;</td>
<td>&#x53D1;&#x5E03;/&#x8BA2;&#x9605;</td>
</tr>
<tr>
<td>&#x5F02;&#x6B65;</td>
<td>&#x8BF7;&#x6C42;/&#x5F02;&#x6B65;&#x54CD;&#x5E94;</td>
<td>&#x53D1;&#x5E03;/&#x5F02;&#x6B65;&#x54CD;&#x5E94;</td>
</tr>
</tbody>
</table>
<p>&#x8868; 3-1&#x3001;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#x65B9;&#x5F0F;</p>
<p>&#x4EE5;&#x4E0B;&#x4E3A;&#x4E00;&#x5BF9;&#x4E00;&#x4EA4;&#x4E92;&#xFF0C;&#x5305;&#x62EC;&#x540C;&#x6B65;&#xFF08;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#xFF09;&#x4E0E;&#x5F02;&#x6B65;&#xFF08;&#x901A;&#x77E5;&#x4E0E;&#x8BF7;&#x6C42;/&#x5F02;&#x6B65;&#x54CD;&#x5E94;&#xFF09;&#xFF1A;</p>
<ul>
<li><p><strong>&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;</strong></p>
<p> &#x5BA2;&#x6237;&#x7AEF;&#x5411;&#x670D;&#x52A1;&#x53D1;&#x51FA;&#x8BF7;&#x6C42;&#x5E76;&#x7B49;&#x5F85;&#x54CD;&#x5E94;&#x3002;&#x5BA2;&#x6237;&#x7AEF;&#x8981;&#x6C42;&#x54CD;&#x5E94;&#x53CA;&#x65F6;&#x5230;&#x8FBE;&#x3002;&#x5728;&#x57FA;&#x4E8E;&#x7EBF;&#x7A0B;&#x7684;&#x5E94;&#x7528;&#x4E2D;&#xFF0C;&#x53D1;&#x51FA;&#x8BF7;&#x6C42;&#x7684;&#x7EBF;&#x7A0B;&#x53EF;&#x80FD;&#x5728;&#x7B49;&#x5F85;&#x65F6;&#x53D1;&#x751F;&#x963B;&#x585E;&#x3002;</p>
</li>
<li><p><strong>&#x901A;&#x77E5;&#xFF08;&#x53C8;&#x79F0;&#x4E3A;&#x5355;&#x5411;&#x8BF7;&#x6C42;&#xFF09;</strong></p>
<p> &#x5BA2;&#x6237;&#x7AEF;&#x5411;&#x670D;&#x52A1;&#x53D1;&#x9001;&#x8BF7;&#x6C42;&#xFF0C;&#x4F46;&#x4E0D;&#x8981;&#x6C42;&#x54CD;&#x5E94;&#x3002;</p>
</li>
<li><p><strong>&#x8BF7;&#x6C42;/&#x5F02;&#x6B65;&#x54CD;&#x5E94;</strong></p>
<p> &#x5BA2;&#x6237;&#x7AEF;&#x5411;&#x670D;&#x52A1;&#x53D1;&#x9001;&#x8BF7;&#x6C42;&#xFF0C;&#x670D;&#x52A1;&#x5F02;&#x6B65;&#x54CD;&#x5E94;&#x3002;&#x5BA2;&#x6237;&#x7AEF;&#x5728;&#x7B49;&#x5F85;&#x65F6;&#x4E0D;&#x53D1;&#x751F;&#x963B;&#x6B62;&#xFF0C;&#x9002;&#x7528;&#x4E8E;&#x5047;&#x8BBE;&#x54CD;&#x5E94;&#x53EF;&#x80FD;&#x4E0D;&#x4F1A;&#x7ACB;&#x5373;&#x5230;&#x8FBE;&#x7684;&#x573A;&#x666F;&#x3002;</p>
</li>
</ul>
<p>&#x4E00;&#x5BF9;&#x591A;&#x4EA4;&#x4E92;&#xFF0C;&#x5B83;&#x4EEC;&#x90FD;&#x662F;&#x5F02;&#x6B65;&#x7684;&#xFF1A;</p>
<ul>
<li><p><strong>&#x53D1;&#x5E03;/&#x8BA2;&#x9605;</strong></p>
<p> &#x5BA2;&#x6237;&#x7AEF;&#x53D1;&#x5E03;&#x901A;&#x77E5;&#x6D88;&#x606F;&#xFF0C;&#x7531;&#x96F6;&#x4E2A;&#x6216;&#x591A;&#x4E2A;&#x670D;&#x52A1;&#x6D88;&#x8D39;&#x3002;</p>
</li>
<li><p><strong>&#x53D1;&#x5E03;/&#x5F02;&#x6B65;&#x54CD;&#x5E94;</strong></p>
<p> &#x5BA2;&#x6237;&#x7AEF;&#x53D1;&#x5E03;&#x8BF7;&#x6C42;&#x6D88;&#x606F;&#xFF0C;&#x4E4B;&#x540E;&#x7B49;&#x5F85;&#x4E00;&#x5B9A;&#x65F6;&#x95F4;&#x6765;&#x63A5;&#x6536;&#x6D88;&#x8D39;&#x8005;&#x7684;&#x54CD;&#x5E94;&#x3002;</p>
</li>
</ul>
<p>&#x901A;&#x5E38;&#xFF0C;&#x6BCF;&#x4E2A;&#x670D;&#x52A1;&#x90FD;&#x7EC4;&#x5408;&#x7740;&#x4F7F;&#x7528;&#x8FD9;&#x4E9B;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#x3002;&#x5BF9;&#x4E00;&#x4E9B;&#x670D;&#x52A1;&#x800C;&#x8A00;&#xFF0C;&#x5355;&#x4E00;&#x7684; IPC &#x673A;&#x5236;&#x5C31;&#x8DB3;&#x591F;&#x4E86;&#xFF0C;&#x4F46;&#x5176;&#x4ED6;&#x670D;&#x52A1;&#x53EF;&#x80FD;&#x9700;&#x8981;&#x7EC4;&#x5408;&#x591A;&#x4E2A; IPC &#x673A;&#x5236;&#x3002;</p>
<p>&#x56FE; 3-2 &#x663E;&#x793A;&#x4E86;&#x5F53;&#x7528;&#x6237;&#x8BF7;&#x6C42;&#x6253;&#x8F66;&#x65F6;&#xFF0C;&#x6253;&#x8F66;&#x5E94;&#x7528;&#x4E2D;&#x7684;&#x670D;&#x52A1;&#x53EF;&#x80FD;&#x4F1A;&#x53D1;&#x751F;&#x4EA4;&#x4E92;&#x3002;</p>
<figure id="fig1.5.2"><img src="resources/3-2.png" alt="&#x4F7F;&#x7528;&#x4E86;&#x591A;&#x79CD; IPC &#x673A;&#x5236;&#x7684;&#x670D;&#x52A1;&#x4EA4;&#x4E92;"><figcaption>&#x4F7F;&#x7528;&#x4E86;&#x591A;&#x79CD; IPC &#x673A;&#x5236;&#x7684;&#x670D;&#x52A1;&#x4EA4;&#x4E92;</figcaption></figure>
<p>&#x670D;&#x52A1;&#x4F7F;&#x7528;&#x4E86;&#x901A;&#x77E5;&#x3001;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x548C;&#x53D1;&#x5E03;/&#x8BA2;&#x9605;&#x7EC4;&#x5408;&#x3002;&#x4F8B;&#x5982;&#xFF0C;&#x4E58;&#x5BA2;&#x7684;&#x667A;&#x80FD;&#x624B;&#x673A;&#x5411; Trip Management &#x5FAE;&#x670D;&#x52A1;&#x53D1;&#x9001;&#x4E00;&#x6761;&#x901A;&#x77E5;&#x8BF7;&#x6C42;&#x4E00;&#x8F86;&#x8F66;&#x3002;Trip Management &#x670D;&#x52A1;&#x901A;&#x8FC7;&#x4F7F;&#x7528;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x6765;&#x8C03;&#x7528; Passenger Management &#x670D;&#x52A1;&#x4EE5;&#x9A8C;&#x8BC1;&#x4E58;&#x5BA2;&#x7684;&#x5E10;&#x6237;&#x662F;&#x5426;&#x53EF;&#x7528;&#x3002;&#x4E4B;&#x540E;&#xFF0C;Trip Management &#x670D;&#x52A1;&#x521B;&#x5EFA;&#x8DEF;&#x7EBF;&#xFF0C;&#x5E76;&#x4F7F;&#x7528;&#x53D1;&#x5E03;/&#x8BA2;&#x9605;&#x901A;&#x77E5;&#x5176;&#x4ED6;&#x670D;&#x52A1;&#xFF0C;&#x5305;&#x62EC;&#x7528;&#x4E8E;&#x5B9A;&#x4F4D;&#x53EF;&#x7528;&#x53F8;&#x673A;&#x7684; Dispatcher&#x3002;</p>
<p>&#x73B0;&#x5728;&#x6211;&#x4EEC;&#x6765;&#x770B;&#x4E00;&#x4E0B;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#xFF0C;&#x6211;&#x4EEC;&#x5148;&#x6765;&#x770B;&#x770B;&#x5982;&#x4F55;&#x5B9A;&#x4E49; API&#x3002;</p>
<p><a id="defining-apis"></a></p>
<h2 id="33&#x3001;&#x5B9A;&#x4E49;-api">3.3&#x3001;&#x5B9A;&#x4E49; API</h2>
<p>&#x670D;&#x52A1; API &#x662F;&#x670D;&#x52A1;&#x4E0E;&#x5BA2;&#x6237;&#x7AEF;&#x4E4B;&#x95F4;&#x7684;&#x5951;&#x7EA6;&#x3002;&#x65E0;&#x8BBA;&#x4F60;&#x9009;&#x62E9;&#x4F55;&#x79CD; IPC &#x673A;&#x5236;&#xFF0C;&#x4F7F;&#x7528;&#x63A5;&#x53E3;&#x5B9A;&#x4E49;&#x8BED;&#x8A00;&#xFF08;interface definition language&#xFF0C;IDL&#xFF09;&#x6765;&#x4E25;&#x683C;&#x5B9A;&#x4E49;&#x670D;&#x52A1; API &#x90FD;&#x662F;&#x975E;&#x5E38;&#x6709;&#x5FC5;&#x8981;&#x7684;&#x3002;&#x6709;&#x8BBA;&#x636E;&#x8BC1;&#x660E;&#x4F7F;&#x7528; <a href="https://www.programmableweb.com/news/how-to-design-great-apis-api-first-design-and-raml/how-to/2015/07/10" target="_blank">API &#x4F18;&#x5148;&#x6CD5;</a>&#x5B9A;&#x4E49;&#x670D;&#x52A1;&#x66F4;&#x52A0;&#x5408;&#x7406;&#x3002;&#x5728;&#x5BF9;&#x9700;&#x8981;&#x5B9E;&#x73B0;&#x7684;&#x670D;&#x52A1;&#x7684; API &#x5B9A;&#x4E49;&#x8FDB;&#x884C;&#x8FED;&#x4EE3;&#x4E4B;&#x540E;&#xFF0C;&#x4F60;&#x53EF;&#x4EE5;&#x901A;&#x8FC7;&#x7F16;&#x5199;&#x63A5;&#x53E3;&#x5B9A;&#x4E49;&#x5E76;&#x4E0E;&#x5BA2;&#x6237;&#x7AEF;&#x5F00;&#x53D1;&#x4EBA;&#x5458;&#x8FDB;&#x884C;&#x5BA1;&#x9605;&#x6765;&#x5F00;&#x59CB;&#x5F00;&#x53D1;&#x670D;&#x52A1;&#x3002;&#x8FD9;&#x6837;&#x8BBE;&#x8BA1;&#x53EF;&#x4EE5;&#x589E;&#x52A0;&#x4F60;&#x6210;&#x529F;&#x7684;&#x673A;&#x7387;&#xFF0C;&#x4EE5;&#x6784;&#x5EFA;&#x51FA;&#x7B26;&#x5408;&#x5BA2;&#x6237;&#x7AEF;&#x9700;&#x6C42;&#x7684;&#x670D;&#x52A1;&#x3002;</p>
<p>&#x6B63;&#x5982;&#x4F60;&#x5C06;&#x4F1A;&#x5728;&#x540E;&#x9762;&#x770B;&#x5230;&#xFF0C;&#x5B9A;&#x4E49; API &#x7684;&#x65B9;&#x5F0F;&#x53D6;&#x51B3;&#x4E8E;&#x4F60;&#x4F7F;&#x7528;&#x4F55;&#x79CD; IPC &#x673A;&#x5236;&#x3002;&#x5982;&#x679C;&#x4F60;&#x6B63;&#x5728;&#x4F7F;&#x7528;&#x6D88;&#x606F;&#x4F20;&#x9012;&#xFF0C;&#x90A3;&#x4E48; API &#x662F;&#x7531;&#x6D88;&#x606F;&#x901A;&#x9053;&#x548C;&#x6D88;&#x606F;&#x7C7B;&#x578B;&#x7EC4;&#x6210;&#x3002;&#x5982;&#x679C;&#x4F60;&#x4F7F;&#x7528;&#x7684;&#x662F; HTTP&#xFF0C;&#x90A3;&#x4E48; API &#x662F;&#x7531; URL&#x3001;&#x8BF7;&#x6C42;&#x548C;&#x54CD;&#x5E94;&#x683C;&#x5F0F;&#x7EC4;&#x6210;&#x3002;&#x7A0D;&#x540E;&#x6211;&#x4EEC;&#x5C06;&#x8BE6;&#x7EC6;&#x5730;&#x4ECB;&#x7ECD;&#x5173;&#x4E8E; IDL &#x65B9;&#x9762;&#x7684;&#x5185;&#x5BB9;&#x3002;</p>
<p><a id="evolving-apis"></a></p>
<h2 id="34&#x3001;&#x6F14;&#x5316;-api">3.4&#x3001;&#x6F14;&#x5316; API</h2>
<p>&#x670D;&#x52A1; API &#x603B;&#x662F;&#x968F;&#x7740;&#x65F6;&#x95F4;&#x800C;&#x53D8;&#x5316;&#x3002;&#x5728;&#x5355;&#x4F53;&#x5E94;&#x7528;&#x4E2D;&#xFF0C;&#x66F4;&#x6539; API &#x548C;&#x66F4;&#x65B0;&#x6240;&#x6709;&#x8C03;&#x7528;&#x8005;&#x901A;&#x5E38;&#x662F;&#x4E00;&#x4EF6;&#x76F4;&#x622A;&#x4E86;&#x5F53;&#x7684;&#x4E8B;&#x3002;&#x4F46;&#x5728;&#x57FA;&#x4E8E;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x5E94;&#x7528;&#x4E2D;&#xFF0C;&#x5373;&#x4F7F; API &#x7684;&#x6240;&#x6709;&#x6D88;&#x8D39;&#x8005;&#x90FD;&#x662F;&#x540C;&#x4E00;&#x5E94;&#x7528;&#x4E2D;&#x7684;&#x5176;&#x4ED6;&#x670D;&#x52A1;&#xFF0C;&#x8981;&#x60F3;&#x5B8C;&#x6210;&#x8FD9;&#x4E9B;&#x5DE5;&#x4F5C;&#x4E5F;&#x662F;&#x975E;&#x5E38;&#x56F0;&#x96BE;&#x7684;&#x3002;&#x901A;&#x5E38;&#xFF0C;&#x4F60;&#x65E0;&#x6CD5;&#x5F3A;&#x5236;&#x6240;&#x6709;&#x5BA2;&#x6237;&#x7AEF;&#x4E0E;&#x670D;&#x52A1;&#x5347;&#x7EA7;&#x7684;&#x8282;&#x594F;&#x4E00;&#x81F4;&#x3002;&#x6B64;&#x5916;&#xFF0C;&#x4F60;&#x53EF;&#x80FD;&#x9700;&#x8981;<a href="http://techblog.netflix.com/2013/08/deploying-netflix-api.html" target="_blank">&#x9010;&#x6B65;&#x90E8;&#x7F72;&#x670D;&#x52A1;&#x7684;&#x65B0;&#x7248;&#x672C;</a>&#xFF0C;&#x4EE5;&#x4FBF;&#x65B0;&#x65E7;&#x7248;&#x672C;&#x7684;&#x670D;&#x52A1;&#x540C;&#x65F6;&#x8FD0;&#x884C;&#x3002;&#x56E0;&#x6B64;&#xFF0C;&#x5236;&#x5B9A;&#x8FD9;&#x4E9B;&#x95EE;&#x9898;&#x7684;&#x5904;&#x7406;&#x7B56;&#x7565;&#x8FD8;&#x662F;&#x5F88;&#x91CD;&#x8981;&#x7684;&#x3002;</p>
<p>&#x5904;&#x7406; API &#x53D8;&#x66F4;&#x7684;&#x65B9;&#x5F0F;&#x53D6;&#x51B3;&#x4E8E;&#x53D8;&#x66F4;&#x7684;&#x7A0B;&#x5EA6;&#x3002;&#x67D0;&#x4E9B;&#x66F4;&#x6539;&#x662F;&#x6B21;&#x8981;&#x6216;&#x9700;&#x8981;&#x5411;&#x540E;&#x517C;&#x5BB9;&#x4EE5;&#x524D;&#x7684;&#x7248;&#x672C;&#x3002;&#x4F8B;&#x5982;&#xFF0C;&#x4F60;&#x53EF;&#x80FD;&#x4F1A;&#x5411;&#x8BF7;&#x6C42;&#x6216;&#x54CD;&#x5E94;&#x4E2D;&#x6DFB;&#x52A0;&#x5C5E;&#x6027;&#x3002;&#x6B64;&#x65F6;&#x8BBE;&#x8BA1;&#x5BA2;&#x6237;&#x7AEF;&#x4E0E;&#x670D;&#x52A1;&#x9075;&#x5B88;<a href="https://en.wikipedia.org/wiki/Robustness_principle" target="_blank">&#x9C81;&#x68D2;&#x6027;&#x539F;&#x5219;</a>&#x5C31;&#x663E;&#x5F97;&#x5F88;&#x6709;&#x610F;&#x4E49;&#x4E86;&#x3002;&#x65B0;&#x7248;&#x672C;&#x7684;&#x670D;&#x52A1;&#x8981;&#x80FD;&#x517C;&#x5BB9;&#x4F7F;&#x7528;&#x65E7;&#x7248;&#x672C; API &#x7684;&#x5BA2;&#x6237;&#x7AEF;&#x3002;&#x8BE5;&#x670D;&#x52A1;&#x4E3A;&#x7F3A;&#x5C11;&#x7684;&#x8BF7;&#x6C42;&#x5C5E;&#x6027;&#x63D0;&#x4F9B;&#x9ED8;&#x8BA4;&#x503C;&#xFF0C;&#x5E76;&#x4E14;&#x5BA2;&#x6237;&#x7AEF;&#x5FFD;&#x7565;&#x6240;&#x6709;&#x591A;&#x4F59;&#x7684;&#x54CD;&#x5E94;&#x5C5E;&#x6027;&#x3002;&#x4F7F;&#x7528; IPC &#x673A;&#x5236;&#x548C;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#x975E;&#x5E38;&#x91CD;&#x8981;&#xFF0C;&#x4ED6;&#x4EEC;&#x53EF;&#x4EE5;&#x8BA9;&#x4F60;&#x8F7B;&#x677E;&#x5730;&#x6F14;&#x5316; API&#x3002;</p>
<p>&#x4F46;&#x6709;&#x65F6;&#x5019;&#xFF0C;&#x4F60;&#x5FC5;&#x987B;&#x5BF9; API &#x4F5C;&#x51FA;&#x5927;&#x91CF;&#x4E0D;&#x517C;&#x5BB9;&#x7684;&#x66F4;&#x6539;&#x3002;&#x7531;&#x4E8E;&#x4F60;&#x65E0;&#x6CD5;&#x5F3A;&#x5236;&#x5BA2;&#x6237;&#x7AEF;&#x7ACB;&#x5373;&#x5347;&#x7EA7;&#xFF0C;&#x670D;&#x52A1;&#x4E5F;&#x5FC5;&#x987B;&#x652F;&#x6301;&#x8F83;&#x65E7;&#x7248;&#x672C;&#x7684; API &#x4E00;&#x6BB5;&#x65F6;&#x95F4;&#x3002;&#x5982;&#x679C;&#x4F60;&#x4F7F;&#x7528;&#x4E86;&#x57FA;&#x4E8E; HTTP &#x7684;&#x673A;&#x5236;&#xFF08;&#x5982; REST&#xFF09;&#xFF0C;&#x5219;&#x4E00;&#x79CD;&#x65B9;&#x6CD5;&#x662F;&#x5C06;&#x7248;&#x672C;&#x53F7;&#x5D4C;&#x5165;&#x5230; URL &#x4E2D;&#x3002;&#x6BCF;&#x4E2A;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x53EF;&#x80FD;&#x540C;&#x65F6;&#x5904;&#x7406;&#x591A;&#x4E2A;&#x7248;&#x672C;&#x3002;&#x6216;&#x8005;&#xFF0C;&#x4F60;&#x53EF;&#x4EE5;&#x90E8;&#x7F72;&#x591A;&#x4E2A;&#x4E0D;&#x540C;&#x7684;&#x5B9E;&#x4F8B;&#xFF0C;&#x6BCF;&#x4E2A;&#x5B9E;&#x4F8B;&#x5904;&#x7406;&#x7279;&#x5B9A;&#x7684;&#x7248;&#x672C;&#x3002;</p>
<p><a id="handling-partial-failure"></a></p>
<h2 id="35&#x3001;&#x5904;&#x7406;&#x5C40;&#x90E8;&#x6545;&#x969C;">3.5&#x3001;&#x5904;&#x7406;&#x5C40;&#x90E8;&#x6545;&#x969C;</h2>
<p>&#x6B63;&#x5982;<a href="2-using-an-api-gateway.html">&#x7B2C;&#x4E8C;&#x7AE0;</a>&#x4E2D;&#x5173;&#x4E8E; API &#x7F51;&#x5173;&#x6240;&#x8FF0;&#xFF0C;&#x5728;&#x5206;&#x5E03;&#x5F0F;&#x7CFB;&#x7EDF;&#x4E2D;&#x59CB;&#x7EC8;&#x5B58;&#x5728;&#x5C40;&#x90E8;&#x6545;&#x969C;&#x7684;&#x98CE;&#x9669;&#x3002;&#x7531;&#x4E8E;&#x5BA2;&#x6237;&#x7AEF;&#x8FDB;&#x7A0B;&#x4E0E;&#x670D;&#x52A1;&#x8FDB;&#x7A0B;&#x662F;&#x5206;&#x5F00;&#x7684;&#xFF0C;&#x670D;&#x52A1;&#x53EF;&#x80FD;&#x65E0;&#x6CD5;&#x53CA;&#x65F6;&#x54CD;&#x5E94;&#x5BA2;&#x6237;&#x7AEF;&#x7684;&#x8BF7;&#x6C42;&#x3002;&#x7531;&#x4E8E;&#x6545;&#x969C;&#x6216;&#x8005;&#x7EF4;&#x62A4;&#xFF0C;&#x670D;&#x52A1;&#x53EF;&#x80FD;&#x9700;&#x8981;&#x5173;&#x95ED;&#x3002;&#x4E5F;&#x6709;&#x53EF;&#x80FD;&#x56E0;&#x670D;&#x52A1;&#x8FC7;&#x8F7D;&#xFF0C;&#x9020;&#x6210;&#x54CD;&#x5E94;&#x901F;&#x5EA6;&#x53D8;&#x5F97;&#x6781;&#x6162;&#x3002;</p>
<p>&#x4F8B;&#x5982;&#xFF0C;&#x8BF7;&#x56DE;&#x60F3;<a href="2-using-an-api-gateway.html">&#x7B2C;&#x4E8C;&#x7AE0;</a>&#x4E2D;&#x7684;&#x4EA7;&#x54C1;&#x8BE6;&#x7EC6;&#x4FE1;&#x606F;&#x573A;&#x666F;&#x3002;&#x6211;&#x4EEC;&#x5047;&#x8BBE;&#x63A8;&#x8350;&#x670D;&#x52A1;&#x6CA1;&#x6709;&#x54CD;&#x5E94;&#x3002;&#x5929;&#x771F;&#x7684;&#x5BA2;&#x6237;&#x7AEF;&#x5B9E;&#x73B0;&#x53EF;&#x80FD;&#x4F1A;&#x4E0D;&#x505C;&#x5730;&#x963B;&#x585E;&#x4EE5;&#x7B49;&#x5F85;&#x54CD;&#x5E94;&#x3002;&#x8FD9;&#x4E0D;&#x4EC5;&#x4F1A;&#x5BFC;&#x81F4;&#x7528;&#x6237;&#x4F53;&#x9A8C;&#x7CDF;&#x7CD5;&#xFF0C;&#x800C;&#x4E14;&#x5728;&#x8BB8;&#x591A;&#x5E94;&#x7528;&#x4E2D;&#xFF0C;&#x5B83;&#x4F1A;&#x6D88;&#x8017;&#x7EBF;&#x7A0B;&#x7B49;&#x5B9D;&#x8D35;&#x7684;&#x8D44;&#x6E90;&#x3002;&#x6700;&#x7EC8;&#x5BFC;&#x81F4;&#x8FD0;&#x884C;&#x65F6;&#x7CFB;&#x7EDF;&#x5C06;&#x7EBF;&#x7A0B;&#x6D88;&#x8017;&#x5B8C;&#xFF0C;&#x9020;&#x6210;&#x7CFB;&#x7EDF;&#x65E0;&#x6CD5;&#x54CD;&#x5E94;&#xFF0C;&#x5982;&#x56FE; 3-3 &#x6240;&#x793A;&#x3002;</p>
<figure id="fig1.5.3"><img src="resources/3-3.png" alt="&#x56E0;&#x65E0;&#x54CD;&#x5E94;&#x670D;&#x52A1;&#x5F15;&#x8D77;&#x7684;&#x7EBF;&#x7A0B;&#x963B;&#x585E;"><figcaption>&#x56E0;&#x65E0;&#x54CD;&#x5E94;&#x670D;&#x52A1;&#x5F15;&#x8D77;&#x7684;&#x7EBF;&#x7A0B;&#x963B;&#x585E;</figcaption></figure>
<p>&#x4E3A;&#x4E86;&#x9632;&#x6B62;&#x51FA;&#x73B0;&#x6B64;&#x7C7B;&#x95EE;&#x9898;&#xFF0C;&#x5728;&#x8BBE;&#x8BA1;&#x670D;&#x52A1;&#x65F6;&#x5FC5;&#x987B;&#x8003;&#x8651;&#x5904;&#x7406;&#x5C40;&#x90E8;&#x6545;&#x969C;&#x3002;&#x4EE5;&#x4E0B;&#x662F;&#x4E00;&#x4E2A;&#x7531; <a href="http://techblog.netflix.com/2012/02/fault-tolerance-in-high-volume.html" target="_blank">Netflix &#x7ED9;&#x51FA;&#x7684;&#x597D;&#x65B9;&#x6848;</a>&#x3002;&#x5904;&#x7406;&#x5C40;&#x90E8;&#x6545;&#x969C;&#x7684;&#x7B56;&#x7565;&#x5305;&#x62EC;&#xFF1A;</p>
<ul>
<li><p><strong>&#x7F51;&#x7EDC;&#x8D85;&#x65F6;</strong></p>
<p> &#x5728;&#x7B49;&#x5F85;&#x54CD;&#x5E94;&#x65F6;&#xFF0C;&#x4E0D;&#x8981;&#x65E0;&#x9650;&#x671F;&#x5730;&#x963B;&#x585E;&#xFF0C;&#x59CB;&#x7EC8;&#x4F7F;&#x7528;&#x8D85;&#x65F6;&#x65B9;&#x6848;&#x3002;&#x4F7F;&#x7528;&#x8D85;&#x65F6;&#x65B9;&#x6848;&#x786E;&#x4FDD;&#x8D44;&#x6E90;&#x4E0D;&#x88AB;&#x65E0;&#x9650;&#x5730;&#x6D88;&#x8017;&#x3002;</p>
</li>
<li><p><strong>&#x9650;&#x5236;&#x672A;&#x5B8C;&#x6210;&#x7684;&#x8BF7;&#x6C42;&#x6570;&#x91CF;</strong></p>
<p> &#x5BF9;&#x5BA2;&#x6237;&#x7AEF;&#x8BF7;&#x6C42;&#x7684;&#x67D0;&#x4E9B;&#x670D;&#x52A1;&#xFF0C;&#x8BBE;&#x7F6E;&#x672A;&#x5B8C;&#x6210;&#x8BF7;&#x6C42;&#x7684;&#x6570;&#x91CF;&#x4E0A;&#x9650;&#x3002;&#x5982;&#x679C;&#x8FBE;&#x5230;&#x4E86;&#x4E0A;&#x9650;&#xFF0C;&#x53D1;&#x51FA;&#x7684;&#x989D;&#x5916;&#x8BF7;&#x6C42;&#x53EF;&#x4EE5;&#x89C6;&#x4E3A;&#x6BEB;&#x65E0;&#x610F;&#x4E49;&#xFF0C;&#x56E0;&#x6B64;&#x8FD9;&#x4E9B;&#x5C1D;&#x8BD5;&#x9700;&#x8981;&#x7ACB;&#x5373;&#x5931;&#x8D25;&#x3002;</p>
</li>
<li><p><strong><a href="http://martinfowler.com/bliki/CircuitBreaker.html" target="_blank">&#x65AD;&#x8DEF;&#x5668;&#x6A21;&#x5F0F;</a></strong></p>
<p> &#x8FFD;&#x8E2A;&#x6210;&#x529F;&#x548C;&#x5931;&#x8D25;&#x8BF7;&#x6C42;&#x7684;&#x6570;&#x91CF;&#x3002;&#x5982;&#x679C;&#x9519;&#x8BEF;&#x7387;&#x8D85;&#x8FC7;&#x914D;&#x7F6E;&#x9608;&#x503C;&#xFF0C;&#x5219;&#x65AD;&#x5F00;&#x65AD;&#x8DEF;&#x5668;&#xFF0C;&#x4EE5;&#x4FBF;&#x540E;&#x7EED;&#x7684;&#x5C1D;&#x8BD5;&#x80FD;&#x7ACB;&#x5373;&#x5931;&#x8D25;&#x3002;&#x5982;&#x679C;&#x51FA;&#x73B0;&#x5927;&#x91CF;&#x8BF7;&#x6C42;&#x5931;&#x8D25;&#xFF0C;&#x5219;&#x8868;&#x660E;&#x670D;&#x52A1;&#x4E0D;&#x53EF;&#x7528;&#xFF0C;&#x53D1;&#x9001;&#x8BF7;&#x6C42;&#x5C06;&#x6BEB;&#x65E0;&#x610F;&#x4E49;&#x3002;&#x53D1;&#x751F;&#x8D85;&#x65F6;&#x540E;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x5E94;&#x91CD;&#x65B0;&#x5C1D;&#x8BD5;&#xFF0C;&#x5982;&#x679C;&#x6210;&#x529F;&#xFF0C;&#x5219;&#x5173;&#x95ED;&#x65AD;&#x8DEF;&#x5668;&#x3002;</p>
</li>
<li><p><strong>&#x63D0;&#x4F9B;&#x56DE;&#x9000;</strong></p>
<p> &#x8BF7;&#x6C42;&#x5931;&#x8D25;&#x65F6;&#x6267;&#x884C;&#x56DE;&#x9000;&#x903B;&#x8F91;&#x3002;&#x4F8B;&#x5982;&#xFF0C;&#x8FD4;&#x56DE;&#x7F13;&#x5B58;&#x6570;&#x636E;&#x6216;&#x8005;&#x9ED8;&#x8BA4;&#x503C;&#xFF0C;&#x53EF;&#x4EE5;&#x662F;&#x4E00;&#x7EC4;&#x7A7A;&#x767D;&#x7684;&#x63A8;&#x8350;&#x6570;&#x636E;&#x3002;</p>
</li>
</ul>
<p><a href="https://github.com/Netflix/Hystrix" target="_blank">Netflix Hystrix</a> &#x662F;&#x4E00;&#x4E2A;&#x5B9E;&#x73B0;&#x4E0A;&#x8FF0;&#x6A21;&#x5F0F;&#x548C;&#x5176;&#x4ED6;&#x6A21;&#x5F0F;&#x7684;&#x5F00;&#x6E90;&#x5E93;&#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;&#x5728;&#x975E; JVM &#x73AF;&#x5883;&#x4E2D;&#x8FD0;&#x884C;&#xFF0C;&#x5219;&#x5E94;&#x4F7F;&#x7528;&#x540C;&#x7B49;&#x4F5C;&#x7528;&#x7684;&#x5E93;&#x3002;</p>
<p><a id="ipc-technologies"></a></p>
<h2 id="36&#x3001;ipc-&#x6280;&#x672F;">3.6&#x3001;IPC &#x6280;&#x672F;</h2>
<p>&#x6709;&#x591A;&#x79CD; IPC &#x6280;&#x672F;&#x53EF;&#x4F9B;&#x9009;&#x62E9;&#x3002;&#x670D;&#x52A1;&#x53EF;&#x4EE5;&#x4F7F;&#x7528;&#x57FA;&#x4E8E;&#x540C;&#x6B65;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x7684;&#x901A;&#x4FE1;&#x673A;&#x5236;&#xFF0C;&#x6BD4;&#x5982;&#x57FA;&#x4E8E; HTTP &#x7684; REST &#x6216; Thrift&#x3002;&#x6216;&#x8005;&#xFF0C;&#x53EF;&#x4EE5;&#x4F7F;&#x7528;&#x5F02;&#x6B65;&#x3001;&#x57FA;&#x4E8E;&#x6D88;&#x606F;&#x7684;&#x901A;&#x4FE1;&#x673A;&#x5236;&#xFF0C;&#x5982; AMQP &#x6216; STOMP&#x3002;</p>
<p>&#x8FD8;&#x6709;&#x5404;&#x79CD;&#x4E0D;&#x540C;&#x7684;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#x3002;&#x670D;&#x52A1;&#x53EF;&#x4EE5;&#x4F7F;&#x7528;&#x53EF;&#x8BFB;&#x7684;&#x3001;&#x57FA;&#x4E8E;&#x6587;&#x672C;&#x7684;&#x683C;&#x5F0F;&#xFF0C;&#x5982; JSON &#x6216; XML&#x3002;&#x6216;&#x8005;&#xFF0C;&#x53EF;&#x4EE5;&#x4F7F;&#x7528;&#x5982; Avro &#x6216; Protocol Buffers &#x7B49;&#x4E8C;&#x8FDB;&#x5236;&#x683C;&#x5F0F;&#xFF08;&#x66F4;&#x52A0;&#x9AD8;&#x6548;&#xFF09;&#x3002;&#x7A0D;&#x540E;&#x6211;&#x4EEC;&#x5C06;&#x8BA8;&#x8BBA;&#x540C;&#x6B65; IPC &#x673A;&#x5236;&#xFF0C;&#x4F46;&#x5728;&#x6B64;&#x4E4B;&#x524D;&#x8BA9;&#x6211;&#x4EEC;&#x5148;&#x6765;&#x8BA8;&#x8BBA;&#x4E00;&#x4E0B;&#x5F02;&#x6B65; IPC &#x673A;&#x5236;&#x3002;</p>
<p><a id="asynchronous-message-based-communication"></a></p>
<h2 id="37&#x3001;&#x5F02;&#x6B65;&#x3001;&#x57FA;&#x4E8E;&#x6D88;&#x606F;&#x7684;&#x901A;&#x4FE1;">3.7&#x3001;&#x5F02;&#x6B65;&#x3001;&#x57FA;&#x4E8E;&#x6D88;&#x606F;&#x7684;&#x901A;&#x4FE1;</h2>
<p>&#x5F53;&#x4F7F;&#x7528;&#x6D88;&#x606F;&#x4F20;&#x9012;&#x65F6;&#xFF0C;&#x8FDB;&#x7A0B;&#x901A;&#x8FC7;&#x5F02;&#x6B65;&#x4EA4;&#x6362;&#x6D88;&#x606F;&#x8FDB;&#x884C;&#x901A;&#x4FE1;&#x3002;&#x5BA2;&#x6237;&#x7AEF;&#x901A;&#x8FC7;&#x53D1;&#x9001;&#x6D88;&#x606F;&#x5411;&#x670D;&#x52A1;&#x53D1;&#x51FA;&#x8BF7;&#x6C42;&#x3002;&#x5982;&#x679C;&#x670D;&#x52A1;&#x9700;&#x8981;&#x56DE;&#x590D;&#xFF0C;&#x5219;&#x901A;&#x8FC7;&#x5411;&#x5BA2;&#x6237;&#x7AEF;&#x53D1;&#x9001;&#x4E00;&#x6761;&#x5355;&#x72EC;&#x7684;&#x6D88;&#x606F;&#x6765;&#x5B9E;&#x73B0;&#x3002;&#x7531;&#x4E8E;&#x901A;&#x4FE1;&#x662F;&#x5F02;&#x6B65;&#x7684;&#xFF0C;&#x56E0;&#x6B64;&#x5BA2;&#x6237;&#x7AEF;&#x4E0D;&#x4F1A;&#x963B;&#x585E;&#x7B49;&#x5F85;&#x56DE;&#x590D;&#x3002;&#x76F8;&#x53CD;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x88AB;&#x5047;&#x5B9A;&#x4E0D;&#x4F1A;&#x7ACB;&#x5373;&#x6536;&#x5230;&#x56DE;&#x590D;&#x3002;</p>
<p>&#x4E00;&#x6761;<a href="http://www.enterpriseintegrationpatterns.com/patterns/messaging/Message.html" target="_blank">&#x6D88;&#x606F;</a>&#x7531;&#x5934;&#x90E8;&#xFF08;&#x5982;&#x53D1;&#x4EF6;&#x4EBA;&#x4E4B;&#x7C7B;&#x7684;&#x5143;&#x6570;&#x636E;&#xFF09;&#x548C;&#x6D88;&#x606F;&#x4F53;&#x7EC4;&#x6210;&#x3002;&#x6D88;&#x606F;&#x901A;&#x8FC7;<a href="http://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageChannel.html" target="_blank">&#x901A;&#x9053;</a>&#x8FDB;&#x884C;&#x4EA4;&#x6362;&#x3002;&#x4EFB;&#x4F55;&#x6570;&#x91CF;&#x7684;&#x751F;&#x4EA7;&#x8005;&#x90FD;&#x53EF;&#x4EE5;&#x5411;&#x901A;&#x9053;&#x53D1;&#x9001;&#x6D88;&#x606F;&#x3002;&#x7C7B;&#x4F3C;&#x5730;&#xFF0C;&#x4EFB;&#x4F55;&#x6570;&#x91CF;&#x7684;&#x6D88;&#x8D39;&#x8005;&#x90FD;&#x53EF;&#x4EE5;&#x4ECE;&#x901A;&#x9053;&#x63A5;&#x6536;&#x6D88;&#x606F;&#x3002;&#x6709;&#x4E24;&#x79CD;&#x901A;&#x9053;&#x7C7B;&#x578B;&#xFF0C;&#x5206;&#x522B;&#x662F;<a href="http://www.enterpriseintegrationpatterns.com/patterns/messaging/PointToPointChannel.html" target="_blank">&#x70B9;&#x5BF9;&#x70B9;</a>&#xFF08;point&#x2011;to&#x2011;point&#xFF09;&#x4E0E;<a href="http://www.enterpriseintegrationpatterns.com/patterns/messaging/PublishSubscribeChannel.html" target="_blank">&#x53D1;&#x5E03;&#x8BA2;&#x9605;</a>&#xFF08;publish&#x2011;subscribe&#xFF09;&#xFF1A;</p>
<ul>
<li><strong>&#x70B9;&#x5BF9;&#x70B9;&#x901A;&#x9053;</strong>&#x53D1;&#x9001;&#x4E00;&#x6761;&#x6D88;&#x606F;&#x7ED9;&#x4E00;&#x4E2A;&#x5207;&#x786E;&#x7684;&#x3001;&#x6B63;&#x5728;&#x4ECE;&#x901A;&#x9053;&#x8BFB;&#x53D6;&#x6D88;&#x606F;&#x7684;&#x6D88;&#x8D39;&#x8005;&#x3002;&#x670D;&#x52A1;&#x4F7F;&#x7528;&#x70B9;&#x5BF9;&#x70B9;&#x901A;&#x9053;&#xFF0C;&#x5C31;&#x662F;&#x4E0A;&#x8FF0;&#x7684;&#x4E00;&#x5BF9;&#x4E00;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#x3002;</li>
<li><strong>&#x53D1;&#x5E03;&#x8BA2;&#x9605;&#x901A;&#x9053;</strong>&#x5C06;&#x6BCF;&#x6761;&#x6D88;&#x606F;&#x4F20;&#x9012;&#x7ED9;&#x6240;&#x6709;&#x5DF2;&#x8BA2;&#x9605;&#x7684;&#x6D88;&#x8D39;&#x8005;&#x3002;&#x670D;&#x52A1;&#x4F7F;&#x7528;&#x53D1;&#x5E03;&#x8BA2;&#x9605;&#x901A;&#x9053;&#xFF0C;&#x5C31;&#x662F;&#x4E0A;&#x8FF0;&#x7684;&#x4E00;&#x5BF9;&#x591A;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#x3002;</li>
</ul>
<p>&#x56FE; 3-4 &#x5C55;&#x793A;&#x4E86;&#x6253;&#x8F66;&#x5E94;&#x7528;&#x5982;&#x4F55;&#x4F7F;&#x7528;&#x53D1;&#x5E03;&#x8BA2;&#x9605;&#x901A;&#x9053;&#x3002;</p>
<figure id="fig1.5.4"><img src="resources/3-4.png" alt="&#x4F7F;&#x7528;&#x4E86;&#x53D1;&#x5E03;/&#x8BA2;&#x9605;&#x901A;&#x9053;&#x7684;&#x6253;&#x8F66;&#x5E94;&#x7528;"><figcaption>&#x4F7F;&#x7528;&#x4E86;&#x53D1;&#x5E03;/&#x8BA2;&#x9605;&#x901A;&#x9053;&#x7684;&#x6253;&#x8F66;&#x5E94;&#x7528;</figcaption></figure>
<p>Trip Management &#x670D;&#x52A1;&#x901A;&#x8FC7;&#x5411;&#x53D1;&#x5E03;&#x8BA2;&#x9605;&#x901A;&#x9053;&#x5199;&#x5165; Trip Created &#x6D88;&#x606F;&#x6765;&#x901A;&#x77E5;&#x5DF2;&#x8BA2;&#x9605;&#x7684;&#x670D;&#x52A1;&#xFF0C;&#x5982; Dispatcher&#x3002;Dispatcher &#x627E;&#x5230;&#x53EF;&#x7528;&#x7684;&#x53F8;&#x673A;&#x5E76;&#x901A;&#x8FC7;&#x5411;&#x53D1;&#x5E03;&#x8BA2;&#x9605;&#x901A;&#x9053;&#x5199;&#x5165; Driver Proposed &#x6D88;&#x606F;&#x6765;&#x901A;&#x77E5;&#x5176;&#x4ED6;&#x670D;&#x52A1;&#x3002;</p>
<p>&#x6709;&#x8BB8;&#x591A;&#x6D88;&#x606F;&#x7CFB;&#x7EDF;&#x53EF;&#x4F9B;&#x9009;&#x62E9;&#xFF0C;&#x4F60;&#x5E94;&#x8BE5;&#x9009;&#x62E9;&#x4E00;&#x4E2A;&#x652F;&#x6301;&#x591A;&#x79CD;&#x7F16;&#x7A0B;&#x8BED;&#x8A00;&#x7684;&#x3002;</p>
<p>&#x4E00;&#x4E9B;&#x6D88;&#x606F;&#x7CFB;&#x7EDF;&#x652F;&#x6301;&#x6807;&#x51C6;&#x534F;&#x8BAE;&#xFF0C;&#x5982; AMQP &#x548C; STOMP&#x3002;&#x5176;&#x4ED6;&#x6D88;&#x606F;&#x7CFB;&#x7EDF;&#x6709;&#x4E13;&#x6709;&#x7684;&#x6587;&#x6863;&#x5316;&#x534F;&#x8BAE;&#x3002;</p>
<p>&#x6709;&#x5927;&#x91CF;&#x7684;&#x5F00;&#x6E90;&#x6D88;&#x606F;&#x7CFB;&#x7EDF;&#x53EF;&#x4F9B;&#x9009;&#x62E9;&#xFF0C;&#x5305;&#x62EC; <a href="http://www.rabbitmq.com/" target="_blank">RabbitMQ</a>&#x3001;<a href="http://kafka.apache.org/" target="_blank">Apache Kafka</a>&#x3001;<a href="http://activemq.apache.org/" target="_blank">Apache ActiveMQ</a> &#x548C; <a href="https://github.com/bitly/nsq" target="_blank">NSQ</a>&#x3002;&#x4ECE;&#x9AD8;&#x5C42;&#x800C;&#x8A00;&#xFF0C;&#x4ED6;&#x4EEC;&#x90FD;&#x652F;&#x6301;&#x67D0;&#x79CD;&#x5F62;&#x5F0F;&#x7684;&#x6D88;&#x606F;&#x548C;&#x901A;&#x9053;&#x3002;&#x4ED6;&#x4EEC;&#x90FD;&#x529B;&#x6C42;&#x505A;&#x5230;&#x53EF;&#x9760;&#x3001;&#x9AD8;&#x6027;&#x80FD;&#x548C;&#x53EF;&#x6269;&#x5C55;&#x3002;&#x7136;&#x800C;&#xFF0C;&#x6BCF;&#x4E2A;&#x4EE3;&#x7406;&#x7684;&#x6D88;&#x606F;&#x4F20;&#x9012;&#x6A21;&#x578B;&#x7EC6;&#x8282;&#x4E0A;&#x90FD;&#x5B58;&#x5728;&#x7740;&#x5F88;&#x5927;&#x5DEE;&#x5F02;&#x3002;</p>
<p>&#x4F7F;&#x7528;&#x6D88;&#x606F;&#x4F20;&#x9012;&#x6709;&#x5F88;&#x591A;&#x4F18;&#x70B9;&#xFF1A;</p>
<ul>
<li><p><strong>&#x5C06;&#x5BA2;&#x6237;&#x7AEF;&#x4E0E;&#x670D;&#x52A1;&#x5206;&#x79BB;</strong></p>
<p> &#x5BA2;&#x6237;&#x7AEF;&#x901A;&#x8FC7;&#x5411;&#x76F8;&#x5E94;&#x7684;&#x901A;&#x9053;&#x53D1;&#x9001;&#x4E00;&#x6761;&#x6D88;&#x606F;&#x6765;&#x7B80;&#x5355;&#x5730;&#x53D1;&#x51FA;&#x4E00;&#x4E2A;&#x8BF7;&#x6C42;&#x3002;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x5BF9;&#x5BA2;&#x6237;&#x7AEF;&#x800C;&#x8A00;&#x662F;&#x900F;&#x660E;&#x7684;&#x3002;&#x5BA2;&#x6237;&#x7AEF;&#x4E0D;&#x9700;&#x8981;&#x4F7F;&#x7528;&#x53D1;&#x73B0;&#x673A;&#x5236;&#x6765;&#x786E;&#x5B9A;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x7684;&#x4F4D;&#x7F6E;&#x3002;</p>
</li>
<li><p><strong>&#x6D88;&#x606F;&#x7F13;&#x51B2;</strong></p>
<p> &#x4F7F;&#x7528;&#x5982; HTTP &#x7684;&#x540C;&#x6B65;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x534F;&#x8BAE;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x548C;&#x670D;&#x52A1;&#x5728;&#x4EA4;&#x6362;&#x671F;&#x95F4;&#x5FC5;&#x987B;&#x53EF;&#x7528;&#x3002;&#x76F8;&#x6BD4;&#x4E4B;&#x4E0B;&#xFF0C;&#x6D88;&#x606F;&#x4EE3;&#x7406;&#x4F1A;&#x5C06;&#x6D88;&#x606F;&#x6392;&#x961F;&#x5199;&#x5165;&#x901A;&#x9053;&#xFF0C;&#x76F4;&#x5230;&#x6D88;&#x8D39;&#x8005;&#x5904;&#x7406;&#x5B83;&#x4EEC;&#x3002;&#x8FD9;&#x610F;&#x5473;&#x7740;&#xFF0C;&#x4F8B;&#x5982;&#xFF0C;&#x5373;&#x4F7F;&#x8BA2;&#x5355;&#x6267;&#x884C;&#x7CFB;&#x7EDF;&#x51FA;&#x73B0;&#x7F13;&#x6162;&#x6216;&#x4E0D;&#x53EF;&#x7528;&#x7684;&#x60C5;&#x51B5;&#xFF0C;&#x5728;&#x7EBF;&#x5546;&#x5E97;&#x8FD8;&#x662F;&#x53EF;&#x4EE5;&#x63A5;&#x53D7;&#x5BA2;&#x6237;&#x7684;&#x8BA2;&#x5355;&#x3002;&#x8BA2;&#x5355;&#x6D88;&#x606F;&#x53EA;&#x9700;&#x8981;&#x7B80;&#x5355;&#x5730;&#x6392;&#x961F;&#x3002;</p>
</li>
<li><p><strong>&#x7075;&#x6D3B;&#x7684;&#x5BA2;&#x6237;&#x7AEF; &#x2014; &#x670D;&#x52A1;&#x4EA4;&#x4E92;</strong></p>
<p> &#x6D88;&#x606F;&#x4F20;&#x9012;&#x652F;&#x6301;&#x524D;&#x9762;&#x63D0;&#x5230;&#x7684;&#x6240;&#x6709;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#x3002;</p>
</li>
<li><p><strong>&#x6BEB;&#x65E0;&#x9690;&#x7792;&#x7684;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;</strong></p>
<p> &#x57FA;&#x4E8E; RPC &#x7684;&#x673A;&#x5236;&#x8BD5;&#x56FE;&#x4F7F;&#x8C03;&#x7528;&#x8FDC;&#x7A0B;&#x670D;&#x52A1;&#x770B;&#x8D77;&#x6765;&#x4E0E;&#x8C03;&#x7528;&#x672C;&#x5730;&#x670D;&#x52A1;&#x76F8;&#x540C;&#x3002;&#x7136;&#x800C;&#xFF0C;&#x7531;&#x4E8E;&#x7269;&#x7406;&#x56E0;&#x7D20;&#x548C;&#x5C40;&#x90E8;&#x6545;&#x969C;&#x7684;&#x53EF;&#x80FD;&#x6027;&#xFF0C;&#x4ED6;&#x4EEC;&#x5B9E;&#x9645;&#x4E0A;&#x662F;&#x5B8C;&#x5168;&#x4E0D;&#x540C;&#x7684;&#x3002;&#x6D88;&#x606F;&#x4F20;&#x9012;&#x4F7F;&#x8FD9;&#x4E9B;&#x5DEE;&#x5F02;&#x53D8;&#x5F97;&#x975E;&#x5E38;&#x660E;&#x663E;&#xFF0C;&#x6240;&#x4EE5;&#x5F00;&#x53D1;&#x4EBA;&#x5458;&#x4E0D;&#x4F1A;&#x88AB;&#x8FD9;&#x4E9B;&#x865A;&#x5047;&#x7684;&#x5B89;&#x5168;&#x611F;&#x6240;&#x6B3A;&#x9A97;&#x3002;</p>
</li>
</ul>
<p>&#x7136;&#x800C;&#xFF0C;&#x6D88;&#x606F;&#x4F20;&#x9012;&#x4E5F;&#x5B58;&#x5728;&#x4E00;&#x4E9B;&#x7F3A;&#x70B9;&#xFF1A;</p>
<ul>
<li><p><strong>&#x989D;&#x5916;&#x7684;&#x590D;&#x6742;&#x64CD;&#x4F5C;</strong></p>
<p> &#x6D88;&#x606F;&#x4F20;&#x9012;&#x7CFB;&#x7EDF;&#x662F;&#x4E00;&#x4E2A;&#x9700;&#x8981;&#x5B89;&#x88C5;&#x3001;&#x914D;&#x7F6E;&#x548C;&#x64CD;&#x4F5C;&#x7684;&#x7CFB;&#x7EDF;&#x7EC4;&#x4EF6;&#x3002;&#x6D88;&#x606F;&#x4EE3;&#x7406;&#x7A0B;&#x5E8F;&#x5FC5;&#x987B;&#x9AD8;&#x5EA6;&#x53EF;&#x7528;&#xFF0C;&#x5426;&#x5219;&#x7CFB;&#x7EDF;&#x7684;&#x53EF;&#x9760;&#x6027;&#x5C06;&#x53D7;&#x5230;&#x5F71;&#x54CD;&#x3002;</p>
</li>
<li><p><strong>&#x5B9E;&#x73B0;&#x57FA;&#x4E8E;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x5F0F;&#x4EA4;&#x4E92;&#x7684;&#x590D;&#x6742;&#x6027;</strong></p>
<p> &#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x5F0F;&#x4EA4;&#x4E92;&#x9700;&#x8981;&#x505A;&#x4E9B;&#x5DE5;&#x4F5C;&#x6765;&#x5B9E;&#x73B0;&#x3002;&#x6BCF;&#x4E2A;&#x8BF7;&#x6C42;&#x6D88;&#x606F;&#x5FC5;&#x987B;&#x5305;&#x542B;&#x5E94;&#x7B54;&#x901A;&#x9053;&#x6807;&#x8BC6;&#x7B26;&#x548C;&#x76F8;&#x5173;&#x6807;&#x8BC6;&#x7B26;&#x3002;&#x8BE5;&#x670D;&#x52A1;&#x5C06;&#x5305;&#x542B;&#x76F8;&#x5173; ID &#x7684;&#x54CD;&#x5E94;&#x6D88;&#x606F;&#x5199;&#x5165;&#x5E94;&#x7B54;&#x4FE1;&#x9053;&#x3002;&#x5BA2;&#x6237;&#x7AEF;&#x4F7F;&#x7528;&#x76F8;&#x5173; ID &#x5C06;&#x54CD;&#x5E94;&#x4E0E;&#x8BF7;&#x6C42;&#x76F8;&#x5339;&#x914D;&#x3002;&#x901A;&#x5E38;&#x4F7F;&#x7528;&#x76F4;&#x63A5;&#x652F;&#x6301;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x7684; IPC &#x673A;&#x5236;&#x66F4;&#x52A0;&#x5BB9;&#x6613;&#x3002;</p>
</li>
</ul>
<p>&#x73B0;&#x5728;&#x6211;&#x4EEC;&#x5DF2;&#x7ECF;&#x4E86;&#x89E3;&#x4E86;&#x4F7F;&#x7528;&#x57FA;&#x4E8E;&#x6D88;&#x606F;&#x7684; IPC&#xFF0C;&#x8BA9;&#x6211;&#x4EEC;&#x6765;&#x770B;&#x770B;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x7684; IPC&#x3002;</p>
<p><a id="synchronous-request-response-ipc"></a></p>
<h2 id="38&#x3001;&#x540C;&#x6B65;&#x7684;&#x8BF7;&#x6C42;&#x54CD;&#x5E94;-ipc">3.8&#x3001;&#x540C;&#x6B65;&#x7684;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94; IPC</h2>
<p>&#x5F53;&#x4F7F;&#x7528;&#x57FA;&#x4E8E;&#x540C;&#x6B65;&#x3001;&#x57FA;&#x4E8E;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x7684; IPC &#x673A;&#x5236;&#x65F6;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x5411;&#x670D;&#x52A1;&#x5668;&#x53D1;&#x9001;&#x8BF7;&#x6C42;&#x3002;&#x670D;&#x52A1;&#x5904;&#x7406;&#x8BE5;&#x8BF7;&#x6C42;&#x5E76;&#x8FD4;&#x56DE;&#x54CD;&#x5E94;&#x3002;</p>
<p>&#x5728;&#x8BB8;&#x591A;&#x5BA2;&#x6237;&#x7AEF;&#x4E2D;&#xFF0C;&#x8BF7;&#x6C42;&#x7684;&#x7EBF;&#x7A0B;&#x5728;&#x7B49;&#x5F85;&#x54CD;&#x5E94;&#x65F6;&#x88AB;&#x963B;&#x585E;&#x3002;&#x5176;&#x4ED6;&#x5BA2;&#x6237;&#x7AEF;&#x53EF;&#x80FD;&#x4F1A;&#x4F7F;&#x7528;&#x5230;&#x5F02;&#x6B65;&#x3001;&#x4E8B;&#x4EF6;&#x9A71;&#x52A8;&#x7684;&#x5BA2;&#x6237;&#x7AEF;&#x4EE3;&#x7801;&#xFF0C;&#x8FD9;&#x4E9B;&#x4EE3;&#x7801;&#x53EF;&#x80FD;&#x662F;&#x7531; <a href="http://docs.scala-lang.org/overviews/core/futures.html" target="_blank">Futures</a> &#x6216; <a href="http://reactivex.io/documentation/observable.html" target="_blank">Rx Observables</a> &#x5C01;&#x88C5;&#x7684;&#x3002;&#x7136;&#x800C;&#xFF0C;&#x4E0E;&#x4F7F;&#x7528;&#x6D88;&#x606F;&#x4F20;&#x9012;&#x4E0D;&#x540C;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x5047;&#x5B9A;&#x54CD;&#x5E94;&#x80FD;&#x53CA;&#x65F6;&#x5230;&#x8FBE;&#x3002;</p>
<p>&#x6709;&#x8BB8;&#x591A;&#x534F;&#x8BAE;&#x53EF;&#x4F9B;&#x9009;&#x62E9;&#xFF0C;&#x5176;&#x4E2D;&#x6709;&#x4E24;&#x79CD;&#x6D41;&#x884C;&#x534F;&#x8BAE;&#x5206;&#x522B;&#x662F; REST &#x548C; Thrift&#x3002;&#x6211;&#x4EEC;&#x5148;&#x6765;&#x770B;&#x4E00;&#x4E0B; REST&#x3002;</p>
<p><a id="rest"></a></p>
<h3 id="381&#x3001;rest">3.8.1&#x3001;REST</h3>
<p>&#x5982;&#x4ECA;&#xFF0C;&#x5F00;&#x53D1; <a href="https://en.wikipedia.org/wiki/Representational_state_transfer" target="_blank">RESTful</a> &#x98CE;&#x683C;&#x7684; API &#x53D8;&#x5F97;&#x975E;&#x5E38;&#x6D41;&#x884C;&#x3002;REST &#x662F;&#x4E00;&#x79CD;&#x4F7F;&#x7528;&#x4E86; HTTP &#xFF08;&#x51E0;&#x4E4E;&#x603B;&#x662F;&#xFF09;&#x7684; IPC &#x673A;&#x5236;&#x3002;</p>
<p>&#x8D44;&#x6E90;&#x662F; REST &#x4E2D;&#x7684;&#x4E00;&#x4E2A;&#x5173;&#x952E;&#x6982;&#x5FF5;&#xFF0C;&#x5B83;&#x901A;&#x5E38;&#x7528;&#x4E8E;&#x8868;&#x793A;&#x4E1A;&#x52A1;&#x5BF9;&#x8C61;&#xFF0C;&#x5982;&#x5BA2;&#x6237;&#x3001;&#x4EA7;&#x54C1;&#x6216;&#x8FD9;&#x4E9B;&#x4E1A;&#x52A1;&#x5BF9;&#x8C61;&#x7684;&#x96C6;&#x5408;&#x3002;REST &#x4F7F;&#x7528; HTTP &#x52A8;&#x8BCD;&#xFF08;&#x8C13;&#x8BCD;&#xFF09;&#x6765;&#x64CD;&#x7EB5;&#x8D44;&#x6E90;&#xFF0C;&#x8FD9;&#x4E9B;&#x8D44;&#x6E90;&#x901A;&#x8FC7; URL &#x5F15;&#x7528;&#x3002;&#x4F8B;&#x5982;&#xFF0C;GET &#x8BF7;&#x6C42;&#x8FD4;&#x56DE;&#x4E00;&#x4E2A;&#x8D44;&#x6E90;&#x7684;&#x8868;&#x8FF0;&#x5F62;&#x5F0F;&#xFF0C;&#x53EF;&#x80FD;&#x662F; XML &#x6587;&#x6863;&#x6216; JSON &#x5BF9;&#x8C61;&#x5F62;&#x5F0F;&#x3002;POST &#x8BF7;&#x6C42;&#x521B;&#x5EFA;&#x4E00;&#x4E2A;&#x65B0;&#x8D44;&#x6E90;&#xFF0C;PUT &#x8BF7;&#x6C42;&#x66F4;&#x65B0;&#x4E00;&#x4E2A;&#x8D44;&#x6E90;&#x3002;</p>
<p>&#x5F15;&#x7528; REST &#x521B;&#x5EFA;&#x8005; Roy Fielding &#x7684;&#x8BDD;&#xFF1A;</p>
<blockquote>
<p>&#x201C;REST &#x63D0;&#x4F9B;&#x4E86;&#x4E00;&#x5957;&#x67B6;&#x6784;&#x7EA6;&#x675F;&#xFF0C;&#x5F53;&#x5E94;&#x7528;&#x4F5C;&#x4E3A;&#x6574;&#x4F53;&#x65F6;&#xFF0C;&#x5176;&#x5F3A;&#x8C03;&#x7EC4;&#x4EF6;&#x4EA4;&#x4E92;&#x7684;&#x53EF;&#x6269;&#x5C55;&#x6027;&#x3001;&#x63A5;&#x53E3;&#x7684;&#x901A;&#x7528;&#x6027;&#xFF0C;&#x7EC4;&#x4EF6;&#x7684;&#x72EC;&#x7ACB;&#x90E8;&#x7F72;&#x4EE5;&#x53CA;&#x4E2D;&#x95F4;&#x7EC4;&#x4EF6;&#xFF0C;&#x4EE5;&#x51CF;&#x5C11;&#x4EA4;&#x4E92;&#x5EF6;&#x8FDF;&#x3001;&#x5B9E;&#x65BD;&#x5B89;&#x5168;&#x6027;&#x548C;&#x5C01;&#x88C5;&#x9057;&#x7559;&#x7CFB;&#x7EDF;&#x3002;&#x201D; &#x2014; <strong>Roy Fielding&#xFF0C;<a href="http://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm" target="_blank">&#x300A;&#x67B6;&#x6784;&#x98CE;&#x683C;&#x4E0E;&#x57FA;&#x4E8E;&#x7F51;&#x7EDC;&#x7684;&#x8F6F;&#x4EF6;&#x67B6;&#x6784;&#x8BBE;&#x8BA1;&#x300B;</a></strong></p>
</blockquote>
<p>&#x56FE; 3-5 &#x5C55;&#x793A;&#x4E86;&#x6253;&#x8F66;&#x5E94;&#x7528;&#x53EF;&#x80FD;&#x4F7F;&#x7528; REST &#x7684;&#x65B9;&#x5F0F;&#x4E4B;&#x4E00;&#x3002;</p>
<figure id="fig1.5.5"><img src="resources/3-5.png" alt="&#x4F7F;&#x7528;&#x4E86; RESTful &#x4EA4;&#x4E92;&#x7684;&#x6253;&#x8F66;&#x5E94;&#x7528;"><figcaption>&#x4F7F;&#x7528;&#x4E86; RESTful &#x4EA4;&#x4E92;&#x7684;&#x6253;&#x8F66;&#x5E94;&#x7528;</figcaption></figure>
<p>&#x4E58;&#x5BA2;&#x7684;&#x667A;&#x80FD;&#x624B;&#x673A;&#x901A;&#x8FC7;&#x5411; Trip Management &#x670D;&#x52A1;&#x7684; <code>/trips</code> &#x8D44;&#x6E90;&#x53D1;&#x51FA;&#x4E00;&#x4E2A; POST &#x8BF7;&#x6C42;&#x6765;&#x8BF7;&#x6C42;&#x65C5;&#x7A0B;&#x3002;&#x8BE5;&#x670D;&#x52A1;&#x901A;&#x8FC7;&#x5411; Passenger Management &#x670D;&#x52A1;&#x53D1;&#x9001;&#x4E00;&#x4E2A;&#x83B7;&#x53D6;&#x4E58;&#x5BA2;&#x4FE1;&#x606F;&#x7684; GET &#x8BF7;&#x6C42;&#x6765;&#x5904;&#x7406;&#x8BE5;&#x8BF7;&#x6C42;&#x3002;&#x5728;&#x9A8C;&#x8BC1;&#x4E58;&#x5BA2;&#x6709;&#x6743;&#x9650;&#x521B;&#x5EFA;&#x65C5;&#x7A0B;&#x540E;&#xFF0C;Trip Management &#x670D;&#x52A1;&#x5C06;&#x521B;&#x5EFA;&#x65C5;&#x7A0B;&#xFF0C;&#x5E76;&#x5411;&#x667A;&#x80FD;&#x624B;&#x673A;&#x8FD4;&#x56DE; 201 &#x54CD;&#x5E94;&#x3002;</p>
<p>&#x8BB8;&#x591A;&#x5F00;&#x53D1;&#x4EBA;&#x5458;&#x58F0;&#x79F0;&#x5176;&#x57FA;&#x4E8E; HTTP &#x7684; API &#x5C31;&#x662F; RESTful&#x3002;&#x7136;&#x800C;&#xFF0C;&#x6B63;&#x5982; Fielding &#x5728;&#x90A3;&#x7BC7;&#x535A;&#x6587;&#x4E2D;&#x6240;&#x63CF;&#x8FF0;&#x7684;&#x90A3;&#x6837;&#xFF0C;&#x5E76;&#x4E0D;&#x90FD;&#x662F;&#x8FD9;&#x6837;&#x3002;</p>
<p>Leonard Richardson &#x5B9A;&#x4E49;&#x4E86;&#x4E00;&#x4E2A;&#x975E;&#x5E38;&#x6709;&#x7528;&#x7684; <a href="https://martinfowler.com/articles/richardsonMaturityModel.html" target="_blank">REST &#x6210;&#x719F;&#x5EA6;&#x6A21;&#x578B;</a>&#xFF0C;&#x5305;&#x62EC;&#x4EE5;&#x4E0B;&#x5C42;&#x6B21;&#xFF1A;</p>
<ul>
<li><p><strong>&#x7EA7;&#x522B; 0</strong></p>
<p> &#x7EA7;&#x522B; 0 &#x7684; API &#x7684;&#x5BA2;&#x6237;&#x7AEF;&#x901A;&#x8FC7;&#x5411;&#x5176;&#x552F;&#x4E00;&#x7684; URL &#x7AEF;&#x70B9;&#x53D1;&#x9001; HTTP POST &#x8BF7;&#x6C42;&#x6765;&#x8C03;&#x7528;&#x8BE5;&#x670D;&#x52A1;&#x3002;&#x6BCF;&#x4E2A;&#x8BF7;&#x6C42;&#x88AB;&#x6307;&#x5B9A;&#x8981;&#x6267;&#x884C;&#x7684;&#x64CD;&#x4F5C;&#x3001;&#x64CD;&#x4F5C;&#x7684;&#x76EE;&#x6807;&#xFF08;&#x5982;&#x4E1A;&#x52A1;&#x5BF9;&#x8C61;&#xFF09;&#x4EE5;&#x53CA;&#x53C2;&#x6570;&#x3002;</p>
</li>
<li><p><strong>&#x7EA7;&#x522B; 1</strong></p>
<p> &#x7EA7;&#x522B; 1 &#x7684; API &#x652F;&#x6301;&#x8D44;&#x6E90;&#x6982;&#x5FF5;&#x3002;&#x8981;&#x5BF9;&#x8D44;&#x6E90;&#x6267;&#x884C;&#x64CD;&#x4F5C;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x4F1A;&#x521B;&#x5EFA;&#x4E00;&#x4E2A; POST &#x8BF7;&#x6C42;&#xFF0C;&#x6307;&#x5B9A;&#x8981;&#x6267;&#x884C;&#x7684;&#x64CD;&#x4F5C;&#x548C;&#x53C2;&#x6570;&#x3002;</p>
</li>
<li><p><strong>&#x7EA7;&#x522B; 2</strong></p>
<p> &#x7EA7;&#x522B; 2 &#x7684; API &#x4F7F;&#x7528; HTTP &#x52A8;&#x8BCD;&#xFF08;&#x8C13;&#x8BCD;&#xFF09;&#x6267;&#x884C;&#x64CD;&#x4F5C;&#xFF1A;&#x4F7F;&#x7528; GET &#x68C0;&#x7D22;&#x3001;&#x4F7F;&#x7528; POST &#x521B;&#x5EFA;&#x548C;&#x4F7F;&#x7528; PUT &#x8FDB;&#x884C;&#x66F4;&#x65B0;&#x3002;&#x8BF7;&#x6C42;&#x67E5;&#x8BE2;&#x53C2;&#x6570;&#x548C;&#x8BF7;&#x6C42;&#x4F53;&#xFF08;&#x5982;&#x679C;&#x6709;&#xFF09;&#x6307;&#x5B9A;&#x64CD;&#x4F5C;&#x7684;&#x53C2;&#x6570;&#x3002;&#x8FD9;&#x4F7F;&#x670D;&#x52A1;&#x80FD;&#x591F;&#x5229;&#x7528;&#x5230; Web &#x7684;&#x57FA;&#x7840;&#x7279;&#x6027;&#xFF0C;&#x5982;&#x7F13;&#x5B58; GET &#x8BF7;&#x6C42;&#x3002;</p>
</li>
<li><p><strong>&#x7EA7;&#x522B; 3</strong></p>
<p> &#x7EA7;&#x522B; 3 &#x7684; API &#x57FA;&#x4E8E;&#x975E;&#x5E38;&#x89C4;&#x547D;&#x540D;&#x539F;&#x5219;&#x8BBE;&#x8BA1;&#xFF0C;HATEOAS&#xFF08;Hypermedia as the engine of application state&#xFF0C;&#x8D85;&#x5A92;&#x4F53;&#x5373;&#x5E94;&#x7528;&#x72B6;&#x6001;&#x5F15;&#x64CE;&#xFF09;&#x3002;&#x57FA;&#x672C;&#x601D;&#x60F3;&#x662F; GET &#x8BF7;&#x6C42;&#x8FD4;&#x56DE;&#x7684;&#x8D44;&#x6E90;&#x7684;&#x8868;&#x8FF0;&#xFF0C;&#x5305;&#x542B;&#x7528;&#x4E8E;&#x6267;&#x884C;&#x8BE5;&#x8D44;&#x6E90;&#x5141;&#x8BB8;&#x7684;&#x64CD;&#x4F5C;&#x7684;&#x94FE;&#x63A5;&#x3002;&#x4F8B;&#x5982;&#xFF0C;&#x53D1;&#x9001; GET &#x8BF7;&#x6C42;&#x68C0;&#x7D22;&#x8BA2;&#x5355;&#xFF0C;&#x8FD4;&#x56DE;&#x7684;&#x8BA2;&#x5355;&#x54CD;&#x5E94;&#x4E2D;&#x5305;&#x542B;&#x53D6;&#x6D88;&#x8BA2;&#x5355;&#x94FE;&#x63A5;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x53EF;&#x4EE5;&#x7528;&#x8BE5;&#x94FE;&#x63A5;&#x6765;&#x53D6;&#x6D88;&#x8BA2;&#x5355;&#x3002;HATEOAS &#x7684;&#x4E00;&#x4E2A;<a href="http://www.infoq.com/news/2009/04/hateoas-restful-api-advantages" target="_blank">&#x597D;&#x5904;</a>&#x662F;&#x4E0D;&#x518D;&#x9700;&#x8981;&#x5C06; URL &#x786C;&#x7F16;&#x7801;&#x5728;&#x5BA2;&#x6237;&#x7AEF;&#x4EE3;&#x7801;&#x4E2D;&#x3002;&#x53E6;&#x4E00;&#x4E2A;&#x597D;&#x5904;&#x662F;&#xFF0C;&#x7531;&#x4E8E;&#x8D44;&#x6E90;&#x7684;&#x8868;&#x793A;&#x5305;&#x542B;&#x53EF;&#x5141;&#x8BB8;&#x64CD;&#x4F5C;&#x7684;&#x94FE;&#x63A5;&#xFF0C;&#x6240;&#x4EE5;&#x5BA2;&#x6237;&#x7AEF;&#x4E0D;&#x5FC5;&#x731C;&#x6D4B;&#x53EF;&#x4EE5;&#x5BF9;&#x5F53;&#x524D;&#x72B6;&#x6001;&#x7684;&#x8D44;&#x6E90;&#x6267;&#x884C;&#x4EC0;&#x4E48;&#x64CD;&#x4F5C;&#x3002;</p>
</li>
</ul>
<p>&#x4F7F;&#x7528;&#x57FA;&#x4E8E; HTTP &#x7684;&#x534F;&#x8BAE;&#x6709;&#x5F88;&#x591A;&#x597D;&#x5904;&#xFF1A;</p>
<ul>
<li>HTTP &#x7B80;&#x5355;&#x6613;&#x61C2;&#x3002;</li>
<li>&#x4F60;&#x53EF;&#x4EE5;&#x4F7F;&#x7528;&#x6D4F;&#x89C8;&#x5668;&#x6269;&#x5C55;&#xFF08;&#x5982; <a href="https://www.getpostman.com/" target="_blank">Postman</a>&#xFF09;&#x6765;&#x6D4B;&#x8BD5; HTTP API&#xFF0C;&#x6216;&#x8005;&#x4F7F;&#x7528; curl &#x547D;&#x4EE4;&#x884C;&#x6D4B;&#x8BD5; HTTP API&#xFF08;&#x5047;&#x8BBE;&#x4F7F;&#x7528;&#x4E86; JSON &#x6216;&#x5176;&#x4ED6;&#x4E00;&#x4E9B;&#x6587;&#x672C;&#x683C;&#x5F0F;&#xFF09;&#x3002;</li>
<li>&#x5B83;&#x76F4;&#x63A5;&#x652F;&#x6301;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x5F0F;&#x901A;&#x4FE1;&#x3002;</li>
<li>HTTP &#x5C5E;&#x4E8E;&#x9632;&#x706B;&#x5899;&#x53CB;&#x597D;&#x3002;</li>
<li>&#x5B83;&#x4E0D;&#x9700;&#x8981;&#x4E2D;&#x95F4;&#x4EE3;&#x7406;&#xFF0C;&#x7B80;&#x5316;&#x4E86;&#x7CFB;&#x7EDF;&#x67B6;&#x6784;&#x3002;</li>
</ul>
<p>&#x4F7F;&#x7528; HTTP &#x4E5F;&#x5B58;&#x5728;&#x4E00;&#x4E9B;&#x7F3A;&#x70B9;&#xFF1A;</p>
<ul>
<li>HTTP &#x4EC5;&#x76F4;&#x63A5;&#x652F;&#x6301;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x7684;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#x3002;&#x4F60;&#x53EF;&#x4EE5;&#x4F7F;&#x7528; HTTP &#x8FDB;&#x884C;&#x901A;&#x77E5;&#xFF0C;&#x4F46;&#x670D;&#x52A1;&#x5668;&#x5FC5;&#x987B;&#x59CB;&#x7EC8;&#x53D1;&#x9001; HTTP &#x54CD;&#x5E94;&#x3002;</li>
<li>&#x56E0;&#x4E3A;&#x5BA2;&#x6237;&#x7AEF;&#x548C;&#x670D;&#x52A1;&#x76F4;&#x63A5;&#x901A;&#x4FE1;&#xFF08;&#x6CA1;&#x6709;&#x4E00;&#x4E2A;&#x4E2D;&#x95F4;&#x8005;&#x6765;&#x7F13;&#x51B2;&#x6D88;&#x606F;&#xFF09;&#xFF0C;&#x6240;&#x4EE5;&#x5B83;&#x4EEC;&#x5FC5;&#x987B;&#x5728;&#x4EA4;&#x6362;&#x671F;&#x95F4;&#x90FD;&#x8FD0;&#x884C;&#x7740;&#x3002;</li>
<li>&#x5BA2;&#x6237;&#x7AEF;&#x5FC5;&#x987B;&#x77E5;&#x9053;&#x6BCF;&#x4E2A;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x7684;&#x4F4D;&#x7F6E;&#xFF08;&#x5373; URL&#xFF09;&#x3002;&#x5982;<a href="2-using-an-api-gateway.html">&#x7B2C;&#x4E8C;&#x7AE0;</a>&#x5173;&#x4E8E; API &#x7F51;&#x5173;&#x6240;&#x8FF0;&#xFF0C;&#x8FD9;&#x662F;&#x73B0;&#x4EE3;&#x5E94;&#x7528;&#x9762;&#x4E34;&#x7684;&#x4E00;&#x4E2A;&#x590D;&#x6742;&#x95EE;&#x9898;&#x3002;&#x5BA2;&#x6237;&#x7AEF;&#x5FC5;&#x987B;&#x4F7F;&#x7528;&#x670D;&#x52A1;&#x53D1;&#x73B0;&#x673A;&#x5236;&#x6765;&#x5B9A;&#x4F4D;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x3002;</li>
</ul>
<p>&#x5F00;&#x53D1;&#x4EBA;&#x5458;&#x793E;&#x533A;&#x6700;&#x8FD1;&#x91CD;&#x65B0;&#x53D1;&#x73B0;&#x4E86; RESTful API &#x63A5;&#x53E3;&#x5B9A;&#x4E49;&#x8BED;&#x8A00;&#x7684;&#x4EF7;&#x503C;&#x3002;&#x6709;&#x51E0;&#x4E2A;&#x53EF;&#x4EE5;&#x9009;&#x62E9;&#xFF0C;&#x5305;&#x62EC; <a href="https://raml.org/" target="_blank">RAML</a> &#x548C; <a href="http://swagger.io/" target="_blank">Swagger</a>&#x3002;&#x4E00;&#x4E9B; IDL&#xFF08;&#x5982; Swagger&#xFF09;&#x5141;&#x8BB8;&#x4F60;&#x5B9A;&#x4E49;&#x8BF7;&#x6C42;&#x548C;&#x54CD;&#x5E94;&#x6D88;&#x606F;&#x7684;&#x683C;&#x5F0F;&#x3002;&#x5176;&#x4ED6;&#x5982; RAML&#xFF0C;&#x9700;&#x8981;&#x4F60;&#x4F7F;&#x7528;&#x4E00;&#x4E2A;&#x5355;&#x72EC;&#x7684;&#x89C4;&#x8303;&#xFF0C;&#x5982; <a href="http://json-schema.org/" target="_blank">JSON &#x6A21;&#x5F0F;</a>&#x3002;&#x9664;&#x4E86;&#x7528;&#x4E8E;&#x63CF;&#x8FF0; API &#x4E4B;&#x5916;&#xFF0C;IDL &#x901A;&#x5E38;&#x8FD8;&#x5177;&#x6709;&#x53EF;&#x4ECE;&#x63A5;&#x53E3;&#x5B9A;&#x4E49;&#x751F;&#x6210;&#x5BA2;&#x6237;&#x7AEF; stub &#x548C;&#x670D;&#x52A1;&#x5668; skeleton &#x7684;&#x5DE5;&#x5177;&#x3002;</p>
<p><a id="thrift"></a></p>
<h3 id="382&#x3001;thrift">3.8.2&#x3001;Thrift</h3>
<p><a href="https://thrift.apache.org/" target="_blank">Apache Thrift</a> &#x662F; REST &#x7684;&#x4E00;&#x4E2A;&#x6709;&#x8DA3;&#x7684;&#x66FF;&#x4EE3;&#x65B9;&#x6848;&#x3002;&#x5B83;&#x662F;&#x4E00;&#x4E2A;&#x7528;&#x4E8E;&#x7F16;&#x5199;&#x8DE8;&#x8BED;&#x8A00; <a href="https://en.wikipedia.org/wiki/Remote_procedure_call" target="_blank">RPC</a> &#x5BA2;&#x6237;&#x7AEF;&#x548C;&#x670D;&#x52A1;&#x5668;&#x7684;&#x6846;&#x67B6;&#x3002;Thrift &#x63D0;&#x4F9B;&#x4E86;&#x4E00;&#x4E2A; C &#x98CE;&#x683C;&#x7684; IDL &#x6765;&#x5B9A;&#x4E49; API&#x3002;&#x4F60;&#x53EF;&#x4EE5;&#x4F7F;&#x7528; Thrift &#x7F16;&#x8BD1;&#x5668;&#x751F;&#x6210;&#x5BA2;&#x6237;&#x7AEF; stub &#x548C;&#x670D;&#x52A1;&#x5668;&#x7AEF; skeleton&#x3002;&#x7F16;&#x8BD1;&#x5668;&#x53EF;&#x4EE5;&#x751F;&#x6210;&#x5404;&#x79CD;&#x8BED;&#x8A00;&#x7684;&#x4EE3;&#x7801;&#xFF0C;&#x5305;&#x62EC; C++&#x3001;Java&#x3001;Python&#x3001;PHP&#x3001;Ruby&#x3001;Erlang &#x548C; Node.js&#x3002;</p>
<p>Thrift &#x63A5;&#x53E3;&#x7531;&#x4E00;&#x4E2A;&#x6216;&#x591A;&#x4E2A;&#x670D;&#x52A1;&#x7EC4;&#x6210;&#x3002;&#x670D;&#x52A1;&#x5B9A;&#x4E49;&#x7C7B;&#x4F3C;&#x4E8E;&#x4E00;&#x4E2A; Java &#x63A5;&#x53E3;&#x3002;&#x5B83;&#x662F;&#x5F3A;&#x7C7B;&#x578B;&#x65B9;&#x6CD5;&#x7684;&#x96C6;&#x5408;&#x3002;</p>
<p>Thrift &#x65B9;&#x6CD5;&#x53EF;&#x4EE5;&#x8FD4;&#x56DE;&#x4E00;&#x4E2A;&#xFF08;&#x53EF;&#x80FD;&#x4E3A; void&#xFF09;&#x503C;&#xFF0C;&#x6216;&#x8005;&#x5982;&#x679C;&#x5B83;&#x4EEC;&#x88AB;&#x5B9A;&#x4E49;&#x4E3A;&#x5355;&#x5411;&#xFF0C;&#x5219;&#x4E0D;&#x4F1A;&#x8FD4;&#x56DE;&#x503C;&#x3002;&#x8FD4;&#x56DE;&#x503C;&#x65B9;&#x6CD5;&#x5B9E;&#x73B0;&#x4E86;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x7684;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#xFF0C;&#x5BA2;&#x6237;&#x7AEF;&#x7B49;&#x5F85;&#x54CD;&#x5E94;&#xFF0C;&#x5E76;&#x53EF;&#x80FD;&#x4F1A;&#x629B;&#x51FA;&#x5F02;&#x5E38;&#x3002;&#x5355;&#x5411;&#x65B9;&#x5F0F;&#x5BF9;&#x5E94;&#x901A;&#x77E5;&#x4EA4;&#x4E92;&#x65B9;&#x5F0F;&#xFF0C;&#x670D;&#x52A1;&#x5668;&#x4E0D;&#x53D1;&#x9001;&#x54CD;&#x5E94;&#x3002;</p>
<p>Thrift &#x652F;&#x6301;&#x591A;&#x79CD;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#xFF1A;JSON&#xFF0C;&#x4E8C;&#x8FDB;&#x5236;&#x548C;&#x538B;&#x7F29;&#x4E8C;&#x8FDB;&#x5236;&#x3002;&#x4E8C;&#x8FDB;&#x5236;&#x6BD4; JSON &#x66F4;&#x52A0;&#x9AD8;&#x6548;&#xFF0C;&#x56E0;&#x4E3A;&#x5176;&#x89E3;&#x7801;&#x901F;&#x5EA6;&#x66F4;&#x5FEB;&#x3002;&#x800C;&#x4E14;&#xFF0C;&#x987E;&#x540D;&#x601D;&#x4E49;&#xFF0C;&#x538B;&#x7F29;&#x4E8C;&#x8FDB;&#x5236;&#x662F;&#x4E00;&#x79CD;&#x8282;&#x7701;&#x7A7A;&#x95F4;&#x7684;&#x683C;&#x5F0F;&#x3002;&#x5F53;&#x7136;&#xFF0C;JSON &#x662F;&#x53EF;&#x8BFB;&#x548C;&#x6D4F;&#x89C8;&#x5668;&#x53CB;&#x597D;&#x7684;&#x3002;Thrift &#x8FD8;&#x4E3A;&#x4F60;&#x63D0;&#x4F9B;&#x4E86;&#x5305;&#x62EC;&#x539F;&#x59CB; TCP &#x548C; HTTP &#x5728;&#x5185;&#x7684;&#x4F20;&#x8F93;&#x534F;&#x8BAE;&#x9009;&#x62E9;&#x3002;&#x539F;&#x59CB; TCP &#x53EF;&#x80FD;&#x6BD4; HTTP &#x66F4;&#x52A0;&#x9AD8;&#x6548;&#x3002;&#x7136;&#x800C;&#xFF0C;HTTP &#x662F;&#x9632;&#x706B;&#x5899;&#x53CB;&#x597D;&#x3001;&#x6D4F;&#x89C8;&#x5668;&#x53CB;&#x597D;&#x5E76;&#x4E14;&#x53EF;&#x8BFB;&#x7684;&#x3002;</p>
<p><a id="message-formats"></a></p>
<h2 id="39&#x3001;&#x6D88;&#x606F;&#x683C;&#x5F0F;">3.9&#x3001;&#x6D88;&#x606F;&#x683C;&#x5F0F;</h2>
<p>&#x6211;&#x4EEC;&#x5DF2;&#x7ECF;&#x4E86;&#x89E3;&#x4E86; HTTP &#x548C; Thrift&#xFF0C;&#x73B0;&#x5728;&#x8BA9;&#x6211;&#x4EEC;&#x6765;&#x770B;&#x770B;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#x7684;&#x95EE;&#x9898;&#x3002;&#x5982;&#x679C;&#x4F60;&#x4F7F;&#x7528;&#x7684;&#x662F;&#x6D88;&#x606F;&#x7CFB;&#x7EDF;&#x6216; REST&#xFF0C;&#x5219;&#x53EF;&#x4EE5;&#x9009;&#x62E9;&#x81EA;&#x5DF1;&#x7684;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#x3002;&#x5176;&#x4ED6; IPC &#x673A;&#x5236;&#x5982; Thrift &#x53EF;&#x80FD;&#x53EA;&#x652F;&#x6301;&#x5C11;&#x91CF;&#x7684;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#xFF0C;&#x751A;&#x81F3;&#x53EA;&#x652F;&#x6301;&#x4E00;&#x79CD;&#x3002;&#x5728;&#x4EFB;&#x4E00;&#x79CD;&#x60C5;&#x51B5;&#x4E0B;&#xFF0C;&#x4F7F;&#x7528;&#x8DE8;&#x8BED;&#x8A00;&#x7684;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#x90FD;&#x5F88;&#x91CD;&#x8981;&#x3002;&#x5373;&#x4F7F;&#x4F60;&#x73B0;&#x5728;&#x662F;&#x4EE5;&#x5355;&#x4E00;&#x8BED;&#x8A00;&#x7F16;&#x5199;&#x5FAE;&#x670D;&#x52A1;&#xFF0C;&#x4F60;&#x5C06;&#x6765;&#x4E5F;&#x53EF;&#x80FD;&#x4F1A;&#x4F7F;&#x7528;&#x5230;&#x5176;&#x4ED6;&#x8BED;&#x8A00;&#x3002;</p>
<p>&#x6709;&#x4E24;&#x79CD;&#x4E3B;&#x8981;&#x7684;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#xFF1A;&#x6587;&#x672C;&#x548C;&#x4E8C;&#x8FDB;&#x5236;&#x3002;&#x57FA;&#x4E8E;&#x6587;&#x672C;&#x683C;&#x5F0F;&#x7684;&#x4F8B;&#x5B50;&#x6709; JSON &#x548C; XML&#x3002;&#x8FD9;&#x4E9B;&#x683C;&#x5F0F;&#x7684;&#x4F18;&#x70B9;&#x5728;&#x4E8E;&#xFF0C;&#x5B83;&#x4EEC;&#x4E0D;&#x4EC5;&#x662F;&#x4EBA;&#x7C7B;&#x53EF;&#x8BFB;&#x7684;&#xFF0C;&#x800C;&#x4E14;&#x662F;&#x81EA;&#x63CF;&#x8FF0;&#x7684;&#x3002;&#x5728; JSON &#x4E2D;&#xFF0C;&#x5BF9;&#x8C61;&#x7684;&#x5C5E;&#x6027;&#x7531;&#x4E00;&#x7EC4;&#x952E;&#x503C;&#x5BF9;&#x8868;&#x793A;&#x3002;&#x7C7B;&#x4F3C;&#x5730;&#xFF0C;&#x5728; XML &#x4E2D;&#xFF0C;&#x5C5E;&#x6027;&#x7531;&#x547D;&#x540D;&#x5143;&#x7D20;&#x548C;&#x503C;&#x8868;&#x793A;&#x3002;&#x8FD9;&#x4F7F;&#x5F97;&#x6D88;&#x606F;&#x6D88;&#x8D39;&#x8005;&#x80FD;&#x591F;&#x6311;&#x9009;&#x5176;&#x611F;&#x5174;&#x8DA3;&#x7684;&#x503C;&#x5E76;&#x5FFD;&#x7565;&#x5176;&#x4F59;&#x7684;&#x503C;&#x3002;&#x56E0;&#x6B64;&#xFF0C;&#x7A0D;&#x5FAE;&#x4FEE;&#x6539;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#x5C31;&#x53EF;&#x4EE5;&#x8F7B;&#x677E;&#x5730;&#x5411;&#x540E;&#x517C;&#x5BB9;&#x3002;</p>
<p>XML &#x6587;&#x6863;&#x7684;&#x7ED3;&#x6784;&#x7531; <a href="https://www.w3.org/XML/Schema" target="_blank">XML &#x6A21;&#x5F0F;</a>&#xFF08;schema&#xFF09;&#x5B9A;&#x4E49;&#x3002;&#x968F;&#x7740;&#x65F6;&#x95F4;&#x7684;&#x63A8;&#x79FB;&#xFF0C;&#x5F00;&#x53D1;&#x4EBA;&#x5458;&#x793E;&#x533A;&#x5DF2;&#x7ECF;&#x610F;&#x8BC6;&#x5230; JSON &#x4E5F;&#x9700;&#x8981;&#x4E00;&#x4E2A;&#x7C7B;&#x4F3C;&#x7684;&#x673A;&#x5236;&#x3002;&#x4E00;&#x4E2A;&#x9009;&#x62E9;&#x662F;&#x4F7F;&#x7528; <a href="http://json-schema.org/" target="_blank">JSON Schema</a>&#xFF0C;&#x53E6;&#x4E00;&#x4E2A;&#x662F;&#x72EC;&#x7ACB;&#x6216;&#x4F5C;&#x4E3A; IDL &#x7684;&#x4E00;&#x90E8;&#x5206;&#xFF0C;&#x5982; Swagger&#x3002;</p>
<p>&#x4F7F;&#x7528;&#x57FA;&#x4E8E;&#x6587;&#x672C;&#x7684;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#x7684;&#x7F3A;&#x70B9;&#x662F;&#x6D88;&#x606F;&#x5F80;&#x5F80;&#x662F;&#x5197;&#x957F;&#x7684;&#xFF0C;&#x7279;&#x522B;&#x662F; XML&#x3002;&#x56E0;&#x4E3A;&#x6D88;&#x606F;&#x662F;&#x81EA;&#x63CF;&#x8FF0;&#x7684;&#xFF0C;&#x6BCF;&#x4E2A;&#x6D88;&#x606F;&#x9664;&#x4E86;&#x5B83;&#x4EEC;&#x7684;&#x503C;&#x4E4B;&#x5916;&#x8FD8;&#x5305;&#x542B;&#x5C5E;&#x6027;&#x7684;&#x540D;&#x79F0;&#x3002;&#x53E6;&#x4E00;&#x4E2A;&#x7F3A;&#x70B9;&#x662F;&#x89E3;&#x6790;&#x6587;&#x672C;&#x7684;&#x5F00;&#x9500;&#x3002;&#x56E0;&#x6B64;&#xFF0C;&#x4F60;&#x53EF;&#x80FD;&#x9700;&#x8981;&#x8003;&#x8651;&#x4F7F;&#x7528;&#x4E8C;&#x8FDB;&#x5236;&#x683C;&#x5F0F;&#x3002;</p>
<p>&#x6709;&#x51E0;&#x79CD;&#x4E8C;&#x8FDB;&#x5236;&#x683C;&#x5F0F;&#x53EF;&#x4F9B;&#x9009;&#x62E9;&#x3002;&#x5982;&#x679C;&#x4F60;&#x4F7F;&#x7528;&#x7684;&#x662F; Thrift RPC&#xFF0C;&#x4F60;&#x53EF;&#x4EE5;&#x4F7F;&#x7528; Thrift &#x7684;&#x4E8C;&#x8FDB;&#x5236;&#x683C;&#x5F0F;&#x3002;&#x5982;&#x679C;&#x4F60;&#x53EF;&#x4EE5;&#x9009;&#x62E9;&#x6D88;&#x606F;&#x683C;&#x5F0F;&#xFF0C;&#x6BD4;&#x8F83;&#x6D41;&#x884C;&#x7684;&#x6709; <a href="https://developers.google.com/protocol-buffers/docs/overview" target="_blank">Protocol Buffers</a> &#x548C; <a href="https://avro.apache.org/" target="_blank">Apache Avro</a>&#x3002;&#x8FD9;&#x4E24;&#x79CD;&#x683C;&#x5F0F;&#x90FD;&#x63D0;&#x4F9B;&#x4E86;&#x4E00;&#x79CD;&#x7C7B;&#x578B;&#x5316;&#x7684; IDL &#x7528;&#x4E8E;&#x5B9A;&#x4E49;&#x6D88;&#x606F;&#x7ED3;&#x6784;&#x3002;&#x7136;&#x800C;&#xFF0C;&#x4E00;&#x4E2A;&#x533A;&#x522B;&#x662F; Protocol Buffers &#x4F7F;&#x7528;&#x6807;&#x8BB0;&#x5B57;&#x6BB5;&#xFF0C;&#x800C; Avro &#x6D88;&#x8D39;&#x8005;&#x9700;&#x8981;&#x77E5;&#x9053;&#x6A21;&#x5F0F;&#x624D;&#x80FD;&#x89E3;&#x91CA;&#x6D88;&#x606F;&#x3002;&#x56E0;&#x6B64;&#xFF0C;Protocol Buffers &#x7684; API &#x6F14;&#x5316;&#x6BD4; Avro &#x66F4;&#x5BB9;&#x6613;&#x4F7F;&#x7528;&#x3002;&#x8FD9;&#x91CC;&#x6709;&#x7BC7;<a href="http://martin.kleppmann.com/2012/12/05/schema-evolution-in-avro-protocol-buffers-thrift.html" target="_blank">&#x535A;&#x6587;</a>&#x5BF9; Thrift&#x3001;Protocol Buffers &#x548C; Avro &#x4F5C;&#x4E86;&#x6BD4;&#x8F83;&#x5168;&#x9762;&#x7684;&#x5BF9;&#x6BD4;&#x3002;</p>
<p><a id="summary"></a></p>
<h2 id="310&#x3001;&#x603B;&#x7ED3;">3.10&#x3001;&#x603B;&#x7ED3;</h2>
<p>&#x5FAE;&#x670D;&#x52A1;&#x5FC5;&#x987B;&#x4F7F;&#x7528;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#x673A;&#x5236;&#x8FDB;&#x884C;&#x901A;&#x4FE1;&#x3002;&#x5728;&#x8BBE;&#x8BA1;&#x670D;&#x52A1;&#x5982;&#x4F55;&#x8FDB;&#x884C;&#x901A;&#x4FE1;&#x65F6;&#xFF0C;&#x4F60;&#x9700;&#x8981;&#x8003;&#x8651;&#x5404;&#x79CD;&#x95EE;&#x9898;&#xFF1A;&#x670D;&#x52A1;&#x5982;&#x4F55;&#x4EA4;&#x4E92;&#x3001;&#x5982;&#x4F55;&#x4E3A;&#x6BCF;&#x4E2A;&#x670D;&#x52A1;&#x6307;&#x5B9A; API&#x3001;&#x5982;&#x4F55;&#x6F14;&#x53D8; API &#x4EE5;&#x53CA;&#x5982;&#x4F55;&#x5904;&#x7406;&#x5C40;&#x90E8;&#x6545;&#x969C;&#x3002;&#x5FAE;&#x670D;&#x52A1;&#x53EF;&#x4EE5;&#x4F7F;&#x7528;&#x4E24;&#x79CD; IPC &#x673A;&#x5236;&#xFF1A;&#x5F02;&#x6B65;&#x6D88;&#x606F;&#x4F20;&#x9012;&#x548C;&#x540C;&#x6B65;&#x8BF7;&#x6C42;/&#x54CD;&#x5E94;&#x3002;&#x4E3A;&#x4E86;&#x8FDB;&#x884C;&#x901A;&#x4FE1;&#xFF0C;&#x4E00;&#x4E2A;&#x670D;&#x52A1;&#x5FC5;&#x987B;&#x80FD;&#x591F;&#x627E;&#x5230;&#x53E6;&#x4E00;&#x4E2A;&#x670D;&#x52A1;&#x3002;&#x5728;&#x7B2C;&#x56DB;&#x7AE0;&#x4E2D;&#xFF0C;&#x6211;&#x4EEC;&#x5C06;&#x4ECB;&#x7ECD;&#x5FAE;&#x670D;&#x52A1;&#x67B6;&#x6784;&#x4E2D;&#x670D;&#x52A1;&#x53D1;&#x73B0;&#x95EE;&#x9898;&#x3002;</p>
<p><a id="microservices-in-action"></a></p>
<h2 id="&#x5FAE;&#x670D;&#x52A1;&#x5B9E;&#x6218;&#xFF1A;nginx-&#x4E0E;&#x5E94;&#x7528;&#x67B6;&#x6784;">&#x5FAE;&#x670D;&#x52A1;&#x5B9E;&#x6218;&#xFF1A;NGINX &#x4E0E;&#x5E94;&#x7528;&#x67B6;&#x6784;</h2>
<p>by Floyd Smith</p>
<p>NGINX &#x4F7F;&#x4F60;&#x80FD;&#x591F;&#x5B9E;&#x73B0;&#x5404;&#x79CD;&#x4F38;&#x7F29;&#x548C;&#x955C;&#x50CF;&#x64CD;&#x4F5C;&#xFF0C;&#x4F7F;&#x4F60;&#x7684;&#x5E94;&#x7528;&#x66F4;&#x52A0;&#x7075;&#x654F;&#x548C;&#x9AD8;&#x5EA6;&#x53EF;&#x7528;&#x3002;&#x4F60;&#x4E3A;&#x4F38;&#x7F29;&#x548C;&#x955C;&#x50CF;&#x6240;&#x4F5C;&#x7684;&#x9009;&#x62E9;&#x4F1A;&#x5F71;&#x54CD;&#x5230;&#x4F60;&#x5982;&#x4F55;&#x8FDB;&#x884C;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#xFF0C;&#x8FD9;&#x662F;&#x672C;&#x7AE0;&#x7684;&#x4E3B;&#x9898;&#x3002;</p>
<p>&#x6211;&#x4EEC;&#x5728; NGINX &#x65B9;&#x9762;&#x5EFA;&#x8BAE;&#x4F60;&#x5728;&#x5B9E;&#x73B0;&#x57FA;&#x4E8E;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x5E94;&#x7528;&#x65F6;&#x8003;&#x8651;&#x4F7F;&#x7528;&#x56DB;&#x5C42;&#x67B6;&#x6784;&#x3002;Forrester &#x5728;&#x8FD9;&#x65B9;&#x9762;&#x6709;&#x8BE6;&#x7EC6;&#x7684;&#x62A5;&#x544A;&#xFF0C;&#x4F60;&#x53EF;&#x4EE5;&#x4ECE; NGINX &#x4E0A;&#x514D;&#x8D39;&#x4E0B;&#x8F7D;&#x3002;&#x8FD9;&#x4E9B;&#x5C42;&#x4EE3;&#x8868;&#x5BA2;&#x6237;&#x7AEF;&#xFF08;&#x5305;&#x62EC;&#x53F0;&#x5F0F;&#x673A;&#x6216;&#x7B14;&#x8BB0;&#x672C;&#x7535;&#x8111;&#x3001;&#x79FB;&#x52A8;&#x3001;&#x53EF;&#x7A7F;&#x6234;&#x6216; IoT &#x5BA2;&#x6237;&#x7AEF;&#xFF09;&#x3001;&#x4EA4;&#x4ED8;&#x3001;&#x805A;&#x5408;&#xFF08;&#x5305;&#x62EC;&#x6570;&#x636E;&#x5B58;&#x50A8;&#xFF09;&#x548C;&#x670D;&#x52A1;&#xFF0C;&#x5176;&#x4E2D;&#x5305;&#x62EC;&#x5E94;&#x7528;&#x529F;&#x80FD;&#x548C;&#x7279;&#x5B9A;&#x670D;&#x52A1;&#xFF0C;&#x800C;&#x4E0D;&#x662F;&#x5171;&#x4EAB;&#x6570;&#x636E;&#x5B58;&#x50A8;&#x3002;</p>
<p>&#x56DB;&#x5C42;&#x67B6;&#x6784;&#x6BD4;&#x4EE5;&#x524D;&#x7684;&#x4E09;&#x5C42;&#x67B6;&#x6784;&#x66F4;&#x52A0;&#x7075;&#x6D3B;&#xFF0C;&#x5177;&#x6709;&#x53EF;&#x6269;&#x5C55;&#x3001;&#x54CD;&#x5E94;&#x7075;&#x654F;&#x3001;&#x79FB;&#x52A8;&#x53CB;&#x597D;&#xFF0C;&#x5E76;&#x4E14;&#x5185;&#x5728;&#x652F;&#x6301;&#x57FA;&#x4E8E;&#x5FAE;&#x670D;&#x52A1;&#x7684;&#x5E94;&#x7528;&#x5F00;&#x53D1;&#x548C;&#x4EA4;&#x4ED8;&#x7B49;&#x4F18;&#x70B9;&#x3002;&#x50CF; Netflix &#x548C; Uber &#x8FD9;&#x6837;&#x7684;&#x884C;&#x4E1A;&#x5F15;&#x9886;&#x8005;&#x901A;&#x8FC7;&#x4F7F;&#x7528;&#x8FD9;&#x79CD;&#x67B6;&#x6784;&#x6765;&#x5B9E;&#x73B0;&#x7528;&#x6237;&#x6240;&#x9700;&#x7684;&#x6027;&#x80FD;&#x6C34;&#x5E73;&#x3002;</p>
<p>NGINX &#x672C;&#x8D28;&#x4E0A;&#x975E;&#x5E38;&#x9002;&#x5408;&#x56DB;&#x5C42;&#x67B6;&#x6784;&#xFF0C;&#x4ECE;&#x5BA2;&#x6237;&#x7AEF;&#x5C42;&#x7684;&#x5A92;&#x4F53;&#x6D41;&#xFF0C;&#x5230;&#x4EA4;&#x4ED8;&#x5C42;&#x7684;&#x8D1F;&#x8F7D;&#x5747;&#x8861;&#x4E0E;&#x7F13;&#x5B58;&#x3001;&#x805A;&#x5408;&#x5C42;&#x7684;&#x9AD8;&#x6027;&#x80FD;&#x548C;&#x5B89;&#x5168;&#x7684;&#x57FA;&#x4E8E; API &#x7684;&#x901A;&#x4FE1;&#x7684;&#x5DE5;&#x5177;&#xFF0C;&#x4EE5;&#x53CA;&#x670D;&#x52A1;&#x5C42;&#x4E2D;&#x652F;&#x6301;&#x7075;&#x6D3B;&#x7BA1;&#x7406;&#x7684;&#x77ED;&#x6682;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x3002;</p>
<p>&#x540C;&#x6837;&#x7684;&#x7075;&#x6D3B;&#x6027;&#x4F7F;&#x5F97; NGINX &#x53EF;&#x4EE5;&#x5B9E;&#x73B0;&#x5F3A;&#x5927;&#x7684;&#x4F38;&#x7F29;&#x548C;&#x955C;&#x50CF;&#x6A21;&#x5F0F;&#xFF0C;&#x4EE5;&#x5904;&#x7406;&#x6D41;&#x91CF;&#x53D8;&#x5316;&#xFF0C;&#x9632;&#x6B62;&#x5B89;&#x5168;&#x653B;&#x51FB;&#xFF0C;&#x6B64;&#x5916;&#x8FD8;&#x63D0;&#x4F9B;&#x53EF;&#x7528;&#x7684;&#x6545;&#x969C;&#x914D;&#x7F6E;&#x5207;&#x6362;&#xFF0C;&#x4ECE;&#x800C;&#x5B9E;&#x73B0;&#x9AD8;&#x53EF;&#x7528;&#x3002;</p>
<p>&#x5728;&#x66F4;&#x4E3A;&#x590D;&#x6742;&#x7684;&#x67B6;&#x6784;&#x4E2D;&#xFF0C;&#x5305;&#x62EC;&#x670D;&#x52A1;&#x5B9E;&#x4F8B;&#x5B9E;&#x4F8B;&#x5316;&#x548C;&#x9700;&#x6C42;&#x4E0D;&#x65AD;&#x7684;&#x670D;&#x52A1;&#x53D1;&#x73B0;&#xFF0C;&#x89E3;&#x8026;&#x7684;&#x8FDB;&#x7A0B;&#x95F4;&#x901A;&#x4FE1;&#x5F80;&#x5F80;&#x66F4;&#x53D7;&#x9752;&#x7750;&#x3002;&#x5F02;&#x6B65;&#x548C;&#x4E00;&#x5BF9;&#x591A;&#x901A;&#x4FE1;&#x65B9;&#x5F0F;&#x53EF;&#x80FD;&#x6BD4;&#x9AD8;&#x8026;&#x5408;&#x7684;&#x901A;&#x4FE1;&#x65B9;&#x5F0F;&#x66F4;&#x52A0;&#x7075;&#x6D3B;&#xFF0C;&#x5B83;&#x4EEC;&#x6700;&#x7EC8;&#x63D0;&#x4F9B;&#x66F4;&#x9AD8;&#x7684;&#x6027;&#x80FD;&#x548C;&#x53EF;&#x9760;&#x6027;&#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 20:32:39
</span></footer>
</section>
</div>
</div>
</div>
<a href="2-using-an-api-gateway.html#microservices-in-action" class="navigation navigation-prev " aria-label="Previous page: 微服务实战：NGINX Plus 作为 API 网关">
<i class="fa fa-angle-left"></i>
</a>
<a href="3-inter-process-communication.html#introduction" class="navigation navigation-next " aria-label="Next page: 3.1、简介">
<i class="fa fa-angle-right"></i>
</a>
</div>
<script>
var gitbook = gitbook || [];
gitbook.push(function() {
gitbook.page.hasChanged({"page":{"title":"3、进程间通信","level":"1.5","depth":1,"next":{"title":"3.1、简介","level":"1.5.1","depth":2,"anchor":"#introduction","path":"3-inter-process-communication.md","ref":"3-inter-process-communication.md#introduction","articles":[]},"previous":{"title":"微服务实战：NGINX Plus 作为 API 网关","level":"1.4.7","depth":2,"anchor":"#microservices-in-action","path":"2-using-an-api-gateway.md","ref":"2-using-an-api-gateway.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":"3-inter-process-communication.md","mtime":"2019-06-26T12:32:39.422Z","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