APP disaster recovery system

Abstract

The invention provides an APP disaster recovery system, and particularly relates to the field of software application. The system comprises a disaster recovery environment, a production environment and a gray environment, and takes over businesses related to an APP currently running in the production environment by taking the gray environment and the disaster recovery environment as switching targets when the generation environment breaks down. By means of the mode, when the production environment breaks down, non-perceptual switching is achieved through disaster recovery switching, normal use of an APP by a user is not affected, and meanwhile the problem that only a gray level system serves as a disaster recovery system of the disaster recovery environment, and the problem related to application clusters cannot be solved is solved.

Description

Technical Field

[0001] The present application relates to the field of software applications, and in particular to an APP application disaster recovery system. Background Art

[0002] As the only touchpoint for government and enterprise businesses, any system problems will greatly affect the user experience of government and enterprise customers. Therefore, there are higher disaster recovery response processing requirements for APP application systems.

[0003] In order to solve the problem that problems with the APP system affect the user experience of government and enterprise customers, the existing technology usually uses the following means: adding a grayscale environment and using the grayscale environment as a disaster recovery switching environment to enable the APP to implement a grayscale switching function. When the health of the APP application system is detected to be abnormal, the APP application system is switched from the production environment to the grayscale environment, so that the normal use of the APP application can be maintained through disaster recovery switching without the user's perception.

[0004] However, the above disaster recovery system can only be applied to APP applications included in the grayscale environment, and cannot solve problems involving application clusters. Summary of the invention

[0005] The present application provides an APP application disaster recovery system to solve the technical problem that a disaster recovery system using a grayscale system as a disaster recovery environment cannot solve problems related to application clusters.

[0006] In a first aspect, the present application provides an APP application disaster recovery system, including:

[0007] The production environment includes an APP application system and a production database for the APP application system to call, and the production environment is used to support the business operations involved in the APP application system;

[0008] The disaster recovery environment includes a disaster recovery application system equivalent to the APP application system, and a disaster recovery database for the disaster recovery application system to call. The disaster recovery environment is used to take over the business involved in the APP application currently running in the production environment when a failure occurs in the production environment, wherein the disaster recovery database is a backup database of the production database;

[0009] The grayscale environment includes a grayscale application system and a grayscale database for the grayscale application system to call. The grayscale environment is used to take over the business related to the APP application currently running in the production environment when the production environment fails and the application called by the user is included in the grayscale application system. The grayscale application system is a backup system obtained based on the APP application system and includes some applications of the APP application system.

[0010] Optionally, in the system as described above, the disaster recovery system further comprises a gateway module, wherein:

[0011] The gateway module is used to complete the switching between the production environment and the disaster recovery environment, or the switching between the production environment and the gray environment.

[0012] Optionally, in the system as described above, the gateway module comprises at least one external gateway and at least one internal gateway, wherein:

[0013] The at least one external gateway is used to perform traffic switching when the APP application system is called externally and a failure occurs in the production environment, so as to complete the switching between the production environment and the disaster recovery environment, or the switching between the production environment and the grayscale environment;

[0014] The at least one internal gateway is used to perform proxy switching when the APP application system is called internally and a failure occurs in the production environment, so as to complete the switching between the production environment and the disaster recovery environment, or the switching between the production environment and the grayscale environment.

[0015] Optionally, in the system as described above, the APP application system includes an application management platform, and the application management platform is used to manage an application list consisting of multiple applications included in the APP application system, and at the same time set optional fields for each application in the section to which the application list belongs, so that operation and maintenance personnel can adjust disaster recovery switching information according to the optional fields, wherein the optional fields are determined according to the type of application corresponding to the current section, and the types include: APP applications and H5 applications.

[0016] Optionally, in the system as described above, the application management platform is specifically used to set a first optional field in the section corresponding to each APP application, wherein the first optional field includes: a disaster recovery environment to increase the release request address, a disaster recovery environment release root directory, and a disaster recovery environment release resource path;

[0017] A second optional field is set in the section corresponding to each H5 application, wherein the second optional field includes: a disaster recovery environment increase release request address, a disaster recovery environment release root directory, and an environment switching field.

[0018] Optionally, in the system as described above, the application management platform is also used to, when a failure occurs in the production environment, query the corresponding switching configuration based on the environment switching field set on the panel corresponding to the currently running application; after determining to switch the production environment to the disaster recovery environment based on the corresponding switching configuration, pull the disaster recovery switching information based on the first optional field or the second optional field, and switch to the disaster recovery environment based on the disaster recovery switching information.

