Partition-based application disaster recovery system

Abstract

The invention discloses a partition-based application disaster tolerance system. The system comprises a product business layer, a middle platform service layer and a global support layer, wherein eachof the product business layer and the middle platform service layer comprises at least one business exclusive partition, a plurality of partitions of each business exclusive partition comprise a first partition and a second partition which are backed up mutually, and the global support layer is used for providing auxiliary support; the product business layer, the middle station service layer andthe global support layer perform business isolation and layering through partition middleware. By means of the technical scheme, resource isolation can be achieved, the fault influence range is narrowed, the positioning problem is clear, resource allocation is accurate, and elastic telescoping is convenient.

Description

technical field [0001] The invention relates to the technical field of the Internet, in particular to a partition-based application disaster recovery system. Background technique [0002] Payment is the basic support for the development of all walks of life on the Internet. At present, the requirements for high availability of payment are getting higher and higher, and even everyone gradually forgets that payment is not available. However, as a third-party payment company that provides water, electricity and gas for payment, the requirements for payment scenarios are even more stringent. The business needs to run 24 hours a day in any environment, and the data cannot be discarded or confused. Therefore, as a microservice framework that supports all businesses of the company, how to implement deep isolation and disaster recovery methods for applications has become particularly important. [0003] In the current mainstream application micro-service application framework, serv...

AI Technical Summary

Problems solved by technology

[0006] It is impossible to realize automatic routing through simple operation and maintenance configuration, and a large number of routing identifiers need to be marked in specific tags, and developers need to write a lot of extra code and configuration; dynamic routing cannot be performed; multiple applications cannot be integrated together for overall business integration Isolation; it is impossible to perform simple isolation as a whole; it cannot handle the delivery of services relying on middle and lower-level business routes, and maintain effective tracking; it cannot perform disaster recovery as a whole and quickly keep services available

[0007] The above defects will lead to business failures when the business is performing daily releases, gray scale releases, and disaster recovery switching, which will affect the high availability of the business.

Images