Reprinted: How does Mu Weichengzhou draw the architecture diagram? - Know almost
When we do system architecture design, how to quickly convey our design ideas to the outside world. 4+1 tries to be suitable for us to clarify our thoughts and express our ideas. In our report, it is more appropriate to use a structure diagram to express our views for the recognition and support of the leadership. The architecture diagram includes overall architecture, logical architecture, application architecture, technical architecture, data architecture, functional architecture, network architecture, operating architecture, etc.
1. The overall structure diagram
The overall architecture basically embodies all the following architectures. All the following structures are also consistent with the overall structure.
The overall architecture needs to explain a few things:
-
What is the hardware setup of the whole system?
-
Where does the data come from, how is it collected, stored, processed, and exchanged?
-
What functional abstractions have been made to support upper-layer applications?
-
What business applications are provided? What are the functions of management and control?
-
How do end users access and use these applications?
-
How does the system interface with external systems?
-
How to ensure the safe, reliable and high-quality construction of the entire system?
Security system architecture diagram
2. Logical Architecture
The logical architecture is the content of the overall architecture that removes various guarantees and the underlying hardware foundation, which are not the core of the logic of software development. Therefore, there are many simple projects that do not write the logical architecture at all, and just use the overall architecture directly. If it is complicated, it is necessary to write clearly the logic of the middle layer of the overall architecture above.
The focus is on functionality, including functionality that is directly visible to the user, as well as functionality that is implicit in the system. Or to describe it in a more popular way, the logical architecture is more biased towards the "layering" we understand in daily life, dividing a project into a classic "three-tier architecture" such as "presentation layer, business logic layer, and data access layer".
The purpose of logical architecture design is to tell readers how the entire system works. The so-called system architecture mainly refers to this part. The early monolithic architecture, the later various layered architectures, microservices, service grids, etc., are all designed here.
When designing, many design models will be used. For example, if you see an application support layer/service layer, this is an MVC that separates business logic from the user front end. And all logical architectures have a data layer, which is the earliest MVP, that is, the separation of data, user views, and processing logic. Of course, the more complex the system, the more complex the architecture diagram.
SAIC-GM B2C Logic Architecture
3. Business structure
The enterprise architecture framework white paper divides the architecture into four levels, namely business, application, data, and technology. Only when the business is sorted out can the application, data and technical architecture be guided. The analysis process of business architecture is complicated, and the final output may not be just an architecture diagram. There are more detailed processes, modeling and other outputs. A good architecture diagram is probably: the relationship between each product module is clearly explained in layers and modules.
4. Application Architecture
The application is too rich and needs to be sorted out. What are the internal applications and how to provide external services. Many projects do not have this, because there are relatively few applications, and it is not worth a little more manual writing. It is used to elaborate the detailed logical architecture.
Internet Hospital - Application Architecture
5. Technical Architecture
It is very clear what the technical architecture needs to do, that is, what components and technologies we use to solve what problems at each layer. The requirements are: precise, clear and concise. But the general structure is similar, from the bottom storage to the top interface. On the right are some common operation and maintenance systems or support services. It reflects the dependent SDK, third-party class library, and middleware.
Cloud Technology Architecture
In more cases now, multiple system modules form a large distributed system, or in the case of multiple existing systems, it is necessary to integrate and develop a product.
In this case, the technical architecture is a high-level technical architecture, which not only reflects technical components, but also some higher-level modules and even specifications.
6. Data Architecture
Data architecture is actually describing how data comes from, how to store, how to process, and how to use from the data side. Starting from the data source, how the data is integrated; after it is integrated into the data warehouse, where does it exist, how the data warehouse is layered, and what each layer does; how to store and manage it in the data mart; to the data application What applications does the layer provide. For all of the above, what technology is used, what components are used, and what problems are solved. What kind of data does the system need, how to store it, and how to design the data architecture.
7. Deployment Architecture
The deployment architecture is also called the network architecture, which is the design of the underlying server and network, and the design that provides network security and service reliability. To understand it more simply, it means that your applications and databases are placed on that server, which IP end these servers are on, and how to access them. To specifically reflect: computer room; server number and configuration; network partition relationship; reflect database, high availability; reflect load balancing;
8. Functional Architecture
It is the directory structure of the function menu of the front page. How do you organize all the functions of the system to provide users with corresponding services.
Payment System Architecture
9. Operating structure
The operating architecture is actually the interior of the software. How these systems operate internally usually draws many sequence diagrams, state diagrams, and activity diagrams. Generally, a running architecture is not drawn separately, but is drawn in the outline and detailed design.
k8s running sequence diagram
Article source: Mu Weicheng