foreword
Becoming an architect is an indispensable path for programmers to advance, especially in today's increasingly intelligent society, which puts forward new requirements for every programmer's architectural ability. There is Yan Ruyu in the book. There is a golden house in the book. Only by continuous learning can you get rid of the stalk of being laid off at the age of 35!
It is said that there are two development directions for programmers: one is to study technology and become an architect; the other is to be a manager and develop to the level of technical management , but the road to management is almost saturated. The choice of most programmers is: go to architecture Teacher direction development! Today, the author recommends this excellent book to everyone: "Learning Architecture from Scratch", read it patiently, and you will gain more insights.
Many people may not be able to answer exactly what "architecture" refers to. For example: What is the relationship between architecture and framework? What's the difference? Linux has an architecture, MySQL has an architecture, JVM also has an architecture, and business systems that use Java development, MySQL storage, and packages on Linux also have an architecture. Which architecture should we focus on? WeChat has a structure, the login system of WeChat also has a structure, and the payment system of WeChat also has a structure. When we talk about the structure of WeChat, what structure are we talking about?
The key points are nothing more than subsystems, systems, modules, components, etc., frameworks and architectures.
Some thoughts about the author
Many books on architecture are actually pouring water. When talking about architecture, they start to talk about the details of certain technologies and products. This book, on the other hand, comprehensively incorporates all aspects and considerations of architectural design into an overall framework. The conclusion is clear and straightforward, and the summary is simple and clear.
The core value of architecture is to identify complexity and solve it in a targeted manner. At the same time, the three principles of architecture and complexity are explained very clearly. It is rare to cover and explain almost all the nouns involved in distributed and microservices . Very good introductory book, which can be used as a reference book for repeated reference.
Not much to say, go directly to the catalog
Table of contents
Part 1: Concepts and Fundamentals (chapters 1-3)
Some content shows:
Part II: High Performance Architecture Patterns (chapters 4-5)
Some content shows:
Part III: Advanced Architecture Patterns (chapters 6-10)
Some content shows:
Part IV: Scalable Architecture Patterns (chapters 11-15)
Some content shows:
Part V: Architectural Combat (chapters 16-20)
Some content shows:
All the notes, interview questions, resumes and other materials mentioned below can be found in the self-storage area of the official account [Retired Programmer]
