Architecture Design of Student Information Management system

   recent learning architecture design, first of all from the most basic student information management system analysis.

Objective: thinking about the architecture design of student information management system. The first step: identify the complexity of the system.

The real purpose of    architecture design is to solve the problems caused by software complexity, so we should first identify where the complexity of the system is, and we will find out after analyzing the whole system.

Thinking step 2: basic function login registration information query score management course management step 3: performance

In   , there are about 10-50, 000 students in general schools. The access frequency of student information management system is not high, and the average number of visits per student is less than once per day, so the performance requirements are not complicated. The storage and use of conventional MySQL database can be competent, the cache can be eliminated, and the Web server is more than sufficient to use Nginx.

Think about step 4: scalability

The function of    student information management system is relatively stable, and the expandability space is not large, so the expansibility is not complex.

Think about step 5: high availability

Even if the    student information management system is down for 2 hours, it does not have a great impact on student management, so it does not have to do load balancing, not to mention complex schemes such as living in different places. However, if all the students' data is lost, the repair is very troublesome and can only be repaired one by one manually, which is difficult to accept, so it is a bit complicated to consider the high reliability of storage. We need to consider a variety of abnormal situations: machine failure, computer room failure and so on. For machine failure, we need to design the master and backup scheme of the same computer room of MySQL; for the failure of computer room, we need to design the synchronization scheme of MySQL across the computer room.

Think about step 6: cost

   because the system is very simple, basically a few servers can be done, for a university is not a problem, so do not need to pay attention to too much.

Conclusion

   so far, we can see that the main complexity of the system design is reflected in the storage reliability, need to ensure that when abnormal, do not lose all data (the loss of several or dozens of students' information is not a problem). The corresponding architecture is as follows: