Detailed explanation of the relationship between Zhongtai, wechat and DDD

Zhongtai

The concept of Zhongtai , It's been a hot day in China recently . Ali 、 tencent 、 Baidu 、 JD.COM 、 Meituan 、 Didi and other Internet giants , From last year to this year , One after another began to adjust the organizational structure , Intend to build central Taiwan . There are also many people who think , Central Taiwan is not the magic weapon to solve all problems , Small companies don't need to use middle office , Only companies with a certain scale need Zhongtai . Is there a middle stage ？ What stage is suitable for middle stage / Companies of scale ？ It is a problem worth discussing .

1. What is midfield , What is the problem to be solved ？

This one was first put in by Ali 2015 Put forward in “ Tai Chung Tai , Small front desk ” The concept that extends from strategy , Inspired by a small Finnish company Supercell—— There is only one family 300 Employees , But launched a series of pop games , Is the most profitable star game company in the world . This seemingly small company , Set up a powerful technology platform , To support many small teams in game research and development . thus , They can focus on Innovation , Don't worry about the fundamental but crucial technical support issues . It's this small company , It created the “ How to play ”, And applied it to the extreme .

Supercell How to succeed ？

The best team creates the best game , A game company , Manage in the way of a professional sports team . In this mode , The sole mission of the founders and management is to obtain the best talents , Create the best environment for them , Give them freedom and trust , Help them out of trouble , Make the company a place where the best talents can have the greatest impact
Completely reversed management structure ,300 The human team is divided into several small teams ,5-7 A small team of game developers , Develop your own game , Launch public beta at the fastest speed , Check the popularity of the game . These small teams are also called “ cells ”(cell),Supercell It's a collection of these cells , This is also Supercell The origin of the company name .
A small and sophisticated team , One “ cells ” The core of is usually only 5 people , Not more than 7 people . Although there are few employees, they are excellent , And plenty of freedom . Small teams mean that trial and error costs are not too high , Time and direction can also be adjusted and changed , To meet the needs of the rapidly changing market , I'm more agile with the fighter , Once you find the right target , We can devote ourselves to the expansion of the results . They will share all the information with everyone in the company . Every day in the morning , Everyone will get an email , Including detailed data of each game , The working environment is very transparent . Good game performance , Everyone can see , If the performance is not good , Everyone knows . thus , Will form a more stressful work environment , But for the right person , This is also the driving force of their efforts .
Kill unsuccessful projects , The R & D team decides its own ideas and ideas , But they also set goals for their projects . For example, before a new project is tested , The team should set an indicator , For example, players retain 、 Participation , Then tell the whole company about this goal . After the game enters the test , If the target is not reached , It will be cancelled , No matter how much team members love it, they can't stop . stay Supercell, Failure is never a shameful record , Instead, it's a driving force for progress . Distinctive “ Celebrate failure ” Rooted in its corporate culture , Pananin thought ：“ We built the company on the basis of the lessons we learned from the failures . The faster you fail , The faster we learn , It's going to get better ”.
So-called “ Zhongtai ”, In fact, it is a platform for the front desk , The only purpose of its existence is to better serve the large-scale innovation of the front desk , So as to better serve users , So that enterprises can truly achieve the continuous docking of their own capabilities and user needs

2. Advantages and disadvantages ？

To some extent, the middle stage was born for the front desk ！ For business agility , innovation ！ There are three characteristics ：

agile Business needs change fast , Changes are calculated in days or less , A single large application , It becomes more and more difficult for a large development team to change a single application . Turn large applications into multiple small application combinations , To adapt to the rapid changes outside , Achieving business agility .
decoupling As the business grows , The interaction between business systems usually becomes more and more complex . The modification of a function may affect many aspects . Only functions that will require a lot of interaction are independent , Disassemble from the application , This can greatly reduce the coupling between applications .
Reuse Some common capabilities through reuse , Greatly improved development efficiency , Avoid redundant construction . At the same time, data and processes can be centrally managed and optimized .
So what should be included in the middle stage ？ The middle stage can usually be divided into three levels ： Business level , Data level and technology bottom .

Business Center Business services combine the common needs of the business into services , For example, e-commerce companies , Customer , goods , logistics , Payment is public need , For example, automobile manufacturers , user , vehicle , Order , Delivery is a public need . Combine these common businesses into a unified business service , For each business unit .
Data center Data service data age , Business is increasingly dependent on data , contain ： Data collection , Data processing , Data algorithm and analysis , report form , And data governance .
Technology Center The basic service is usually the underlying service , Technology oriented . These underlying technologies include ： Safety certification , Rights management , Process engine , Gateway , news , Notice, etc . These components are usually not relevant to the business , It belongs to the function that every application needs to use .
At this stage , Most of the companies that put forward the middle platform strategy or build a large middle platform , Most of them have similar difficulties . Business has developed rapidly for many years , Many problems are difficult to return or are being solved in large numbers “ Repeat the wheel ” The problem of , The concept of Zhongtai , In many cases, it is in line with the business development of large companies , And is widely recognized . For many small and medium-sized companies , When they get out of their predicament , When we enter the stage of rapid development , There will be many problems , But one of the problems with high probability is , Past business models , Product capabilities are likely to fail to fully withstand the pressure of large-scale user growth .