[0019] Optionally, in the system as described above, the grayscale environment further includes a grayscale publishing module, wherein:

[0020] The grayscale release module is used to perform the change operation on the grayscale database before performing the change operation on the production database, and monitor the performance and stability of the data in the grayscale database after the change operation, so that the operation and maintenance personnel can adjust and optimize the change operation.

[0021] Optionally, in the system as described above, the grayscale release schedule is predetermined and stored by an operation and maintenance personnel, and is used to indicate the time of performing the change operation on the grayscale database, the target server of each change, and the success indicator;

[0022] The monitoring and analysis component is used to monitor the grayscale database after the change operation, and analyze the change operation according to the monitoring result, the grayscale release schedule and the received feedback information, wherein the feedback information is used to indicate the evaluation of the user corresponding to the target server on the change operation;

[0023] The troubleshooting component is used to send operation prompt information to the change component according to the analysis result, wherein the operation prompt information is used to instruct the change component to perform an expansion operation or a rollback operation.

[0024] Optionally, in the system as described above, the change component is specifically used to back up and store the current version of the grayscale database before performing the change operation, and after receiving the operation prompt information, control the grayscale database after the change operation to roll back to the most recently backed up version;

[0025] Or, a new target server is obtained according to the grayscale release schedule, and the change operation is performed on the new target server.

[0026] Optionally, in the above system, the disaster recovery system further includes a detection module, wherein:

[0027] The detection module is used to: when receiving a business application from a user, monitor the health of the production environment, and when the health is abnormal, obtain the corresponding call type and the application called in the APP application system according to the business application, wherein the call type is an external call or an internal call,

[0028] Acquire the inclusion relationship between the application and the grayscale application system, determine the disaster recovery switching environment according to the inclusion relationship, and acquire the disaster recovery switching process according to the application, wherein the disaster recovery switching process is determined according to the disaster recovery switching information contained in the selection field corresponding to the application;

[0029] A corresponding gateway is obtained according to the call type, and the production environment is switched to the disaster recovery switching environment through the gateway according to the disaster recovery switching process, wherein an external call corresponds to an external gateway and an internal call corresponds to an internal gateway.

[0030] The present application provides an APP application disaster recovery system, which includes a disaster recovery environment, a production environment, and a grayscale environment. The grayscale environment and the disaster recovery environment are used as the switching targets when a failure occurs in the production environment, and the business related to the APP application currently running in the production environment is taken over. Through the above method, when a failure occurs in the production environment, the disaster recovery switching is realized without perception, which does not affect the normal use of the APP application by the user. At the same time, it solves the problem that the disaster recovery system that only uses the grayscale system as the disaster recovery environment cannot solve the problem involving the application cluster. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0032] Figure 1 This is a schematic diagram of the structure of the APP application disaster recovery system. Figure 1 ;

[0033] Figure 2 This is a schematic diagram of the structure of the APP application disaster recovery system. Figure 2 ;

[0034] Figure 3 This is a schematic diagram of the structure of the APP application disaster recovery system. Figure 3 ;

[0035] Figure 4 This is a schematic diagram of the structure of the APP application disaster recovery system. Figure 4 .

[0036] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0037] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0038] In the existing technology, most APP applications for government and enterprise businesses use grayscale systems as disaster recovery switching targets when failures occur in the APP application production environment in order to avoid system problems affecting the user experience of government and enterprise customers. This is used to achieve imperceptible switching and ensure user experience.

[0039] However, the grayscale system is also used for grayscale releases, that is, to plan the system updates according to the scope, and adjust the update plan according to the stability of the grayscale database to avoid directly changing the database corresponding to the production environment, causing system failures and affecting user experience. Therefore, the grayscale environment is only suitable for non-perceptible disaster recovery switching when the production environment corresponding to the APP application covered by its deployment fails, and cannot solve related problems involving application clusters.

[0040] In order to solve the above problems, the present application provides an APP application disaster recovery system, which includes a disaster recovery environment, a production environment and a gray environment, and uses the gray environment and the disaster recovery environment as the switching targets when a failure occurs in the production environment, and takes over the business related to the APP application currently running in the production environment. Through the above method, when a failure occurs in the production environment, the disaster recovery switching is realized without perception, and the normal use of the APP application by the user is not affected. At the same time, the disaster recovery system that only uses the gray system as the disaster recovery environment cannot solve the problem involving the application cluster.

