Database design and database creation

Database design and database creation

Everyone has a martial arts dream. We all envy Qiao Feng, who owns the 18 OPs of the dragon army, Zhang Wuji, who has the power and power of jiuyang, Ling wuchong, who has the power of yijinjing and exclusive jiujian, and envy the legendary lone man for defeat ......

In fact, there is a common secret to their success: they all have a deep foundation of internal strength. With a deep foundation for internal work, you will be able to use your skills. If you throw a stone at will, it means that the stone is magical.

 

 

What I want to say is: A good database design in a software system is like a good internal function of a system. A good database design can better cope with changes in requirements, and the easier the work (the better the work); and a junk database design, the more serious the effort to do, the harder you do it, the more powerful it is. In addition, as long as the demand changes a little, you will follow the major actions.

I believe that many companies work overtime. The important reason is that the database design is not flexible enough.

 

It can be said that a good database design is 1/2 of the success of a system. This sentence is not false. So we can't help but ask: how can we make a good database design?

In fact, I also want to know the answer. I did not dare to pat my chest and say that my design is better. However, I have some thoughts on database design and share them with you.

 

1. a deep understanding of the three paradigms.

Speaking of the three paradigms, if you haven't immediately reflected the three diagrams in your mind, don't talk about the design. Learn about database first. For databases that can be designed, the knowledge of the three paradigm must be well-developed. You can be skillful.

Some people design a database and only map their own convenience. Add a field here and where to add a field. Here, I want to say:If you do not have enough reason, follow the Three-paradigm Database Design strictly.

Sometimes, the third paradigm is not enough. We also need to consider the fourth paradigm and some subsequent paradigm norms.

Why? As we all know, requirements will change. Only by removing redundant fields can we achieve better unified management.

What's more, we follow the paradigm to design a database. Basically, we can determine the most important fields. Even if the fields will be increased or decreased in the future, it will not be a serious injury.

With regard to database design following the paradigm, I believe many people can recognize its importance and do this well. It can be said that understanding the three paradigms is the most fundamental.

 

2. profound understanding of business needs

A good database design must meet its business needs. The reason is very simple, and the example is also very good: the shoes look good and look good, the size is just good; Qian Xuesen knows more, adapt to the national conditions to create China's own atomic bomb; production relations, to meet the development needs of productivity ......

Therefore, to design a database, you must first analyze the requirements.

It is far from enough to understand the three paradigm to design a database with a degree of relaxation and ease of response to demand changes without any major deviations. It is very important to understand the needs in depth.

You need to understand where the data volume will be large and how to design it for better avoidance.

 

.................. (Not finished yet: sleepy, continue writing in another day ...)..................

 

The product manager will not pay for what he said yesterday. If your system cannot cope with changes, he will think that your technology is not good.