|
1 | 1 | # Summary |
2 | 2 |
|
3 | | -* [0、前言](0-foreword.md) |
| 3 | +* 0、前言 |
4 | 4 |
|
5 | | -* [1、微服务简介](1-introduction-to-microservices.md) |
6 | | - - [1.1、构建单体应用](1-introduction-to-microservices.md#building-monolithic-applications) |
7 | | - - [1.2、走向单体地狱](1-introduction-to-microservices.md#marching-toward-monolithic-hell) |
8 | | - - [1.3、微服务-解决复杂问题](1-introduction-to-microservices.md#tackling-the-complexity) |
9 | | - - [1.4、微服务的优点](1-introduction-to-microservices.md#the-benefits-of-microservices) |
10 | | - - [1.5、微服务的缺点](1-introduction-to-microservices.md#the-drawbacks-of-microservices) |
11 | | - - [1.6、总结](1-introduction-to-microservices.md#summary) |
12 | | - - [微服务实战:NGINX Plus 作为反向代理服务器](1-introduction-to-microservices.md#microservices-in-action) |
| 5 | +* 1、微服务简介 |
| 6 | + - 1.1、构建单体应用 |
| 7 | + - 1.2、走向单体地狱 |
| 8 | + - 1.3、微服务-解决复杂问题 |
| 9 | + - 1.4、微服务的优点 |
| 10 | + - 1.5、微服务的缺点 |
| 11 | + - 1.6、总结 |
| 12 | + - 微服务实战:NGINX Plus 作为反向代理服务器 |
13 | 13 |
|
14 | | -* [2、使用 API 网关](2-using-an-api-gateway.md) |
15 | | - - [2.1、简介](2-using-an-api-gateway.md#introduction) |
16 | | - - [2.2、客户端与微服务直接通信](2-using-an-api-gateway.md#direct-client-to-microservice-communication) |
17 | | - - [2.3、使用 API 网关](2-using-an-api-gateway.md#using-an-api-gateway) |
18 | | - - [2.4、API 网关的优点与缺点](2-using-an-api-gateway.md#benefits-and-drawbacks-of-an-api-gateway) |
19 | | - - [2.5、实施 API 网关](2-using-an-api-gateway.md#implementing-an-api-gateway) |
20 | | - - [2.5.1、性能与扩展](2-using-an-api-gateway.md#performance-and-scalability) |
21 | | - - [2.5.2、使用响应式编程模型](2-using-an-api-gateway.md#using-a-reactive-programming-model) |
22 | | - - [2.5.3、服务调用](2-using-an-api-gateway.md#service-invocation) |
23 | | - - [2.5.4、服务发现](2-using-an-api-gateway.md#service-discovery) |
24 | | - - [2.5.5、处理局部故障](2-using-an-api-gateway.md#handling-partial-failures) |
25 | | - - [2.6、总结](2-using-an-api-gateway.md#summary) |
26 | | - - [微服务实战:NGINX Plus 作为 API 网关](2-using-an-api-gateway.md#microservices-in-action) |
| 14 | +* 2、使用 API 网关 |
| 15 | + - 2.1、简介 |
| 16 | + - 2.2、客户端与微服务直接通信 |
| 17 | + - 2.3、使用 API 网关 |
| 18 | + - 2.4、API 网关的优点与缺点 |
| 19 | + - 2.5、实施 API 网关 |
| 20 | + - 2.5.1、性能与扩展] |
| 21 | + - 2.5.2、使用响应式编程模型 |
| 22 | + - 2.5.3、服务调用] |
| 23 | + - 2.5.4、服务发现 |
| 24 | + - 2.5.5、处理局部故障 |
| 25 | + - 2.6、总结 |
| 26 | + - 微服务实战:NGINX Plus 作为 API 网关 |
27 | 27 |
|
28 | | -* [3、进程间通信](3-inter-process-communication.md) |
29 | | - - [3.1、简介](3-inter-process-communication.md#introduction) |
30 | | - - [3.2、交互方式](3-inter-process-communication.md#interaction-styles) |
31 | | - - [3.3、定义 API](3-inter-process-communication.md#defining-apis) |
32 | | - - [3.4、演化 API](3-inter-process-communication.md#evolving-apis) |
33 | | - - [3.5、处理局部故障](3-inter-process-communication.md#handling-partial-failure) |
34 | | - - [3.6、IPC 技术](3-inter-process-communication.md#ipc-technologies) |
35 | | - - [3.7、异步、基于消息的通信](3-inter-process-communication.md#asynchronous-message-based-communication) |
36 | | - - [3.8、同步的请求/响应 IPC](3-inter-process-communication.md#synchronous-request-response-ipc) |
37 | | - - [3.8.1、REST](3-inter-process-communication.md#rest) |
38 | | - - [3.8.2、Thrift](3-inter-process-communication.md#thrift) |
39 | | - - [3.9、消息格式](3-inter-process-communication.md#message-formats) |
40 | | - - [3.10、总结](3-inter-process-communication.md#summary) |
41 | | - - [微服务实战:NGINX 与应用程序架构](3-inter-process-communication.md#microservices-in-action) |
| 28 | +* 3、进程间通信 |
| 29 | + - 3.1、简介 |
| 30 | + - 3.2、交互方式 |
| 31 | + - 3.3、定义 API |
| 32 | + - 3.4、演化 API |
| 33 | + - 3.5、处理局部故障 |
| 34 | + - 3.6、IPC 技术 |
| 35 | + - 3.7、异步、基于消息的通信 |
| 36 | + - 3.8、同步的请求/响应 IPC |
| 37 | + - 3.8.1、REST |
| 38 | + - 3.8.2、Thrift |
| 39 | + - 3.9、消息格式 |
| 40 | + - 3.10、总结 |
| 41 | + - 微服务实战:NGINX 与应用程序架构 |
42 | 42 |
|
43 | 43 | * [4、服务发现](4-service-discovery.md) |
44 | 44 | - [4.1、为何使用服务发现](4-service-discovery.md#why-use-service-discovery) |
|
0 commit comments