[0041] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0042] Figure 1 This is a schematic diagram of the structure of the APP application disaster recovery system. Figure 1 .like Figure 1 As shown, the disaster recovery system includes: a production environment 101, a disaster recovery environment 102, a gray environment 103 and a detection module 104, wherein:

[0043] The production environment 101 includes an APP application system 101A and a production database 101B for the APP application system to call. The production environment is used to support the business operations involved in the APP application system.

[0044] Specifically, the production environment 101 actually refers to a computing environment that has been deployed and run, and is used to host and support actual applications, services, or business operations. The production environment 101 of this embodiment is mainly used to host and support actual applications. In other words, the production environment 101 is the final destination of the application, and the developer deploys his application to this environment so that the end user can access and use it. In this environment, the developer needs to ensure the stability, performance, and security of the application.

[0045] It should be noted that the stability and performance of the production environment 101 directly affects the success of the application and user satisfaction. Any failure or interruption in the production environment 101 may lead to application loss and reputation damage. Therefore, organizations need to invest a lot of resources to ensure the high quality and security of their production environment 101.

[0046] The disaster recovery environment 102 includes a disaster recovery application system 102A equivalent to the APP application system, and a disaster recovery database 102B for the disaster recovery application system to call. The disaster recovery environment is used to take over the business related to the APP application currently running in the production environment when a failure occurs in the production environment, wherein the disaster recovery database is a backup database of the production database.

[0047] Specifically, the disaster recovery environment 102 in this embodiment is application disaster recovery, that is, a complete set of backup application environments equivalent to the local production environment is established. Compared with the data disaster recovery type, the establishment of the disaster recovery environment 102 requires not only a copy of available data, that is, a disaster recovery database 102B, but also resources including networks, hosts, applications, and even IPs, as well as good coordination between various resources, that is, a disaster recovery application system 102A. The construction of the above-mentioned disaster recovery environment 102 requires load balancing and clustering technologies.

[0048] The disaster recovery database 102B is a manifestation of data disaster recovery, that is, the disaster recovery database 102B is a usable copy of the production database 101 B. The data in the disaster recovery database 102B can be a real-time copy of the data in the production database 101B, or it can be slightly behind the data in the production database 101B.

[0049] Therefore, in order to ensure the stability and performance of the production environment 101, a disaster recovery environment 102 is introduced to ensure that the APP application used by the user can be restored within the allowed time range when a failure occurs in the production environment when the user accesses the APP application, so as to minimize the losses caused by the disaster and make the user basically unaware of the occurrence of the disaster.

[0050] The grayscale environment 103 includes a grayscale application system 103A and a grayscale database 103B for the grayscale application system to call. The grayscale environment is used to take over the business related to the APP application currently running in the production environment when the production environment fails and the application called by the user is included in the grayscale application system. The grayscale application system is a backup system obtained based on the APP application system and includes some applications of the APP application system.

[0051] It should be noted that the grayscale environment 103 can also be called an online simulation environment or a pre-release environment. When there is an update operation on the production environment 101, it is released to the grayscale environment in advance. By observing user feedback and the stability of the data in the grayscale database 103B, the update operation can be adjusted to avoid directly updating the production environment 101, causing system errors to affect user use, or users cannot adapt to the completely updated new production environment in a short time, resulting in a large number of user losses.

[0052] Because the gray environment 103 can also be called an online simulation environment or a pre-release environment, when the gray environment 103 fails, it can also be used as the target object for disaster recovery switching. The specific application scope of the APP deployed in the gray environment 103 is determined. The specific determination process is:

[0053] When receiving a business application from a user, the health of the production environment 101 is monitored through the detection module 104, and when the health is abnormal, the corresponding call type and the application called in the APP application system are obtained according to the business application, wherein the call type is an external call or an internal call,

[0054] Acquire the inclusion relationship between the application and the grayscale application system 102A, determine the disaster recovery switching environment according to the inclusion relationship, and acquire the disaster recovery switching process according to the application, wherein the disaster recovery switching process is determined according to the disaster recovery switching information included in the selection field corresponding to the application;

[0055] The corresponding gateway is obtained according to the call type, and the production environment 101 is switched to the disaster recovery switching environment through the gateway according to the disaster recovery switching process, wherein the external call corresponds to the external gateway and the internal call corresponds to the internal gateway.

