Method for realizing separation operation of service software programs

Abstract

The invention relates to the field of on-line software service and discloses a method for realizing the separation operation of service software programs. According to the present invention, a solution that provides a high degree of stability in the availability of serviced software programs can be provided, the service software program with the traditional MVC architecture is separated into two parts: an MC layer code package (i.e. a model layer code package and a control layer code package) and a V layer code package (i.e. a view layer code package), and distribution installation and operation are performed on the two parts. The stability of the system is improved on a middle-larger size service software system, the ability of concurrent processing and lateral expansion is realized, practical application and popularization are facilitated.

Description

technical field [0001] The invention belongs to the field of online software services, and in particular relates to a method for realizing separate operation of service software programs. Background technique [0002] Currently, most known online service software programs run on a single server, and the software programs are complete in a single server. However, the single-point failure of the server is inevitable or avoided, that is, whether it is a system hardware failure, a system software failure, or a single / combined failure of the application software, it will cause the interruption of the functions and services provided by the currently running service software. [0003] In order to prevent service interruption, in traditional server software, the same software is generally installed on multiple servers to form a master-slave structure, but it does not fundamentally solve the problem. There will still be the following problems: (1) only the master server is working d...

AI Technical Summary

Problems solved by technology

However, the single point of failure of the server is inevitable or avoided, that is, whether it is a system hardware failure, system software failure or application software single / combined failure, it will cause the function and service provided by the currently running service software to be interrupted

[0003] In order to prevent service interruption, in traditional server software, the same software is generally installed on multiple servers to form a master-slave structure, but it does not fundamentally solve the problem

There will still be the following problems: (1) only the master server is working during normal work, and the slave server is idle; (2) if the master server is abnormal, switching the service from the master server to the slave server requires switching time, and After the main server returns to normal, the same is true for switching back; (3) During failover, the connection established between the client and the main server will be forcibly interrupted, and all ongoing businesses will be suspended. When the main server returns to normal, the client The connection between the client and the backup server will also be completely interrupted, and the connection with the master server needs to be re-established; (4) Generally, the configuration of the master server will be higher than that of the slave server. If the master server goes down during a business peak, the backup server cannot support the business; (5) If the business volume of a certain business surges, in addition to the optimization of the software system, it is necessary to increase the hardware configuration to make up for it. However, there is an upper limit to the accumulation of the hardware performance of the server itself. Configuration requirements can become infinitely large

Images