Architecture Treasure Book

Name: Architecture Treasure Book
ISBN: 9787121360664

中生代技术社区Publishing House of Electronics Industry · ChinaOct 2020

3.7

Word count: 121K words
Chapters: 146
ISBN: 9787121360664

Report an error Find this book

Summary

This book elaborates on four aspects: architecture design concepts, methods, patterns, and practical cases. It is rich in content, a book that can well guide practice, and moreover a summary of the experience of senior experts and architects. The book is divided into four parts: Part I introduces the concepts and methodology of architecture design, as well as the core capabilities of architects; Part II introduces microservice architecture selection, architecture patterns and practice, data consistency assurance, the relationship between microservices and DevOps, and how to design cloud microservice architecture; Part III introduces excellent practices in fields such as mobile e-commerce, consumer credit, payment systems, and financial matching; Part IV introduces methodologies, cases, and key technologies for optimizing system architecture performance. This book is suitable for technical experts about to enter the architecture field, as well as architects, designers, and developers committed to improving software architecture design capabilities. It is hoped that this book can help readers in their practical work and personal growth.

Editor's review

Architecture Treasure Book was jointly written by several senior architects organized by the Zhong Sheng Dai technology community, and is a concentrated presentation of the practical wisdom accumulated by domestic technology communities in recent years. This book is not a textbook that systematically expounds theory in the traditional sense, but more like a 'revelation of architecture practice' from the front lines. It moves beyond the scope of mere technology selection or framework comparison, focusing on more essential dimensions such as architectural thinking, evolution paths, trade-off decisions, and team collaboration. Most cases in the book originate from real scenarios of domestic internet companies, covering multiple key areas from high-concurrency processing, microservice governance to stability assurance and technical team management, and have strong practical reference significance.

For experienced architects, the value of this book lies in providing diverse perspectives and different approaches to solving complex problems, which can trigger reflection on and resonance with their own work. For growing developers or designers new to architecture, it is like a rough but key-pointing map, revealing the core propositions and common pitfalls in the transition from code to systems and then to technology-business collaboration. Its content may not be sufficiently systematic, and some views may be controversial, but it is precisely this community-derived, slightly 'wild' practice sharing that bridges the gap between purely theoretical books and concrete implementation, providing valuable and warm experience references.

Who it's for

A good fit for

Engineers with more than 3 years of back-end or system development experience who wish to transition to an architect role
Technical leaders currently facing practical challenges such as system refactoring, technology stack evolution, or team splitting
Technology enthusiasts with practical interest in distributed systems, high-availability architecture, and microservice governance who want to learn about frontline domestic practices
Technical team managers who wish to understand the technical logic behind architecture decisions and key points of team collaboration

Not a good fit for

Programming beginners or novices who have not yet been exposed to medium-sized or larger system development
Readers expecting a step-by-step theoretical textbook that provides standard answers and fixed routines

Reading tips

It is recommended to read by topic in a non-linear way, prioritizing chapters most relevant to the pain points of one's current work
While reading, focus on the authors' thinking process and trade-offs in solving problems, rather than merely memorizing specific technical solutions
Reflect on one's own team's current architecture in light of the scenarios mentioned in the book, and try to raise questions and look for clues for improvement

About the publisher

Publishing House of Electronics Industry China · Founded in 1982

The Publishing House of Electronics Industry is a comprehensive publisher distinguished by its focus on electronic information and related fields. Judging from the more than 3,000 titles in its catalogue, its publishing covers programming and design, artificial intelligence, computer science, finance and economics, photography, and social sciences, attending both to cutting-edge technology and to general readers. Representative titles include Factor Investing: Methods and Practice, x86 Assembly Language: From Real Mode to Protected Mode, The RISC-V Reader, Artificial Intelligence: Speech Recognition, Understanding and Practice, Phased Array Radar Technology, Radar Target Characteristics, and 100 Go Mistakes and How to Avoid Them, most of which centre on technical methods and engineering practice. Its authors include Shi Chuan, Li Zhong, Wang Xiaobo, David Patterson, Andrew Waterman, and Yu Zihao, among others from China and abroad. Owing to limited public information, no further publishing features are elaborated here.