[0056] The present application provides an APP application disaster recovery system, which includes a disaster recovery environment, a production environment, and a grayscale environment. The grayscale environment and the disaster recovery environment are used as the switching targets when a failure occurs in the production environment, and the business related to the APP application currently running in the production environment is taken over. Through the above method, when a failure occurs in the production environment, the disaster recovery switching is realized without perception, which does not affect the normal use of the APP application by the user. At the same time, it solves the problem that the disaster recovery system that only uses the grayscale system as the disaster recovery environment cannot solve the problem involving the application cluster.

[0057] Figure 2 This is a schematic diagram of the structure of the APP application disaster recovery system. Figure 2 .like Figure 2 As shown, the disaster recovery system further includes a gateway module 2, wherein:

[0058] The gateway module 2 includes at least one external gateway 201 and at least one internal gateway 202, wherein:

[0059] The at least one external gateway 201 is used to perform traffic switching when the APP application system 101A is externally called and the production environment 101 fails, and complete the switching between the production environment 101 and the disaster recovery environment 102, or the switching between the production environment 101 and the gray environment 103;

[0060] The at least one internal gateway 202 is used to perform proxy switching when the APP application system 101A is internally called and a failure 101 occurs in the production environment, to complete the switching between the production environment 101 and the disaster recovery environment 102, or the switching between the production environment 101 and the gray environment 103.

[0061] The internet is divided into multiple domains or autonomous systems. A domain is a set of hosts and routers that use the same routing protocol and are managed by a single organization. For example, a domain may be the Internet managed by a university or other organization. While the interior gateway protocol selects routes within a domain, the exterior gateway protocol provides a method for two adjacent routers located on the boundaries of their respective domains to exchange messages and information.

[0062] Proxy switching The principle of proxy switching is based on the distributed structure of the Internet. The Internet is composed of a large number of nodes (servers, routers, etc.), each of which has a unique address. When we access the Internet, the data packet will be transmitted through multiple nodes and finally reach the target server. Proxy switching is to modify the address of the device and send the data packet to a different address, thereby changing the access path and source address.

[0063] Figure 3This is a schematic diagram of the structure of the APP application disaster recovery system. Figure 3 This embodiment provides a detailed description of the structure of the APP application system. Figure 3 As shown, the APP application system 101A includes an application management platform 3, and the application management platform 3 is used to manage an application list consisting of multiple applications included in the APP application system 101A, and at the same time set optional fields for each application in the section to which the application list belongs, so that operation and maintenance personnel can adjust disaster recovery switching information according to the optional fields, wherein the optional fields are determined according to the type of application corresponding to the current section, and the types include: APP applications and H5 applications.

[0064] Furthermore, the application list is classified by application, and each application corresponding section contains optional fields, which are determined according to the type of application. Considering that the types of applications are mainly divided into two categories, namely, APP applications and H5 applications, there are two types of optional fields: first optional fields and second optional fields. Specifically:

[0065] A first optional field is set in the section corresponding to each APP application, wherein the first optional field includes: a disaster recovery environment increase release request address, a disaster recovery environment release root directory, and a disaster recovery environment release resource path;

[0066] A second optional field is set in the section corresponding to each H5 application, wherein the second optional field includes: a disaster recovery environment increase release request address, a disaster recovery environment release root directory, and an environment switching field.

[0067] It should be noted that the optional fields are regulated and selected by the operation and maintenance personnel. Therefore, before the APP application disaster recovery system is officially launched, the operation and maintenance personnel need to set the optional fields corresponding to each application in advance. When it is determined that disaster recovery switching is required later, disaster recovery switching is performed according to the optional fields corresponding to the currently running application. Specifically:

[0068] When a failure occurs in the production environment, the corresponding switching configuration is queried according to the environment switching field set on the panel corresponding to the currently running application. After determining to switch the production environment to the disaster recovery environment according to the corresponding switching configuration, the disaster recovery switching information is pulled according to the first optional field or the second optional field, and the environment is switched to according to the disaster recovery switching information.

[0069] Figure 4 This is a schematic diagram of the structure of the APP application disaster recovery system. Figure 4 This embodiment provides a detailed description of the structure of the grayscale environment. Figure 4 As shown, the grayscale environment 103 also includes a grayscale publishing module 4, wherein:

[0070] The grayscale publishing module 4 is used to perform the change operation on the grayscale database 103B before performing the change operation on the production database 101B, and monitor the performance and stability of the data in the grayscale database 103B after the change operation, so that the operation and maintenance personnel can adjust and optimize the change operation.