3 How to build a middle platform ？

The construction of Zhongtai is not so easy . First of all, establish “ Zhongtai “ Supporting relevant management mechanism , The second is to establish the application architecture , Start with the relatively easy basic shared services , To customize the business platform that fits the business . In the process of establishing the middle stage , It needs the supporting background infrastructure for the middle stage operation . The construction of Zhongtai can be summarized as five steps .

Establish a reasonable management mechanism The establishment of Zhongtai , Never make it a project system , The middle office needs to use the way of product management to treat . This is because the services provided by Zhongtai to the outside world need constant iteration , Adapt to the needs of the business , Otherwise, after a period of time , The front desk is solidified because of the service provided by the middle desk , You have to create a new service to meet your business needs , Gradually do not use the public services provided by Zhongtai . For medium-sized products , The question that must be considered is , How many business scenarios can this feature satisfy now or in the future ？ If there is a new business in the future , Is it possible to reuse ？ Or say , How much adjustment is needed to reuse ？ Even , Is it possible to output this function to the outside world , Provide SaaS The service of transformation .
Build an application architecture suitable for enterprises Enterprises are different from Alibaba , Alibaba is basically C End application , Online retailers 、 recreational 、 consumption . Business systems are self-developed . Enterprises have a heavy burden of history , Independent development ability is not strong , Existing purchased commercialized software , There are also self-developed systems . such as , Manufacturing enterprises have back-end SAP ERP,PLM,MES,WMS Such as system , In recent years, external e-commerce has emerged , Customer service , Front end systems such as marketing services . The front-end system changes quickly due to the needs of the market , The system iteration speed is required to be calculated in weeks or even days , And the traditional application in the background , Changes and iterations are usually calculated in months or even years .
Provide basic shared services Basic shared services are basic public shared services facing the technical level , Because most services are integration functions , So it can also be called “ Integrated middle stage ”. There are roughly the following shared public services ：

4. Data center

Enter the data age （DT）, The importance of data is increasingly recognized by enterprises . The collection of data , Analysis and calculation , Deep learning , And transferred to the core competitiveness of the enterprise .

5. Business Center

Every enterprise in the business is different , It is highly personalized , Cannot be obtained by direct purchase , Because it is closely related to business . Business needs long-term precipitation , Abstraction and induction . Building a business platform is never an overnight thing .

Microservice definition

What is microservice ？

Wiki defines it as ： A software development technology - Service Oriented Architecture （SOA） A variant of the schema style , It promotes the division of a single application into a small set of services , Services coordinate with each other 、 Cooperate with each other , Provide the ultimate value for users . Each service runs in its own process , Services and services use lightweight communication mechanism to communicate with each other （ Usually based on HTTP Of RESTful API）. Each service is built around a specific business , And can be independently deployed to the production environment 、 Class production environment, etc . in addition , Try to avoid unified 、 Centralized service management mechanism , For a specific service , Should be based on context , Choose the right language 、 Tools to build it .

DDD Definition

wiki paraphrase ：

Domain-driven design （ English ：Domain-driven design, abbreviation DDD） Is a model that connects implementations to continuous evolution [1] Software development methods to meet complex requirements . The premise of domain driven design is ：

Put the main focus of the project on the core areas （core domain） And domain logic
Put complex design in a bounded domain （bounded context） On the model of
Initiate a creative collaboration between technical and domain experts to iteratively refine the conceptual model , Solving problems in specific areas
Domain driven design is a domain model （ Wall crack recommendation @ A Bai Domain model series ） To drive the idea of system design , Not by storing data dictionaries (DB Table field 、ES Mapper Fields, etc ) To drive system design . A domain model is an abstraction of a business model ,DDD It is a way to translate business model into system architecture design .

The relationship between the three

In my submission , To apply DDD, The first task is to have a thorough understanding of DDD The core design idea of , Make clear DDD、 tiny
The relationship between service and middle office . The essence of midfield is business model , Microservice is the system implementation of business model ,DDD It's one
A design idea , It can guide both business modeling and microservice design in midfield , Between them is such an iron triangle
Relationship .DDD Emphasize the integration of domain model and microservice design , First there's the domain model, then there's the microservice , instead of
Talk about microservice design without domain model .
secondly , It's through strategy , Build a domain model , Divide the microservice boundary . This step is the key , You can use columns
Some of the experience in .
Last , Through tactical design , We will move from domain model to microservice design and implementation . here , The boundary is clear 、 sustainable
The prototype of evolving microservice architecture is in front of you .
Follow the above process , The design idea of this course was born .

Refer to learning courses ：DDD Practical course [ More information about wechat official account ： Wu Peixuan ]

Reference resources
https://zhuanlan.zhihu.com/p/75223466
http://www.woshipm.com/it/4231298.html
https://baike.baidu.com/item/%E5%BE%AE%E6%9C%8D%E5%8A%A1/18758759
https://www.zhihu.com/question/65502802/answer/802678798