[reading notes] the way of enterprise IT architecture transformation Alibaba's China Taiwan strategic thinking and Architecture Practice

Let me start with a statement , The purpose of reading this book is not to build Zhongtai , I am more interested in their practice and thinking in the construction process .

The following is my summary and thinking

1、 Architecture evolution

There is no unchanging architecture , Architecture needs continuous evolution . The architecture of Taobao has continued to evolve , From the chimney 、 To distributed and then to shared architecture , By the original Taobao team 、 Tmall teams operate their own products 、 Customer 、 Transactions wait until shared services appear later , Finally, the center provides sharing , Make the architecture in the process of evolution , Common services have also been precipitated and reused

2、 Trial and error and innovation

In the process of development , No matter what industry has dividends , Everyone will try to divide meat , Therefore, we need to maintain a spirit of trial and error and innovation in the process of business development , You can't just make one piece , Some people should be encouraged to do business trial and error , Only in this way can we maintain the competitiveness and vitality of our business , Only you can truly empower others , Others can do trial and error and business innovation well , Mentioned in the article supercell Our team is like this ,7-8 A group of people , To develop products , Try and make mistakes in the market , This is a good case , He can encourage employees to observe life , Find people's needs , Then do business innovation , Finally, bring commercial benefits

3、CRUD BOY

Many people say that the current development , They are all themselves CRUD, If you work every day, all the time CRUD, There is no time to do other things , It's really possible that you can only do one during working hours CRUD BOY. But have you ever thought about changing this , Participate in the design of the scheme , Not just an executor , You need to do in-depth analysis and understanding of the needs , Know the background of the requirements , So you can design , To carry out independent development , Of course, an in-depth understanding of the requirements may not be able to design a perfect solution , You also need to know what your upstream and downstream, dependencies and links look like , Only in this way can a closed loop be formed . Of course , If you are already responsible for the specific operation process of your business system 、 Master the data model , Do you have your own understanding and ideas about the development of business , How to better optimize the business process , Do business innovation , Or whether you consider changing to another field to be familiar with and master , Master the whole ring business . Only in this way can we understand business .

4、 Microservices

Micro services, which have been popular in recent years, are also one of them , Everyone is disassembling a big one , The goal is to iterate quickly , Services have better scalability , Reduce system complexity . If you use microservices , Whether the service is split according to the field , How are the boundaries of services defined ？ Service online monitoring 、 Requested link 、 Track and analyze how to do ？ Is there any meituan CAT、 Or open source Skywalking、 perhaps Zipkin+sleuth To achieve link tracking and analysis , Is it useful to prometheus Come on jvm、CPU、IO And other information . The service launch is just the beginning , The important thing is the later operation and maintenance , How to accumulate data , To do business analysis , Is another important topic , The data is oil , No reliable conclusion can be drawn without data

5、 Thinking questions

Whether as business development or other roles , We all need to think about the calling link of our own services 、 Whether the call scenario and data are reasonable ？ What is the trend of service invocation , What is the instantaneous peak value generated ？ Whether the highest level of service capacity has been reached ？

In business process design , What services does this service depend on ？ What is the dependent path of the whole link ？ What are the core services ？ If something goes wrong , What will be the impact ？ Where is the time-consuming point of a request , How to analyze and improve ？ Under abnormal circumstances in the past , Where the error rate will be higher ？ Which service business links are the bottleneck of processing