[0071] Among them, the grayscale environment 103 can also be called an online simulation environment or a pre-release environment. Before the change operation on the production environment 101 is implemented, that is, before the new version of the production environment 101 after the change operation is processed goes online, it is released to the grayscale environment 103.

[0072] Furthermore, based on the monitoring of the grayscale environment 103, user feedback can be observed and the product direction can be adjusted immediately to avoid the loss of users due to users not being able to adapt to the new system in a short period of time due to direct launch. In addition, it helps to reduce the cost of launch, such as labor costs and the number of bugs. If problems with the grayscale environment are found, users can be removed from the grayscale list in a timely manner to minimize user losses.

[0073] Specifically, the grayscale release module 4 also includes a change component 401, a monitoring and analysis component 402, and a troubleshooting component 403, wherein:

[0074] The change component 401 is used to perform the change operation on the target server according to the gray release schedule, wherein the gray release schedule is predetermined and stored by the operation and maintenance personnel, and is used to indicate the time of performing the change operation on the gray database, the target server of each change, and the success index;

[0075] The monitoring and analysis component 402 is used to monitor the grayscale database after the change operation, and analyze the change operation according to the monitoring result, the grayscale release schedule and the received feedback information, wherein the feedback information is used to indicate the evaluation of the user corresponding to the target server on the change operation;

[0076] The troubleshooting component 403 is used to send operation prompt information to the change component according to the analysis result, wherein the operation prompt information is used to instruct the change component 401 to perform an expansion operation or a rollback operation.

[0077] Furthermore, after performing a change operation on the grayscale database and receiving the operation prompt information returned by the troubleshooting team 403, in order to ensure the effect of the change operation, that is, not affecting the user experience after the production environment 101 goes online, it is necessary to perform an expansion operation or a rollback operation according to the specific operation prompt information, specifically:

[0078] Control the grayscale database after the change operation to roll back to the most recently backed up version, or obtain a new target server according to the grayscale release schedule, and perform the change operation on the new target server.

[0079] At the same time, considering that it may be necessary to control the grayscale database to roll back to the most recently backed up version, it is necessary to back up and store the current version of the grayscale database before performing changes to the grayscale database.

[0080] It should be understood that the above-mentioned device embodiments are only illustrative, and the device of the present application can also be implemented in other ways. For example, the division of units / modules in the above-mentioned embodiments is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units, modules or components can be combined, or can be integrated into another system, or some features can be ignored or not executed.

[0081] In addition, unless otherwise specified, each functional unit / module in each embodiment of the present application may be integrated into one unit / module, each unit / module may exist physically separately, or two or more units / modules may be integrated together. The above-mentioned integrated unit / module may be implemented in the form of hardware or in the form of a software program module.

[0082] If the integrated unit / module is implemented in the form of hardware, the hardware may be a digital circuit, an analog circuit, etc. The physical implementation of the hardware structure includes but is not limited to transistors, memristors, etc. If not specifically stated, the processor may be any appropriate hardware processor, such as a CPU, a GPU, an FPGA, a DSP, an ASIC, etc. If not specifically stated, the storage unit may be any appropriate magnetic storage medium or magneto-optical storage medium, such as a resistive random access memory RRAM (Resistive Random Access Memory), a dynamic random access memory DRAM (Dynamic Random Access Memory), a static random access memory SRAM (Static Random-Access Memory), an enhanced dynamic random access memory EDRAM (Enhanced Dynamic Random Access Memory), a high-bandwidth memory HBM (High-Bandwidth Memory), a hybrid memory cube HMC (Hybrid Memory Cube), etc.

[0083] If the integrated unit / module is implemented in the form of a software program module and sold or used as an independent product, it can be stored in a computer-readable memory. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a memory and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0084] In the above embodiments, the description of each embodiment has its own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant description of other embodiments. The technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0085] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0086] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. An APP application disaster recovery system, characterized in that: The disaster recovery system includes: a production environment, a disaster recovery environment and a grayscale environment, wherein: The production environment includes an APP application system and a production database for the APP application system to call, and the production environment is used to support the business operations involved in the APP application system; The disaster recovery environment includes a disaster recovery application system equivalent to the APP application system, and a disaster recovery database for the disaster recovery application system to call. The disaster recovery environment is used to take over the business involved in the APP application currently running in the production environment when a failure occurs in the production environment, wherein the disaster recovery database is a backup database of the production database; The grayscale environment includes a grayscale application system and a grayscale database for the grayscale application system to call. The grayscale environment is used to take over the business related to the APP application currently running in the production environment when the production environment fails and the application called by the user is included in the grayscale application system. The grayscale application system is a backup system obtained based on the APP application system and includes some applications of the APP application system.

