Microservices_Designing_Deploying.pdf

【实例截图】

【核心代码】

Foreword iii
Introduction to Microservices . . . . . . . . . . . . . . . . . . . . . . 1
Building Monolithic Applications . . . . . . . . . . . . . . . . . . . . . 1
Marching Toward Monolithic Hell 3
Microservices – Tackling the Complexity 4
The Benefits of Microservices 8
The Drawbacks of Microservices 9
Summary 11
Microservices in Action: NGINX Plus as a Reverse Proxy Server . .11
Using an API Gateway 12
Introduction 12
Direct Client-to-Microservice Communication 15
Using an API Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Benefits and Drawbacks of an API Gateway 17
Implementing an API Gateway 17
Performance and Scalability 17
Using a Reactive Programming Model 18
Service Invocation . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Service Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Handling Partial Failures 19
Summary 20
Microservices in Action: NGINX Plus as an API Gateway . . . . 20
Inter-Process Communication 21
Introduction 21
Interaction Styles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Defining APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Evolving APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Handling Partial Failure 25
IPC Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Asynchronous, Message-Based Communication 26
Synchronous, Request/Response IPC . . . . . . . . . . . . . . . . 29
REST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Thrift . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Message Formats 31
Summary 32
Microservices in Action: NGINX and Application Architecture . . 33
Table of Contents
1
2
3
ii
Service Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Why Use Service Discovery? 34
The Client-Side Discovery Pattern 35
The Server-Side Discovery Pattern . . . . . . . . . . . . . . . . . . 37
The Service Registry 38
Service Registration Options 39
The Self-Registration Pattern . . . . . . . . . . . . . . . . . . . . . . 39
The Third-Party Registration Pattern . . . . . . . . . . . . . . . . . .41
Summary 42
Microservices in Action: NGINX Flexibility 43
Event-Driven Data Management for Microservices 44
Microservices and the Problem of Distributed
Data Management 44
Event-Driven Architecture 47
Achieving Atomicity 50
Publishing Events Using Local Transactions . . . . . . . . . . . . 50
Mining a Database Transaction Log 51
Using Event Sourcing 52
Summary 54
Microservices in Action: NGINX and Storage Optimization . . . 54
Choosing a Microservices Deployment Strategy . . . . . . . . 55
Motivations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Multiple Service Instances per Host Pattern . . . . . . . . . . . . 56
Service Instance per Host Pattern 58
Service Instance per Virtual Machine Pattern 58
Service Instance per Container Pattern . . . . . . . . . . . . . . . 60
Serverless Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Summary 63
Microservices in Action: Deploying Microservices
Across Varying Hosts with NGINX 63
Refactoring a Monolith into Microservices 64
Overview of Refactoring to Microservices 65
Strategy #1: Stop Digging 66
Strategy #2: Split Frontend and Backend 67
Strategy #3: Extract Services . . . . . . . . . . . . . . . . . . . . . . 69
Prioritizing Which Modules to Convert into Services 69
How to Extract a Module . . . . . . . . . . . . . . . . . . . . . . . 69
Summary 71
Microservices in Action: Taming a Monolith with NGINX . . . . . 72
Resources for Microservices and NGINX . . . . . . . . . . . . . . 73