云原生基础架构 pdf 下载 txt 阿里云 lit rtf azw3 免费

暂无相关简介，正在全力查找中！

前言 1

第1章 什么是云原生基础架构 9

1.1 云原生的益处 10

1.2 服务器 11

1.3 虚拟化 11

1.4 基础架构即服务 12

1.5 平台即服务 13

1.6 云原生基础架构 14

1.7 什么不是云原生基础架构 15

1.8 云原生应用 17

1.9 云原生应用如何影响基础架构 25

总结 26

第2章 何时采用云原生 27

2.1 应用 28

2.2 人 29

2.3 系统 29

2.4 业务 31

2.5 何时不需要云原生基础架构 32

总结 35

第3章 云原生部署的演进 37

3.1 表述基础架构 38

3.2 部署工具 46

总结 50

第4章 设计基础架构应用 52

4.1 引导问题 53

4.2 API 54

4.3 万物的状态 55

4.4 协调器模式 59

4.5 协调器模式的方法 63

4.6 审计关系 65

总结 67

第5章 开发基础架构应用 69

5.1 设计API 69

5.2 添加特征 70

5.3 弃用特征 71

5.4 改变基础架构 73

总结 76

第6章 云原生基础架构测试 77

6.1 测试的内容是什么 78

6.2 编写可测试代码 79

6.3 自知 82

6.4 测试类型 84

6.5 监控基础架构 95

总结 96

第7章 云原生应用管理 97

7.1 应用设计 98

7.2 实现云原生模式 99

7.3 应用的生命周期 100

7.4 应用对基础架构的要求 104

总结 111

第8章 保护应用程序 113

8.1 策略即代码 113

8.2 审计基础架构 120

8.3 不可变基础架构 122

总结 123

第9章 实现云原生基础架构 125

9.1 关注变革的地方 126

9.2 预测未来 131

总结 132

附录A 网络弹性模式 134

附录B 关于被锁定 140

附录C Box公司案例研究 143

贾斯汀·加里森（Justin Garrion）是著名媒体公司的工程师。他热爱社区和开源，努力解决人们的需求，而不只是修复问题。

克里斯·诺娃（Kris Nova）是微软的高级开发人员，主要负责容器和Linux操作系统。她也是后端基础架构工程师和Kubernetes维护者。

暂无出版社相关信息，正在全力查找中！

暂无相关书籍摘录，正在全力查找中！

在线阅读地址：云原生基础架构在线阅读

在线听书地址：云原生基础架构在线收听

在线购买地址：云原生基础架构在线购买

Applications that are managed and deployed as single entities are often called monoliths. Monoliths have a lot of benefits when applications are initially developed. They are easier to understand and allow you to change major functionality without affecting other services.

As complexity of the application grows, the benefits of monoliths diminish. They become harder to understand, and they lose agility because it is harder for engineers to reason about and make changes to the code.

One of the best ways to fight complexity is to separate clearly defined functionality into smaller services and let each service independently iterate. This increases the application’s agility by allowing portions of it to be changed more easily as needed. Each microservice can be managed by separate teams, wr...

Infrastructure as code defines and automates your infrastructure in machine-parsible language or domain-specific language (DSL). Traditional tools to apply code to infra‐ structure include configuration management tools (e.g., Chef and Puppet). These tools help greatly in automating tasks and providing consistency, but they fall short in providing the necessary abstractions to describe infrastructure beyond a single server.

A cloud native application is engineered to run on a platform and is designed for resiliency, agility, operability, and observability. Resiliency embraces failures instead of trying to prevent them; it takes advantage of the dynamic nature of running on a plat‐ form. Agility allows for fast deployments and quick iterations. Operability adds con‐ trol of application life cycles from inside the application instead of relying on external processes and monitors. Observability provides information to answer questions about application state.

Any resources you spend to engineer uptime that exceeds the SLO are wasted

暂无其它内容！