2. The system according to claim 1, characterized in that The disaster recovery system also includes a gateway module, wherein: The gateway module is used to complete the switching between the production environment and the disaster recovery environment, or the switching between the production environment and the grayscale environment.

3. The system according to claim 2, characterized in that The gateway module comprises at least one external gateway and at least one internal gateway, wherein: The at least one external gateway is used to perform traffic switching when the APP application system is called externally and a failure occurs in the production environment, so as to complete the switching between the production environment and the disaster recovery environment, or the switching between the production environment and the grayscale environment; The at least one internal gateway is used to perform proxy switching when the APP application system is called internally and a failure occurs in the production environment, so as to complete the switching between the production environment and the disaster recovery environment, or the switching between the production environment and the grayscale environment.

4. The system according to claim 3, characterized in that The APP application system includes an application management platform, which is used to manage an application list consisting of multiple applications included in the APP application system, and at the same time set optional fields for each application in the section to which the application list belongs, so that operation and maintenance personnel can adjust disaster recovery switching information according to the optional fields, wherein the optional fields are determined according to the type of application corresponding to the current section, and the types include: APP applications and H5 applications.

5. The system according to claim 4, characterized in that The application management platform is specifically used to set a first optional field in a section corresponding to each APP application, wherein the first optional field includes: a disaster recovery environment to increase a release request address, a disaster recovery environment release root directory, and a disaster recovery environment release resource path; A second optional field is set in the section corresponding to each H5 application, wherein the second optional field includes: a disaster recovery environment increase release request address, a disaster recovery environment release root directory, and an environment switching field.

6. The system according to claim 5, characterized in that The application management platform is also used to, when a failure occurs in the production environment, query the corresponding switching configuration based on the environment switching field set on the board corresponding to the currently running application, and after determining to switch the production environment to the disaster recovery environment based on the corresponding switching configuration, pull the disaster recovery switching information based on the first optional field or the second optional field, and switch to the disaster recovery environment based on the disaster recovery switching information.

7. The system according to claim 6, characterized in that The grayscale environment also includes a grayscale publishing module, wherein: The grayscale release module is used to perform the change operation on the grayscale database before performing the change operation on the production database, and monitor the performance and stability of the data in the grayscale database after the change operation, so that the operation and maintenance personnel can adjust and optimize the change operation.

8. The system according to claim 7, characterized in that The grayscale release module includes: a change component, a monitoring and analysis component, and a troubleshooting component, wherein: The change component is used to perform the change operation on the target server according to the gray release schedule, wherein the gray release schedule is predetermined and stored by the operation and maintenance personnel and is used to indicate the time for performing the change operation on the gray database, the target server for each change, and the success indicator; The monitoring and analysis component is used to monitor the grayscale database after the change operation, and analyze the change operation according to the monitoring result, the grayscale release schedule and the received feedback information, wherein the feedback information is used to indicate the evaluation of the user corresponding to the target server on the change operation; The troubleshooting component is used to send operation prompt information to the change component according to the analysis result, wherein the operation prompt information is used to instruct the change component to perform an expansion operation or a rollback operation.

9. The system according to claim 8, characterized in that The change component is specifically used to back up and store the current version of the grayscale database before performing the change operation, and after receiving the operation prompt information, control the grayscale database after the change operation to roll back to the most recently backed up version; Or, a new target server is obtained according to the grayscale release schedule, and the change operation is performed on the new target server.

10. The system according to claim 9, characterized in that The disaster recovery system also includes a detection module, wherein: The detection module is used to: when receiving a business application from a user, monitor the health of the production environment, and when the health is abnormal, obtain the corresponding call type and the application called in the APP application system according to the business application, wherein the call type is an external call or an internal call, Acquire the inclusion relationship between the application and the grayscale application system, determine the disaster recovery switching environment according to the inclusion relationship, and acquire the disaster recovery switching process according to the application, wherein the disaster recovery switching process is determined according to the disaster recovery switching information contained in the selection field corresponding to the application; A corresponding gateway is obtained according to the call type, and the production environment is switched to the disaster recovery switching environment through the gateway according to the disaster recovery switching process, wherein an external call corresponds to an external gateway and an internal call corresponds to an internal gateway.

Images