2019.9.9 to 9.10, it took two days to read through the "learning architecture from scratch."
In the wave of the Internet, technology iteration so fast, heart can not help but wonder, some confusion.
On completion of the combination at junior Spring + SpringMVC and MyBatis framework of thought was finally able to take a break, SpringBoot and SpringCloud appeared. After understanding SpringCloud assembly produces a strong subjective bias between the monomer and micro-services, distributed, clustered, high performance, high availability of these terms he has left a deep imprint in the brain.
Senior friends want to develop a APP, but in the back-end technology selection above made difficult. Just completion SpringCloud I naturally want to use as well as use. But the reason I calmed down, micro-services really do for us?
Not to mention the difficulty of business development, Docker and K8s deploy I just have heard, can not come in handy, others team did not find out about the relevant art container deployments.
9.8 Since late anxious and difficult to solve the problem of the day, 22:00 to sleep early. The next day got up early, go to the library whim stroll, summer vacation in the past two months, most library on the fourth floor window of the new shelves and updated. Pick a few interesting, so crazy days of reading began.
Recall
If you take the analogy of the Three Kingdoms era to do so, the book does not depict how sub-Dragon is martial arts, how is the training of the army, but on how Ming is marching lineup, strategizing.
In the book almost did not elaborate on one line of code, but rather focus on the structure and design of the entire system, or is based on a global view on software development.
The first part of the architectural design principles and processes
Appropriate, simple, evolutionary moment three principles to solve my confusion, focused on technology, would be to use technology and the use of technology.
It is the desirable way for specific business and budgetary cost to develop an appropriate development plan.
A second portion of high performance, high availability architecture pattern
Selection and use of the cache database, build server clusters to achieve high availability storage and computing, high-performance.
With the development of business, the initial infrastructure bottlenecks. The need to provide higher performance service. At the same time, it will bring a sharp increase in cost. So the beginning of the project, for project start-up, do not recommend using this direct way, when business traffic is too small, high performance, high availability is a game of ducks and drakes, wasted resources.
The third part of the scalable architecture model
Tiered, SOA, and micro-services. Similarly, by contrast hierarchy of the most simple, but for the SOA is integrated into a large number of heterogeneous IT systems, service is ideal for micro look after business development, but the service granularity divided debatable.
Part IV architecture combat
History of the opening of Taobao I am shaken.
Among them,
Internet business development
- Business complexity
- Start-up period (innovation, fast) 0-1w
- Development period (heap functions, optimizing period) 1w-10w
- Architecture period (split function, database demolition, demolition server) 10w to 100w
- Competition period (platform, create the wheel to avoid duplication; service oriented, interactive problem solving system) 1000w +
- Maturity (optimization) 100 000 000 +
- Users size increases
- performance
- Availability
Very valuable, is the compass in the technology choices blind.
summary:
With the business development and technology is changing , the right is better than the industry-leading, simple is better than complex evolution than in one step.