版权信息
内容简介
序
前言
第1篇架构方法论
1 有关架构的概念认知
1.1 引言
1.2 认识架构
1.3 规划、架构与设计
1.4 解耦与服务化
1.5 分工与组件化
1.6 集中与分布
1.7 规划还是演化
1.8 简化也很必要
1.9 架构与软件开发（软件过程）
1.10 探讨传统企业IT系统架构
1.11 总结
2 以终为始的架构设计
2.1 缘起
2.2 我们的思考方式
2.3 为什么要做架构设计
2.4 如何做架构设计
2.5 架构是什么
2.6 总结
3 闭环架构方法
3.1 系统提升的一般性方法和反馈环
3.2 产品创新闭环
3.3 组织闭环
3.4 研发流程闭环
3.5 系统架构闭环
3.6 一个反馈闭环实例
3.7 总结
4 复杂与架构演进的关系
4.1 什么是复杂
4.2 用架构思维控制复杂
4.3 总结
5 架构师的核心能力
5.1 架构师承担的职责
5.2 架构师的核心能力
5.3 架构能力的修炼
5.4 总结
第2篇面向架构的架构（微服务）
6 快速继承微服务实践
6.1 概述
6.2 我们希望的微服务是什么样子的
6.3 实现微服务
6.4 实现的考量及调研
6.5 让微服务快速落地
6.6 总结
7 微服务架构下的事务处理
7.1 概述
7.2 使用传统的本地事务和分布式事务保证一致性
7.3 在微服务架构中应满足数据最终一致性原则
7.4 微服务架构实现最终一致性的三种模式
7.5 总结
8 微服务架构模式与实践
8.1 微服务的主要架构模式
8.2 大量微服务带来的挑战
8.3 微服务在好雨的解决方案
8.4 总结
9 微服务与DevOps架构实践
9.1 概述
9.2 某金融创业公司的微服务架构选型
9.3 设计思想
9.4 总体架构
9.5 对微服务的支撑
9.6 DevOps平台总体架构
9.7 面向微服务的研发团队介绍
9.8 总结
10 基于云的微服务架构
10.1 概述
10.2 德比软件数据对接平台的架构
10.3 德比软件微服务架构基础设施
10.4 API网关
10.5 服务框架
10.6 基础服务
10.7 服务降级
10.8 自动化
10.9 日志处理
10.10 调用链追踪
10.11 服务健康状态
10.12 发布管理
10.13 总结
11 Service Fabric：平台架构解析
11.1 Service Fabric概述
11.2 Service Fabric编程模式
11.3 Service Fabric服务通信
11.4 Service Fabric可靠服务概述
11.5 Service Fabric可靠执行组件
11.6 Service Fabric容器应用程序
11.7 总结
第3篇面向业务的架构
12 如何搭建高可伸缩的移动电商架构
12.1 概述微服务的主要架构模式
12.2 移动端的混合架构
12.3 服务器端的SOA架构
12.4 PC端和移动端的开发协作管理
12.5 基于容器的虚拟化
12.6 关于电商的私有云建设
12.7 如何应用弹性云来应对电商大促
12.8 应对电商大促峰值的“独孤九剑”
13 消费信贷系统“白付美”是如何持续优化的
13.1 “白付美”介绍
13.2 “白付美”从0到1
13.3 大促期间的性能保证
13.4 大促期间的稳定性保证
13.5 为服务多平台所做的优化
13.6 未来的优化方向
13.7 总结
14 美丽联合集团支付系统架构演进
14.1 概述
14.2 支付系统1.0
14.3 支付系统2.0
14.4 性能提升
14.5 稳定性提升
14.6 压测
14.7 成效
14.8 总结
15 金融撮合架构
15.1 概述
15.2 系统总体设计
15.3 总结
第4篇面向性能的架构
16 一线架构师带你玩性能优化
16.1 什么是系统优化
16.2 系统优化的方法论、思路和原则
16.3 性能优化
16.4 总结
17 性能优化的常见模式及趋势
17.1 性能优化的优缺点
17.2 性能优化的两种模式
17.3 单应用优化
17.4 结构型优化
17.5 两个结构型优化的案例
17.6 总结
18 性能优化之几种常见的压测模型及其优缺点
18.1 压测模型抽象
18.2 线下压测模型
18.3 线上引流压测模型
18.4 线上全链路压测模型
18.5 总结
19 缓存为王——无线缓存架构优化
19.1 无线缓存的定义、限制条件及影响
19.2 无线缓存要从全局考虑
19.3 数据、资源缓存及失效策略
19.4 总结

FAQ

How is this book different from books such as Enterprise IT Architecture Transformation or Phoenix Architecture?

This book focuses more on a collection of diverse practical experiences from multiple architects, with a more dispersed perspective but more specific scenarios, emphasizing decisions and trade-offs in practice rather than building a complete and unified theoretical framework or expounding a specific architecture paradigm.

Is the content of the book outdated?

Technical details may iterate, but the architecture principles, evolutionary thinking, and decision-making methodology that are the core focus of this book have long-term relevance. Specific tools and versions can be understood in light of current technological developments.

Is the book suitable for readers outside the internet industry?

Although the cases in the book mostly originate from the internet, the ideas it reveals about core architecture issues such as complexity management, decoupling, and scalability are also of high reference value to technical personnel in industries such as finance and telecommunications that likewise face complex system construction.

Comments

Find this book

This site is an index: you start “Search all sources” in your browser, and the entries it lists all point to third-party sites; please judge their availability yourself.

About the author

中生代技术社区 Author

The Mesozoic Technology Community is a community-style byline used for collective technical writing and content compilation. Publicly available information is limited, and no clear records have been found regarding its specific membership, founding date, or location. The library currently holds one work under this name, Architecture Treasure Book, commonly classified under programming and design. Judging from the title and category, the book addresses software architecture and is a practical technical title, oriented toward methods, experience, and case-based discussion of architecture design, suitable for developers and architecture practitioners. Community bylines often reflect collaborative writing, group discussion, and the pooling of practical experience, so the style tends to emphasize usefulness and readability rather than academic theorizing. Because verifiable background information is insufficient, this introduction is confined to an objective description of the existing work's subject matter and editorial positioning, without further inference about the community's size, members' qualifications, or the work's influence.