Data Center reconstruction-what happened to our "restructuring?

The reconstruction of the IDC is about to end. When the "third" system is over, it is necessary to think about the purpose of restructuring.

Some people may say, what's the purpose? It's not just to change the programming language to. net. After the bug is completed, you can execute it. What is the power of such a cool day?

If you have such an idea, I must say: You (white) have worked hard!

No matter what you do, you cannot make progress without summative thinking.

There are also many shortcomings in some of my restructuring discussions or reflective summaries. I hope you can correct them more. Thank you!

This article will discuss the reconstruction system from five aspects: system architecture, UML diagram guidance, design mode application, data processing and object-oriented.

 

First,System Architecture.

In this restructuring, we have all applied a three-tier architecture to reduce coupling and improve system reusability and maintainability. In the design, compared with the fundamental process programming of the first data center, we have also experienced the convenience and easy maintenance of the architecture.

By adding basic auxiliary modules or tools such as appearance, sqlhelper, and configuration files, we once again realized the great convenience of independent encapsulation. From decoupling to encapsulation, we can see the object-oriented.

 

Second,Guidance on UML diagrams and documents. This time, the focus is on the UML diagram. the use case diagram, package diagram, class diagram, and sequence diagram are the key.

Design of packages and "Layer 3", class diagrams, and layer D and layer B in Layer 3 (different classification standards, such as designing layer B based on database tables or functions) and time sequence diagrams are inseparable to guide the function operation process, so we must carefully analyze them in advance. Of course, these are based on requirement analysis and case design.

 

Again,Design Patterns.

So far, the difficulty of the application design model is how to adapt a function or series of functions of the system to the design model. During the learning process, it is important to understand and visually describe each instance, so that we can better adapt to future system instance analysis.

In data center reconstruction, I understand or use the following design patterns:

Policy mode-different billing methods are implemented for different types of users

Abstract Factory + reflection-simple switching of different tables

Appearance-the appearance layer between the U layer and B is further decoupled to make the U layer more independent.

Template-similar windows do not require repeated code

Adapter-integrate external reports with VB.net

Singleton-ensure that a window is not new

Responsibility chain-from general users to operators to administrators, there is always a problem to be solved

 

Let's talk about it again.Data processing.

Data processing is a key issue at any time, especially in the modern Big Data era. Efficiency and Security are even more important. In this IDC reconstruction, I have a deeper understanding of some database functions.

Here are two points. First, the second database establishment and improvement were conducted based on the initial analysis of database creation and the lack of necessary Three-paradigm analysis during the first data center. Even in the process of system programming, sometimes we still cannot avoid moving the database and modifying the field to make up for the shortcomings of our analysis and the present.

Second, it is necessary to stop and explore the road cards marked with keywords such as transactions, stored procedures, triggers, and views. The storage process and trigger are easy to run and conform to the encapsulation characteristics. The strict control of certain "Mutual influence" functions of transactions on the system forces us to explore their advantages and apply them. The application of the stored procedure is as follows: offline and Combined Query. transactions can be considered for recharge and checkout.

 

Finally, let's talk about the system andObject-oriented.

In this restructuring, I realized the ubiquitous ideological advantages of object-oriented.

For example, inheritance: Administrators inherit operators and operators inherit general users. They not only understand the relationship between them, but also simplify the structure. In addition, the application of the interface also inherits.

Data encapsulation and function encapsulation are everywhere. A good system design requires a deep understanding of object-oriented and interface-oriented systems. In addition, it is the best way to improve our understanding in practice.

 

Summary: There are still many deficiencies in practical application for this data center reconstruction. How to use these ideas through this reconstruction, or even with the implementation of the next cooperative version, is the best supplement to experience. In this way, we can take the learning itself as a system for perfect analysis and best practices to cope with the following learning.

Data Center reconstruction-what happened to our "restructuring?