Thinking on Architecture Design (under continuous updating)

Service transformation of application

Apply layered design

1. Applications are usually divided vertically , Divide into Service layer 、 Business logic layer and data layer , Try to decouple each layer , The top depends on the bottom , And the lower layer should not rely on the upper layer in reverse
2. Layering involves the most feared Super data structure , Such as passing an object , Then pass this object all the time , And every layer can modify this object , This approach leads to two problems ：
   • Once the object is modified , All layers should be modified
   • It is impossible to know which layer of the object has been modified , Troubleshooting is complicated

therefore , When designing interfaces Try to use native data types , Such as int, string etc.

Tai Chung Tai 、 Small front desk

Development of system scale

The first stage ： Single system

Early business is simple , Several machines support a business system . All business logic is deployed on several machines （ even to the extent that 1 platform ） On the machine

The second stage ： Distributed business system

Single system All business logic is mixed , A hundred problems , It is difficult to develop functions and troubleshoot problems

Distributed business system ： Split the original single system into multiple High cohesion 、 Low coupling Centralized system . Like the user center 、 Commodity Center 、 Trading center, etc ...

“ High cohesion 、 Low coupling ”： Personal understanding , Functions are highly cohesive , Low coupling between centers

The third stage ： Platform stage

For each independent high cohesion business system , In order to quickly respond to business needs , Many times, business logic is written through code ; But different businesses , The corresponding business logic is bound to be different , It will lead to complex logic at the code level , The logical coupling between businesses is serious ; Ultimately, it will affect the efficiency of R & D , Platform came into being

** What is a platform ？** That is to split the basic capabilities and the characteristics of each business party , Isolate the logic between businesses . For example, two similar business parties may be in conflict , But they need to execute on the same platform , At this time, we must separate the business logic .
platform The core point , It is the openness of business abstract modeling and system architecture ; Business Abstract solution 80% Common problems of , Open solution of system architecture 20% Personalized problems

Platformization through reasonable business abstract modeling , Can solve 80% Common problems of ; Often new business access , You can reuse this 80% Commonness of , Greatly improve R & D Efficiency

Personal understanding ：

1. The core of platformization is business abstract modeling ;“ High cohesion ” It is inevitable that many general logic can be abstracted
2. The platform only solves the problems within the field

The fourth stage ： Business stage

platform The problem is , Each business covers several or even more fields , And they are interrelated , After a long time No one can tell the whole story , Simply look through the code by developers to understand the details , High cost ; In the end, the efficiency of needs assessment is often low , Poor business response ; The root cause is that no one understands the whole link , Non technical issues , It's a complex ecological collaboration problem

Business in Taiwan Based on the platform, we need to solve the problem of collaboration , Mainly through three things

1. Protocol standard , Operating mechanism
2. Distributed execution units that meet the standard
3. Centralized control unit

Business middle office is a set of business capability Standards 、 Operating mechanism 、 Business analysis methodology 、 Configuration Management 、 Execution system and Operation service team Constitute a system , It can provide fast 、 Low cost access and innovation

Personal understanding ：

1. Zhongtai must build its own set of agreement Standards , The access of the business party should be in accordance with the agreement of Zhongtai
2. The middle stage is a complete set “ Transportation research and measurement ” system , operating 、 Macroscopically, the product controls the development direction of the console , R & D and testing standardize the medium-sized capabilities from a technical point of view

Zhongtai

The positioning of the middle stage

The so-called positioning is to tell others what I can do 、 What I need and what I don't want .

1. What can I do? , This is the basic plate of Zhongtai . Zhongtai must have provided a clear 、 High cohesion function , The business side has this function, and the first thing it thinks of is this midrange
2. What do I need , This is a necessary agreement and specification between China and Taiwan ; Whether it is the access of new services , Or the function iteration of the old business , It must be based on this set of specifications ; What data is needed to access the middle station 、 What kind of interaction mode is provided , We should follow the norms of Zhongtai
3. I don't want anything , This is the boundary that the middle stage needs to be clear ; There is a limit to what kind of service the middle office can provide .

The efficiency of the middle stage is improved

1. Communication efficiency issues
   • Unified terminology ; Especially in the communication between operating products and developers , Inconsistent terminology will cause great communication obstacles （ We need to pay attention to some skills of data formation , For example, a good name ）
   • Structurally express requirements ： Pass the product requirements through a series of terms 、 Chart 、 Pages can be better understood and presented in the same context , Let the other party understand better
   • Unified business identity
2. Development efficiency
3. Test efficiency
4. O & M efficiency