WO2020259086A1 - Distributed architecture - Google Patents
Distributed architecture Download PDFInfo
- Publication number
- WO2020259086A1 WO2020259086A1 PCT/CN2020/088833 CN2020088833W WO2020259086A1 WO 2020259086 A1 WO2020259086 A1 WO 2020259086A1 CN 2020088833 W CN2020088833 W CN 2020088833W WO 2020259086 A1 WO2020259086 A1 WO 2020259086A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data center
- nodes
- data
- distributed architecture
- node
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Definitions
- the embodiment of the present invention relates to the field of financial technology (Fintech), in particular to a distributed architecture.
- the common distributed architecture mainly adopts the centralized loosely coupled architecture.
- the centralized loosely coupled architecture because the customer's business is highly interdependent, according to the barrel principle, the availability and performance of the entire architecture depends on the shortest node, so , The performance of each node can only solve the processing performance of its own application and cannot realize the sharing of system load and resources between nodes.
- the current network technology cannot guarantee the absolute stability and availability of long-distance communication quality.
- the centralized loosely coupled architecture may cause customer data to be inaccessible, and there is a risk of failure.
- the embodiment of the present invention provides a distributed architecture to ensure the overall availability and scalability of the architecture, and reduce the scope of the failure risk.
- a distributed architecture provided by an embodiment of the present invention includes: N data centers and M groups of data center nodes;
- Each data center includes X data center nodes, each group of data center nodes includes Y data center nodes, and Y data center nodes in each group of data center nodes are located in Y different data centers; each data center node includes A database server storing customer data of Z customers and/or an application server storing an application system that processes all services of the Z customers;
- the database server storing the customer data of each customer and/or the application server storing the application system processing all the services of the Z customers are stored in one data center node, and at least Q pieces of data in the N data centers The centers are located in different cities, the Y data center nodes in each group of data center nodes include one master data center node and at least two slave data center nodes, and N, M, X, Y, Z, and Q are positive integers.
- each data center node since the data center nodes included in each data center of the distributed architecture are divided into groups based on the customer dimension, each data center node has an independent business processing application system and/or stores customers Data can maintain high availability even when a data center node fails in a distributed architecture, disperse the processing pressure and failure risk of a single data center, effectively reduce the scope of the failure, and all Y different data centers store customer data And/or application system, it also realizes that customer data is more active and/or application is more active, even if there is a failure, it can seamlessly provide services, reducing the scope of the risk of failure.
- the Y data center nodes in each group of data center nodes include one primary data center node, at least one secondary data center node in the same city as the primary data center node, and at least one secondary data center node that is connected to the primary data center node.
- the central node is a remote slave data center node.
- the customer data of the Z customers stored in the master data center node and the slave data center node are the same, and/or the stored application systems that process all the services of the Z customers are the same.
- the physical resources among the Y data center nodes are isolated from each other.
- the Y data center nodes preset one data center node for grayscale publishing.
- the physical resources in each data center node include multiple database servers and multiple application servers;
- the application systems are grouped according to different application domains, and different groups do not share application servers and do not share database servers.
- the distributed architecture is horizontally expanded by increasing the number of data center nodes in each group of data center nodes.
- the distributed architecture is vertically expanded by increasing the computing resources of the preset data center nodes in each group of data center nodes; or by temporarily allocating the computing resources in the reserved computing resource pool to The preset data center nodes in each group of data center nodes perform vertical expansion of the distributed architecture.
- the distributed architecture further includes a global positioning system
- the global positioning system uses a preset weighted random algorithm to manage the fragmentation strategy of the customer, and locate the data center node where the customer data is stored.
- the global positioning system communicates with application systems in each data center node through a message bus.
- FIG. 1 is a schematic structural diagram of a distributed architecture provided by an embodiment of the present invention
- FIG. 2 is a schematic structural diagram of a distributed architecture provided by an embodiment of the present invention.
- FIG. 3 is a schematic diagram of a data center node provided by an embodiment of the present invention.
- Fig. 4 is a schematic diagram of a global positioning system provided by an embodiment of the present invention.
- FIG. 1 exemplarily shows a schematic structural diagram of a distributed architecture provided by an embodiment of the present invention.
- the distributed architecture may include N data centers (Internet Data Center, IDC) and M groups of data Data Center Node (DCN).
- IDC Internet Data Center
- DCN Data Center Node
- the data center (Internet Data Center, IDC) is a physical unit for the planning and management of a new generation of Internet architecture in the financial field. It has network throughput capabilities and security protection capabilities.
- the data center can be selected according to the location
- the modules constitute the physical architecture of the data center.
- the standardization of each module includes its network architecture, physical deployment, hardware equipment models, etc., but does not include its capacity; the capacity of the module can be expanded horizontally as needed.
- the data center node is the logical unit of planning and management of the new generation Internet architecture in the financial field.
- Each data center node is a node with independent physical resources and self-contained application logic, used to carry a specific customer group or provide a set of specific services.
- Data center nodes have independent physical computing and storage resources. Different nodes do not share physical computing and storage resources. Different nodes share data center-level resources, mainly including: data center infrastructure, basic network, and data center level Public services (for example: message bus, etc.).
- data center nodes can be divided into two types of services according to different service objects: one is customer service: the external services provided by the bank to various types of bank customers; the other is the bank Back-end management services: internal services used by the bank itself, such as general ledger, management accounting, etc.
- each data center includes X data center nodes, each group of data center nodes includes Y data center nodes, and Y data center nodes in each group of data center nodes are located at Y Different data centers; each data center node includes a database server for storing customer data of Z customers and/or an application server for storing application systems for processing all services of Z customers.
- the database server that stores the customer data of each customer and/or the application server that stores the application systems that process all the services of the Z customers are stored in one data center node, and at least Q of the N data centers are located in different cities .
- the Y data center nodes in each group of data center nodes include one master data center node and at least two slave data center nodes, and N, M, X, Y, Z, and Q are positive integers.
- the customer data of Z customers stored in the main data center node and the slave data center node are the same as the application system that processes all the services of the Z customers.
- the number of data centers in the same city can be selected as multiple (for example, N or less than N).
- N the number of data centers in the same city
- the number of Y is less than N.
- each group of data center nodes only needs to include Y data center nodes. It is not necessary for each group of data center nodes to contain N data center nodes.
- a backup data center node provides services, which can prevent excessive consumption of resources.
- N data centers such as 5
- M groups of data center nodes DCN
- DCN group 1 can optionally include three DCNs, one of which is located in IDC1 Among them, one is located in IDC2, and the other is located in IDC3.
- the DCNs in IDC1 and IDC2 each contain a database server that stores customer data and an application server that stores application systems that process all customer business.
- IDC3 only contains storage The database server of customer data, in this way, the number of data center nodes in each group of data center nodes is less than the number of data centers, which can ensure that there is a backup data center node when a data center node fails Providing services can also prevent excessive consumption of resources.
- IDC3 can also deploy an application server.
- a data center node includes a database server and/or an application server, and the database server and the application server are independent of each other on two different levels and do not respond to each other.
- multi-instance and active deployment of application systems can be realized. Even if the application system in a certain DCN fails, it can be provided by other DCN application systems. Services can ensure business continuity in various disaster recovery scenarios. In the existing distributed architecture, when a certain application system fails, the backup application system can only be manually started manually, which requires a long waiting time, and the obvious failure has a large impact range.
- each data center node has an independent application system for processing all customer services.
- the application system takes over the processing, and there is no need to set up the main and standby application systems in a data center node, saving the resources of the data center node.
- At least Q data centers of N data centers are located in different cities.
- the distributed architecture as shown in FIG. 2 there are three data centers in total, of which there are two data centers in the same city and one data center for remote disaster recovery.
- This kind of architecture can be called a "two places and three centers" deployment architecture.
- a single data center from power supply, cooling to network connectivity is designed according to the minimum 2N level of redundancy, and requires all lines to be physically Isolation to ensure that a construction site does not have a fatal impact on the connectivity of a single data center. Therefore, when any data center in the same city fails, the architecture can support the switch between data centers in the same city.
- each group of data center nodes include a primary data center node, at least one secondary data center node in the same city as the primary data center node, and at least one secondary data center node that is remote from the primary data center node .
- each data center is composed of multiple data center nodes.
- Each group of data center nodes is composed of a master node, a backup node in the same city, and a disaster recovery node in a remote location.
- each group of data center nodes also independently form a "two places and three centers" structure to ensure that the main node fails It can quickly switch to the standby node and support uninterrupted business operation to meet RTO (Recovery Time Object, Recovery Time Object) and RPO (Recovery Point Object, Recovery Point Object) related requirements.
- RTO Recovery Time Object
- RPO Recovery Point Object, Recovery Point Object
- Two data center nodes can be located in the same city, and the other data center node can be located in a remote city, so that each group of data center nodes can also be formed independently.
- the "two locations and three centers" structure can disperse the processing pressure of a single data center and save system overhead.
- a single data center node its physical resources include multiple database servers and multiple application servers.
- Application systems are grouped according to different application domains, and different groups do not share application servers and do not share database servers.
- the physical resources between data center nodes are isolated from each other.
- data center nodes can be analyzed from the composed hardware resources and deployed data and application systems.
- a data center node contains hardware resources such as application servers and database servers.
- the relevant hardware resources of a data center node are deployed in a centralized manner, fixed by 2 application server cabinets and 3 database server cabinets constitute.
- Each SET (data set) is composed of three SET nodes, and the three SET nodes are scattered on three database server cabinets.
- the corresponding data is stored in three copies, and the three data are distributed in three different cabinets.
- Such a database deployment structure can fully guarantee the high availability of data.
- operation and maintenance management tools such as configuration information management
- banks have become more mature in the management of data center nodes, and can read and filter all resource information related to a data center node from the operation and maintenance management tools at any time and quickly.
- data center nodes are also facing certain expansion requirements.
- the current data center nodes are no longer limited to centralized cabinets, but are more open and transformed into logical regional divisions.
- the data center becomes a huge resource pool.
- a data center can be integrated at any time according to actual construction needs. Any server joining or moving out of a data center node can quickly realize the elastic expansion and shrinkage of data center nodes.
- Each group of data center nodes can preset a data center node for grayscale release. Through the distributed architecture with customers as the unit, the weight of customer allocation of one of the nodes can be reduced, so that this node has exactly the same application architecture, deployment architecture and resource configuration as all other nodes, but lower than the customer load of other nodes .
- the distributed architecture with customers as the unit through the isolation of each customer node, through standardized node deployment and the control of customer distribution weights, can easily achieve true and effective grayscale verification, thereby greatly improving the application release cycle. Reduce the dependence on the test process, through the gray production flow, directly completed the last test link of software and hardware update in the production environment.
- the distributed architecture has two expansion methods, specifically:
- the bank’s customer service capacity can be increased by rapidly deploying corresponding types of standard data center nodes; in the vertical expansion strategy, we have two different modes: one is permanent expansion, the other is Temporary expansion.
- Permanent expansion refers to vertical expansion and upgrade by increasing the computing resources of logical nodes. For example, a module was originally scheduled to serve 5 million customers. With the continuous development of business and the continuous launch of new products, while serving 5 million customers unchanged, multiple nodes generally have performance bottlenecks. Then, at this time, computing resources will be added to these nodes according to certain strategies, and the processing capabilities of the nodes will be permanently improved.
- the distributed architecture also includes a global positioning system, which uses a preset weighted random algorithm to manage fragmentation strategies for customers and locate data center nodes where customer data is stored.
- the global positioning system uses a weighted random algorithm to determine which data center node to store the new customer's data when creating a new customer, and in the subsequent business processing of the new customer, through a fragmented information retrieval mechanism based on customer information To locate the data center node where customer data needed for business processing is stored, that is, use the global positioning system for customer segmentation management and customer positioning.
- the customer data storage nodes are allocated through the global positioning system, and the weighted random algorithm is used to implement in a distributed architecture.
- the weighted random algorithm is used to implement in a distributed architecture.
- the global positioning system communicates with the application systems in each data center node through the message bus.
- the biggest difference between the above model and the model adopted by traditional banks is the introduction of the dimension of data center nodes, which splits a data center into multiple data center nodes.
- the biggest challenge brought by this difference is how to effectively solve the communication problem between systems, that is, an application subsystem will be distributed on multiple data center nodes at the same time, how does the upstream caller know which data center to visit?
- the downstream subsystem of the node To solve this problem, it is impossible to make a lot of changes to all applications to adapt to this architecture. The best way is to converge and solve the problem.
- the message bus is a design scheme that has been proposed for a long time, and the communication between various application subsystems can be converged through the message bus. But just using the message bus is not enough.
- the embodiment of the present invention introduces a global positioning system that provides uniform customer and service addressing functions across the bank, and returns the data center node number where the customer is located based on the customer identification information such as the customer number, card number, or account number entered. This makes it possible to obtain the data center node where the callee is located when calling between systems, and inform the upstream subsystem of which data center node's downstream subsystem to visit through the standard interface provided by the global positioning system.
- the embodiment of the present invention not only realizes the overall architecture of “two places and multiple centers”, but also achieves specific results in the following three aspects: Distribute applications to multiple data center nodes through the design In the homogeneous BOX, the flexible expansion and shrinkage capabilities of a single data center node are realized; the multi-instance multi-active deployment of applications is realized, and the "two-place multi-center" solution is combined to ensure business in various disaster recovery scenarios Continuity: Through the message bus and the global positioning system, the communication problem between systems is solved, and the impact of the change of the architecture on the application is minimized.
- the embodiment of the present invention shows that the distributed architecture includes: N data centers and M groups of data center nodes.
- Each data center includes X data center nodes, each group of data center nodes includes Y data center nodes, and Y data center nodes in each group of data center nodes are located in Y different data centers; each data center node is used for Including a database server that stores customer data of Z customers and/or an application server that stores application systems that process all services of Z customers; among them, a database server that stores customer data of each customer and/or stores and processes the Z customers
- the application servers of all business application systems are stored in one data center node, at least Q data centers in the N data centers are located in different cities, and the Y data center nodes in each group of data center nodes include a master For the data center node and at least two slave data center nodes, N, M, X, Y, Z, and Q are positive integers.
- each data center node Since the data center nodes included in each data center of the distributed architecture are based on the customer dimension and divided into groups, each data center node has an independent business processing application system, which can realize the data center nodes in the distributed architecture In the event of a failure, it still maintains high availability, disperses the processing pressure and failure risk of a single data center, and effectively reduces the scope of the failure. Moreover, Y different data centers store customer data and/or application systems, and customer data is also realized Multi-activity and/or application multi-activity can seamlessly provide services even if there is a failure, reducing the scope of the risk of failure.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims (10)
- 一种分布式架构,其特征在于,包括:N个数据中心和M组数据中心节点;A distributed architecture, which is characterized by comprising: N data centers and M groups of data center nodes;每个数据中心包括X个数据中心节点,每组数据中心节点包括Y个数据中心节点,每组数据中心节点中的Y个数据中心节点位于Y个不同的数据中心;每个数据中心节点包括用于存放Z个客户的客户数据的数据库服务器和/或存放处理所述Z个客户所有业务的应用系统的应用服务器;Each data center includes X data center nodes, each group of data center nodes includes Y data center nodes, and Y data center nodes in each group of data center nodes are located in Y different data centers; each data center node includes A database server storing customer data of Z customers and/or an application server storing an application system that processes all services of the Z customers;其中,存放每个客户的客户数据的数据库服务器和/或存放处理所述Z个客户所有业务的应用系统的应用服务器都存放于一个数据中心节点中,所述N个数据中心中至少Q个数据中心位于不同城市,所述每组数据中心节点中的Y个数据中心节点包括一个主数据中心节点和至少两个从数据中心节点,N、M、X、Y、Z、Q为正整数。Wherein, the database server storing the customer data of each customer and/or the application server storing the application system processing all the services of the Z customers are stored in one data center node, and at least Q pieces of data in the N data centers The centers are located in different cities, the Y data center nodes in each group of data center nodes include one master data center node and at least two slave data center nodes, and N, M, X, Y, Z, and Q are positive integers.
- 如权利要求1所述的分布式架构,其特征在于,所述每组数据中心节点中的Y个数据中心节点包括一个所述主数据中心节点,至少一个与所述主数据中心节点同城的从数据中心节点和至少一个与所述主数据中心节点异地的从数据中心节点。The distributed architecture of claim 1, wherein the Y data center nodes in each group of data center nodes include one master data center node, and at least one slave data center node in the same city as the master data center node A data center node and at least one slave data center node remote from the master data center node.
- 如权利要求1所述的分布式架构,其特征在于,所述主数据中心节点和从数据中心节点中存放的Z个客户的客户数据相同,和/或存放的处理所述Z个客户所有业务的应用系统相同。The distributed architecture of claim 1, wherein the customer data of the Z customers stored in the master data center node and the slave data center node are the same, and/or the stored processing of all the services of the Z customers The application system is the same.
- 如权利要求1所述的分布式架构,其特征在于,所述Y个数据中心节点之间的物理资源相互隔离。The distributed architecture of claim 1, wherein the physical resources among the Y data center nodes are isolated from each other.
- 如权利要求4所述的分布式架构,其特征在于,所述Y个数据中心节点预设一个数据中心节点进行灰度发布。The distributed architecture according to claim 4, wherein the Y data center nodes preset one data center node for grayscale publishing.
- 如权利要求1所述的分布式架构,其特征在于,每个数据中心节点中的物理资源包括多个数据库服务器和多个应用服务器;The distributed architecture according to claim 1, wherein the physical resources in each data center node include multiple database servers and multiple application servers;所述应用系统按照不同的应用域进行分组,不同的组不共享应用服务器 以及不共享数据库服务器。The application systems are grouped according to different application domains, and different groups do not share application servers and do not share database servers.
- 如权利要求1至6任一项所述的分布式架构,其特征在于,通过增加所述每组数据中心节点中的数据中心节点的数量,对所述分布式架构进行横向扩容。The distributed architecture according to any one of claims 1 to 6, wherein the distributed architecture is horizontally expanded by increasing the number of data center nodes in each group of data center nodes.
- 如权利要求1至6任一项所述的分布式架构,其特征在于,通过增加所述每组数据中心节点中的预设数据中心节点的计算资源,对所述分布式架构进行纵向扩容;或通过将预留的计算资源池中的计算资源临时分配给所述每组数据中心节点中的预设数据中心节点,对所述分布式架构进行纵向扩容。The distributed architecture according to any one of claims 1 to 6, wherein the distributed architecture is vertically expanded by increasing the computing resources of a preset data center node in each group of data center nodes; Or by temporarily allocating the computing resources in the reserved computing resource pool to preset data center nodes in each group of data center nodes, the distributed architecture is vertically expanded.
- 如权利要求1至6任一项所述的分布式架构,其特征在于,所述分布式架构还包括全局定位系统;The distributed architecture according to any one of claims 1 to 6, wherein the distributed architecture further includes a global positioning system;所述全局定位系统采用预设的加权随机算法对所述客户进行分片策略管理,和对所述客户数据存放的数据中心节点进行定位。The global positioning system adopts a preset weighted random algorithm to manage the fragmentation strategy of the customer, and locates the data center node where the customer data is stored.
- 如权利要求9所述的分布式架构,其特征在于,所述全局定位系统通过消息总线分别与每个数据中心节点中的应用系统进行通信。9. The distributed architecture of claim 9, wherein the global positioning system communicates with application systems in each data center node through a message bus.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201910553289.2A CN110225138B (en) | 2019-06-25 | 2019-06-25 | Distributed architecture |
CN201910553289.2 | 2019-06-25 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020259086A1 true WO2020259086A1 (en) | 2020-12-30 |
Family
ID=67814748
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/088833 WO2020259086A1 (en) | 2019-06-25 | 2020-05-06 | Distributed architecture |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN110225138B (en) |
WO (1) | WO2020259086A1 (en) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110225138B (en) * | 2019-06-25 | 2021-12-14 | 深圳前海微众银行股份有限公司 | Distributed architecture |
CN110990200B (en) * | 2019-11-26 | 2022-07-05 | 苏宁云计算有限公司 | Flow switching method and device based on multiple active data centers |
CN112698839B (en) * | 2020-12-30 | 2024-04-12 | 深圳前海微众银行股份有限公司 | Data center node deployment method, device and system and computer storage medium |
CN113961400B (en) * | 2021-12-21 | 2022-03-08 | 唐山启奥科技股份有限公司 | Blood disaster tolerance and emergency management system and method |
CN117453150B (en) * | 2023-12-25 | 2024-04-05 | 杭州阿启视科技有限公司 | Method for implementing multiple instances of video storage scheduling service |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020194015A1 (en) * | 2001-05-29 | 2002-12-19 | Incepto Ltd. | Distributed database clustering using asynchronous transactional replication |
CN105681401A (en) * | 2015-12-31 | 2016-06-15 | 深圳前海微众银行股份有限公司 | Distributed architecture |
CN105763386A (en) * | 2016-05-13 | 2016-07-13 | 中国工商银行股份有限公司 | Service processing system and method |
CN107038192A (en) * | 2016-11-17 | 2017-08-11 | 阿里巴巴集团控股有限公司 | database disaster recovery method and device |
CN107391294A (en) * | 2017-07-28 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of method for building up and device of IPSAN disaster tolerance systems |
CN109819004A (en) * | 2017-11-22 | 2019-05-28 | 中国人寿保险股份有限公司 | For disposing the method and system at more live data centers |
CN110225138A (en) * | 2019-06-25 | 2019-09-10 | 深圳前海微众银行股份有限公司 | A kind of distributed structure/architecture |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9756184B2 (en) * | 2012-11-08 | 2017-09-05 | Genesys Telecommunications Laboratories, Inc. | System and method of distributed maintenance of contact center state |
CN104717186B (en) * | 2013-12-16 | 2019-06-25 | 腾讯科技(深圳)有限公司 | A kind of method, apparatus and data transmission system for transmitting data in network system |
CN105554126A (en) * | 2015-12-22 | 2016-05-04 | 内蒙古农业大学 | Method for realizing distributed deployment of multiple data centers through CDN acceleration mechanism |
CN105577675A (en) * | 2015-12-31 | 2016-05-11 | 深圳前海微众银行股份有限公司 | Multi-tenant resource management method and device |
CN107193546B (en) * | 2017-04-11 | 2021-05-04 | 国网天津市电力公司信息通信公司 | Micro-service business application system |
CN107454171B (en) * | 2017-08-10 | 2021-04-30 | 深圳前海微众银行股份有限公司 | Message service system and implementation method thereof |
CN108989456B (en) * | 2018-08-11 | 2019-06-25 | 广东易积网络股份有限公司 | A kind of network implementation approach based on big data |
CN208820800U (en) * | 2018-09-25 | 2019-05-03 | 国家电网有限公司客户服务中心 | A kind of 95598 strange land dual-active systems standby based on core business calamity |
CN109447876A (en) * | 2018-10-16 | 2019-03-08 | 湖北三峡云计算中心有限责任公司 | A kind of burgher card system |
CN109542659A (en) * | 2018-11-14 | 2019-03-29 | 深圳前海微众银行股份有限公司 | Using more activating methods, equipment, data center's cluster and readable storage medium storing program for executing |
-
2019
- 2019-06-25 CN CN201910553289.2A patent/CN110225138B/en active Active
-
2020
- 2020-05-06 WO PCT/CN2020/088833 patent/WO2020259086A1/en active Application Filing
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020194015A1 (en) * | 2001-05-29 | 2002-12-19 | Incepto Ltd. | Distributed database clustering using asynchronous transactional replication |
CN105681401A (en) * | 2015-12-31 | 2016-06-15 | 深圳前海微众银行股份有限公司 | Distributed architecture |
CN105763386A (en) * | 2016-05-13 | 2016-07-13 | 中国工商银行股份有限公司 | Service processing system and method |
CN107038192A (en) * | 2016-11-17 | 2017-08-11 | 阿里巴巴集团控股有限公司 | database disaster recovery method and device |
CN107391294A (en) * | 2017-07-28 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of method for building up and device of IPSAN disaster tolerance systems |
CN109819004A (en) * | 2017-11-22 | 2019-05-28 | 中国人寿保险股份有限公司 | For disposing the method and system at more live data centers |
CN110225138A (en) * | 2019-06-25 | 2019-09-10 | 深圳前海微众银行股份有限公司 | A kind of distributed structure/architecture |
Also Published As
Publication number | Publication date |
---|---|
CN110225138B (en) | 2021-12-14 |
CN110225138A (en) | 2019-09-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020259086A1 (en) | Distributed architecture | |
JP5102901B2 (en) | Method and system for maintaining data integrity between multiple data servers across a data center | |
CN107707393A (en) | More live systems based on Openstack O version characteristics | |
CN204859222U (en) | With two high available systems that live of city data center | |
US20090187668A1 (en) | Protocol Independent Server Replacement and Replication in a Storage Area Network | |
CN102938705B (en) | Method for managing and switching high availability multi-machine backup routing table | |
CN101227315A (en) | Dynamic state server colony and control method thereof | |
CN105930498A (en) | Distributed database management method and system | |
CN103226518A (en) | Method and device for performing volume expansion in storage management system | |
CN107273440A (en) | Computer application, date storage method, micro services and microdata storehouse | |
CN109819004A (en) | For disposing the method and system at more live data centers | |
CN110727709A (en) | Cluster database system | |
CN109739640A (en) | A kind of container resource management system based on Shen prestige framework | |
CN110535924A (en) | A kind of rail traffic server communications method and system | |
CN114301972A (en) | Block chain link point hierarchical deployment method and system based on cloud edge cooperation | |
CN108810150A (en) | The data copy method of cooperative office system application layer disaster recovery and backup systems | |
CN107135097A (en) | The disaster tolerance system and disaster recovery method filed based on bookkeeping | |
CN108964986A (en) | Cooperative office system application layer dual-active disaster recovery and backup systems | |
CN105872024A (en) | Disaster recovery device, system and method | |
CN109361777A (en) | Synchronous method, synchronization system and the relevant apparatus of distributed type assemblies node state | |
CN111800484A (en) | Service anti-destruction replacing method for mobile edge information service system | |
CN105681401A (en) | Distributed architecture | |
CN107577564A (en) | A kind of method that dual-active system is realized based on block simultaneous techniques | |
WO2021129038A1 (en) | Water resource management system service clustering framework construction method | |
CN113779143A (en) | Double-activity data center and business system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20831503 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20831503 Country of ref document: EP Kind code of ref document: A1 |
|
32PN | Ep: public notification in the ep bulletin as address of the adressee cannot be established |
Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 05/04/2022) |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20831503 Country of ref document: EP Kind code of ref document: A1 |