CN113157813A - Synchronous node device for realizing bidirectional synchronization of database - Google Patents
Synchronous node device for realizing bidirectional synchronization of database Download PDFInfo
- Publication number
- CN113157813A CN113157813A CN202110581382.1A CN202110581382A CN113157813A CN 113157813 A CN113157813 A CN 113157813A CN 202110581382 A CN202110581382 A CN 202110581382A CN 113157813 A CN113157813 A CN 113157813A
- Authority
- CN
- China
- Prior art keywords
- database
- incremental data
- synchronization
- opposite
- bidirectional
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000002457 bidirectional effect Effects 0.000 title claims abstract description 71
- 230000001360 synchronised effect Effects 0.000 title claims abstract description 57
- 238000000034 method Methods 0.000 claims description 8
- 238000013459 approach Methods 0.000 description 3
- 238000012217 deletion Methods 0.000 description 3
- 230000037430 deletion Effects 0.000 description 3
- 238000007792 addition Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000003780 insertion Methods 0.000 description 2
- 230000037431 insertion Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
Abstract
The invention discloses a synchronous node device for realizing bidirectional synchronization of a database, which belongs to the technical field of bidirectional synchronization of the database and aims to solve the technical problem of how to achieve bidirectional synchronization of the database without changing the databases of both parties and manually submitting incremental data transactions and avoid endless loop. The structure includes: the cloud message service node CMSP is used for caching and sending incremental data of the opposite-end database; the bidirectional synchronous warehousing module is used for storing the incremental data of the opposite-end database into the local-end database; the incremental data log module is used for recording the incremental data of the opposite-end database; and the bidirectional synchronous acquisition module is used for sending the incremental data change data of the local database to the cloud message service node CMSP and sending the incremental data change data to the other database if the incremental data log module does not record the incremental data change data of the local database.
Description
Technical Field
The invention relates to the technical field of database bidirectional synchronization, in particular to a synchronous node device for realizing the bidirectional synchronization of a database.
Background
In a production environment, due to requirements of performance, availability and the like, data of the same type needs to be distributed in different databases for processing, for example, in two databases in different places, the two databases respectively update data logically belonging to the same table according to a certain rule, and meanwhile, data change (including addition, deletion and change operations) in one database a needs to be synchronized into the other database B, and data change of the other database B also needs to be synchronized into the database a. The commonly used database one-way synchronization approach cannot be simply used in this scenario, such as a log-based data synchronization approach, because such an approach would cause the synchronization operation to fall into a dead loop.
Chinese patent publication No. CN103970833B discloses a solution for bidirectional synchronous data circulation in a log-based heterogeneous database synchronization system, which includes the following steps: respectively establishing special tables in a database for bidirectional synchronization; when the incremental data is transmitted to a target database from a source database, inserting a special table data into the target database, then finishing executing all the incremental data in the target database, and finally manually submitting an incremental data transaction in the target database; the specific operation when performing incremental data synchronization is as follows: acquiring incremental data from the log by taking a transaction as a unit, checking whether the transaction contains insertion data of a special table B of a database B, and if the insertion data exists and the source of the data is the database A, not synchronizing the incremental data to the database A any more; otherwise, the incremental data is synchronized to database a. The invention solves the problem of data circulation simply and conveniently by using the atomicity of the affairs without influencing the performance of the database. However, the patent also has a problem that an actual production system is often not allowed when a special table is built in a library of two parties and an incremental data transaction is submitted manually, so that the method is difficult to implement and the use scene is limited.
The cloud message service platform CMSP is a distributed message system which can cache and transmit messages and can be deployed in a distributed mode.
How to achieve the aim of bidirectional synchronization of the databases without endless loop under the conditions of not changing the databases of both parties and manually submitting incremental data transactions is a technical problem to be solved.
Disclosure of Invention
The technical task of the invention is to provide a synchronous node device for realizing the bidirectional synchronization of the databases to solve the technical problems of how to achieve the bidirectional synchronization of the databases without any change to the databases of both parties and manual submission of incremental data transactions and no endless loop.
In a first aspect, the present invention provides a synchronization node apparatus for implementing bidirectional synchronization of databases, configured on a database, for implementing bidirectional synchronization between databases, where:
the cloud message service node CMSP is used for caching and sending incremental data of an opposite-end database;
the bidirectional synchronous warehousing module is connected with the cloud message service node CMSP and used for acquiring database incremental data from an opposite database from the cloud message service node CMSP and storing the incremental data of the opposite database into a local database;
the incremental data log module is connected with the bidirectional synchronous warehousing module and is used for recording incremental data of an opposite-end database;
the bidirectional synchronous acquisition module is used for acquiring incremental data of database change data of a local database of a corresponding database, comparing the incremental data of the local database with the incremental data of an opposite-end database stored in the incremental data log module, if the incremental data log module does not record the incremental data change data of the local database, sending the incremental data change data of the local database to a cloud message service node CMSP, and sending the incremental data change data of the local database to the opposite-end database through the cloud message service node CMSP.
Preferably, the incremental data includes related information corresponding to each incremental record, including key value, hash value, incremental change type and recording time of the primary key or index column.
Preferably, the incremental change types include addition, modification, and deletion.
Preferably, when the incremental data of the local database is compared with the incremental data of the opposite database stored in the incremental data log module, the bidirectional synchronous acquisition module checks the Key value of the main Key or the index column, the generated hash value of the complete record and the incremental data of the database stored in the incremental data log module, and if the two values are completely consistent, the two values are considered to be the incremental data of the database from the opposite database, and synchronization is not needed.
Preferably, the incremental data log module is configured with a thread, and the thread is configured to periodically delete an expired incremental data log according to a set expiration time and a set recording time of the incremental data, so as to save storage resources and maintain the operating efficiency of the incremental data log module.
Preferably, the bi-directionally synchronized database is a homogeneous database or a heterogeneous database, and the databases are not limited to two.
Preferably, the cloud message service node CMSP may be replaced with message service software of a related function.
In a second aspect, the present invention provides a database bidirectional synchronization method, including the following steps:
for the databases synchronized bidirectionally, each database is configured with a synchronization node device for implementing bidirectional synchronization of the databases according to any one of claims 1 to 7;
for each database, caching and sending incremental data of an opposite-end database through a cloud message service node (CMSP);
for each database, acquiring incremental data of an opposite-end database from a cloud message service node CMSP through a bidirectional synchronous database-in module, and storing the incremental data of the opposite-end database into a local-end database;
for each database, recording incremental data of an opposite-end database through an incremental data log module;
for each database, acquiring incremental data of a local database through a bidirectional synchronous acquisition module, comparing the incremental data of the local database with the incremental data of an opposite database stored in an incremental data log module, if the incremental data of the local database is not recorded in the incremental data log module, sending the incremental data of the local database to a cloud message service node (CMSP), and sending the incremental data of the local database to the opposite database through the cloud message service node (CMSP).
Preferably, when the incremental data of the local database is compared with the incremental data of the opposite-end database stored in the incremental data log module, the bidirectional synchronous acquisition module checks the Key value of the main Key or the index column, the generated hash value of the complete record and the incremental data of the database stored in the incremental data log module, and if the Key value and the hash value are completely consistent, the incremental data of the database from the opposite-end database is considered, and synchronization is not needed.
Preferably, the thread configured in the incremental data log module periodically deletes the expired incremental data log according to the set expiration time and recording time of the incremental data, so as to save storage resources and maintain the operating efficiency of the incremental data log module.
The synchronous node device for realizing the bidirectional synchronization of the database has the following advantages that: after the synchronous node device is configured on the database, the aim of bidirectional synchronization and endless loop of the database can be achieved without changing the databases of both parties, namely, without building a special table for the databases of both parties and manually submitting incremental data transactions, and the synchronous node device has higher performance.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed for the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on the drawings without creative efforts.
The invention is further described below with reference to the accompanying drawings.
Fig. 1 is a block diagram illustrating an operation principle of a synchronization node apparatus according to embodiment 1 for implementing bidirectional synchronization of a database.
Detailed Description
The present invention is further described in the following with reference to the drawings and the specific embodiments so that those skilled in the art can better understand the present invention and can implement the present invention, but the embodiments are not to be construed as limiting the present invention, and the embodiments and the technical features of the embodiments can be combined with each other without conflict.
The embodiment of the invention provides a synchronous node device for realizing bidirectional synchronization of databases, which is used for solving the technical problems of bidirectional synchronization of the databases and no endless loop under the conditions that databases of two parties are not changed and incremental data transactions do not need to be submitted manually.
Example 1:
the synchronous node device for realizing the bidirectional synchronization of the databases is configured on the databases and used for realizing the bidirectional synchronization among the databases, a cloud message service node CMSP, a bidirectional synchronous storage module, an incremental data log module and a bidirectional synchronous acquisition module are configured in the synchronous node, and the cloud message service node CMSP is used for caching and sending the incremental data of an opposite-end database; the bidirectional synchronous database-in module is connected with the cloud message service node CMSP and is used for acquiring database incremental data from an opposite database from the cloud message service node CMSP and storing the incremental data of the opposite database into a local database; the incremental data log module is connected with the bidirectional synchronous warehousing module and used for recording incremental data of an opposite-end database, the bidirectional synchronous acquisition module is used for acquiring database change data incremental data of a local-end database of the opposite-end database, comparing the incremental data of the local-end database with the incremental data of the opposite-end database stored in the incremental data log module, if the incremental data log module does not record the incremental data change data of the local-end database, sending the incremental data change data of the local-end database to a cloud message service node CMSP, and sending the incremental data change data of the local-end database to the opposite-end database through the cloud message service node CMSP.
In this embodiment, the incremental data includes related information corresponding to each incremental record, including a key value, a hash value, an incremental change type, and a recording time of the primary key or the index column; the incremental change types include addition, modification, deletion, and the like.
When the incremental data of the local database is compared with the incremental data of the opposite-end database stored in the incremental data log module by the bidirectional synchronous acquisition module, the Key value of a main Key or an index row, the generated hash value of a complete record and the incremental data of the database stored in the incremental data log module are checked, and the Key value and the hash value are completely consistent, so that the incremental data of the database from the opposite-end database is considered to be the incremental data of the database, and synchronization is not needed.
The cloud message service node CMSP may be replaced with message service software of the related function.
The synchronization node device for implementing bidirectional database synchronization of the embodiment may be configured between heterogeneous databases or homogeneous databases, and implement database synchronization without changing the databases.
Specifically, the work flow is as follows:
the method comprises the steps that database incremental data from a database B are obtained from a cloud message service node CMSP of the database A, and are stored in the database A and stored in an incremental data log module of the database A;
the bidirectional synchronous acquisition module of the database A is responsible for acquiring database change data of the database A, comparing the acquired database change data with database incremental data stored in the incremental data log module, recording the database change data into a cloud message service node CMSP if the incremental data log module does not have the information, and sending the database incremental data of the database A to the database B through the cloud message service node CMSP, so that database synchronization is realized.
As an improvement of this embodiment, a thread is configured in the incremental data log module, and the thread is used for periodically deleting an expired incremental data log according to a set expiration time and a set recording time of the incremental data, so as to save storage resources and maintain the operating efficiency of the incremental data log module.
Example 2:
the bidirectional database synchronization method realizes the publication of isomorphic databases or heterogeneous databases. The method comprises the following steps:
s100, for the databases in bidirectional synchronization, each database is provided with a synchronization node device for realizing the bidirectional synchronization of the databases disclosed in the embodiment 1;
s200, caching and sending incremental data of an opposite-end database through a cloud message service node (CMSP) for each database;
s300, for each database, acquiring incremental data of an opposite-end database from a cloud message service node CMSP through a bidirectional synchronous warehousing module, and storing the incremental data of the opposite-end database into a local-end database;
s400, for each database, recording incremental data of an opposite-end database through an incremental data log module;
s500, for each database, acquiring incremental data of a local database through a bidirectional synchronous acquisition module, comparing the incremental data of the local database with the incremental data of an opposite-end database stored in an incremental data log module, if the incremental data of the local database is not recorded in the incremental data log module, sending the incremental data of the local database to a cloud message service node (CMSP), and sending the incremental data of the local database to the opposite-end database through the cloud message service node (CMSP).
In this embodiment, when the bidirectional synchronous acquisition module compares the incremental data of the local database with the incremental data of the opposite-end database stored in the incremental data log module, the Key value of the primary Key or the index row, the hash value of the generated complete record, and the database incremental data stored in the incremental data log module are checked, and the two are completely consistent, so that the incremental data of the database from the opposite-end database is considered to be the database incremental data, and synchronization is not required.
Based on the steps, for the database A and the database B to be bidirectionally synchronized, a synchronization node is respectively arranged at the database A end and the database B end, each synchronization node is respectively provided with a bidirectional synchronization acquisition module, a bidirectional synchronization storage module, an incremental data log module and a cloud message service node CMSP, and all modes of the synchronization nodes at the two ends cooperatively execute bidirectional synchronization.
For the database A end node, the bidirectional synchronous acquisition module is responsible for acquiring change information of the database A, comparing the acquired change information of the database A with the change information of the database stored in the incremental data log module, and if the incremental data log module does not have the change information, recording the change information into a cloud message service node (CMSP) and sending the change information to a database B; the bidirectional synchronous warehousing module is responsible for acquiring synchronous information from the database B from the cloud message service node CMSP, warehousing the synchronous information into the database A and storing the synchronous information into the incremental data log module; the incremental data log module is used for recording incremental data information from the database B; the cloud message service node CMSP is used for caching and sending database incremental data.
For the database B end node, the bidirectional synchronous acquisition module is responsible for acquiring the change information of the database B, comparing the acquired change information of the database B with the change information of the database stored in the incremental data log module, and if the incremental data log module does not have the change information, recording the change information into a cloud message service node CMSP and sending the change information to a database A; the bidirectional synchronous warehousing module is responsible for acquiring synchronous information from the database A from the cloud message service node CMSP, warehousing the synchronous information into the database B and storing the synchronous information into the incremental data log module; the incremental data log module is used for recording incremental data information from the database A; the cloud message service node CMSP is used for caching and sending database incremental data.
As an improvement, the expired incremental data logs are periodically deleted through threads configured in the incremental data log module according to the set expiration time and recording time of the incremental data, so that storage resources are saved and the operating efficiency of the incremental data log module is maintained.
It should be noted that not all steps and modules in the above flows and system structure diagrams are necessary, and some steps or modules may be omitted according to actual needs. The execution order of the steps is not fixed and can be adjusted as required. The system structure described in the above embodiments may be a physical structure or a logical structure, that is, some modules may be implemented by the same physical entity, or some modules may be implemented by a plurality of physical entities, or some components in a plurality of independent devices may be implemented together.
In the above embodiments, the hardware unit may be implemented mechanically or electrically. For example, a hardware element may comprise permanently dedicated circuitry or logic (such as a dedicated processor, FPGA or ASIC) to perform the corresponding operations. The hardware elements may also comprise programmable logic or circuitry, such as a general purpose processor or other programmable processor, that may be temporarily configured by software to perform the corresponding operations. The specific implementation (mechanical, or dedicated permanent, or temporarily set) may be determined based on cost and time considerations.
While the invention has been shown and described in detail in the drawings and in the preferred embodiments, it is not intended to limit the invention to the embodiments disclosed, and it will be apparent to those skilled in the art that various combinations of the code auditing means in the various embodiments described above may be used to obtain further embodiments of the invention, which are also within the scope of the invention.
Claims (10)
1. A synchronization node device for implementing bidirectional synchronization of databases, configured on the databases, and configured to implement bidirectional synchronization between the databases, wherein the synchronization node device is configured with:
the cloud message service node CMSP is used for caching and sending incremental data of an opposite-end database;
the bidirectional synchronous warehousing module is connected with the cloud message service node CMSP and used for acquiring database incremental data from an opposite database from the cloud message service node CMSP and storing the incremental data of the opposite database into a local database;
the incremental data log module is connected with the bidirectional synchronous warehousing module and is used for recording incremental data of an opposite-end database;
the bidirectional synchronous acquisition module is used for acquiring incremental data of database change data of a local database of a corresponding database, comparing the incremental data of the local database with the incremental data of an opposite-end database stored in the incremental data log module, if the incremental data log module does not record the incremental data change data of the local database, sending the incremental data change data of the local database to a cloud message service node CMSP, and sending the incremental data change data of the local database to the opposite-end database through the cloud message service node CMSP.
2. The synchronization node apparatus for implementing bidirectional synchronization of database according to claim 1, wherein the incremental data includes related information corresponding to each incremental record, including key value, hash value, incremental change type and recording time of the primary key or index column.
3. The sync node apparatus for bi-directional synchronization of databases as recited in claim 2, wherein the incremental change types include add, modify, and delete.
4. The synchronous node device for realizing bidirectional synchronization of databases according to claim 2 or 3, wherein the bidirectional synchronous acquisition module compares incremental data of a local database with incremental data of an opposite-end database stored in the incremental data log module, and checks the Key value of a primary Key or an index column, the generated hash value of a complete record and the incremental data of the database stored in the incremental data log module, and if the two are completely consistent, the two are considered as the incremental data of the database from the opposite-end database, and synchronization is not required.
5. The synchronization node apparatus for implementing bidirectional synchronization of databases according to claim 1, 2 or 3, wherein the incremental data log module is configured with a thread, and the thread is configured to periodically delete an expired incremental data log according to a set expiration time and a set recording time of the incremental data, so as to save storage resources and maintain the operating efficiency of the incremental data log module.
6. Synchronous node device for enabling bidirectional synchronization of databases according to claim 1, 2 or 3, characterized in that the databases synchronized bidirectionally are homogeneous databases or heterogeneous databases and the databases are not limited to two.
7. The synchronization node apparatus for implementing bidirectional synchronization of database according to claim 1, 2 or 3, wherein the cloud message service node CMSP can be replaced by message service software of related function.
8. The database bidirectional synchronization method is characterized by comprising the following steps:
for the databases synchronized bidirectionally, each database is configured with a synchronization node device for implementing bidirectional synchronization of the databases according to any one of claims 1 to 7;
for each database, caching and sending incremental data of an opposite-end database through a cloud message service node (CMSP);
for each database, acquiring incremental data of an opposite-end database from a cloud message service node CMSP through a bidirectional synchronous database-in module, and storing the incremental data of the opposite-end database into a local-end database;
for each database, recording incremental data of an opposite-end database through an incremental data log module;
for each database, acquiring incremental data of a local database through a bidirectional synchronous acquisition module, comparing the incremental data of the local database with the incremental data of an opposite database stored in an incremental data log module, if the incremental data of the local database is not recorded in the incremental data log module, sending the incremental data of the local database to a cloud message service node (CMSP), and sending the incremental data of the local database to the opposite database through the cloud message service node (CMSP).
9. The database bidirectional synchronization method according to claim 8, wherein the bidirectional synchronization acquisition module checks the Key value of the primary Key or index row, the hash value of the generated complete record, and the database incremental data stored in the incremental data log module when comparing the incremental data of the local database with the incremental data of the opposite database stored in the incremental data log module, and the two are completely consistent, so that the incremental data of the database from the opposite database is considered to be the incremental data of the database, and synchronization is not required.
10. The bidirectional synchronization method of the database according to claim 8 or 9, wherein the expired incremental data log is periodically deleted according to the set expiration time and recording time of the incremental data by the thread configured in the incremental data log module, so as to save storage resources and maintain the operating efficiency of the incremental data log module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110581382.1A CN113157813A (en) | 2021-05-27 | 2021-05-27 | Synchronous node device for realizing bidirectional synchronization of database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110581382.1A CN113157813A (en) | 2021-05-27 | 2021-05-27 | Synchronous node device for realizing bidirectional synchronization of database |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113157813A true CN113157813A (en) | 2021-07-23 |
Family
ID=76877695
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110581382.1A Pending CN113157813A (en) | 2021-05-27 | 2021-05-27 | Synchronous node device for realizing bidirectional synchronization of database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113157813A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6122630A (en) * | 1999-06-08 | 2000-09-19 | Iti, Inc. | Bidirectional database replication scheme for controlling ping-ponging |
| CN110990432A (en) * | 2019-11-18 | 2020-04-10 | 北京禧云信息科技有限公司 | Device and method for synchronizing distributed cache clusters across machine rooms |
| CN112000684A (en) * | 2020-08-25 | 2020-11-27 | 浪潮云信息技术股份公司 | Method and tool for realizing bidirectional synchronization of database of loop control based on TRXID |
| CN112035463A (en) * | 2020-07-22 | 2020-12-04 | 武汉达梦数据库有限公司 | Bidirectional synchronization method and synchronization device of heterogeneous database based on log analysis |
| CN112035418A (en) * | 2020-08-28 | 2020-12-04 | 掌阅科技股份有限公司 | Multi-computer room synchronization method, computing device and computer storage medium |
| CN112241437A (en) * | 2020-12-15 | 2021-01-19 | 深圳市易博天下科技有限公司 | Loop control method, device and equipment for multi-master synchronization of database and storage medium |
-
2021
- 2021-05-27 CN CN202110581382.1A patent/CN113157813A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6122630A (en) * | 1999-06-08 | 2000-09-19 | Iti, Inc. | Bidirectional database replication scheme for controlling ping-ponging |
| CN110990432A (en) * | 2019-11-18 | 2020-04-10 | 北京禧云信息科技有限公司 | Device and method for synchronizing distributed cache clusters across machine rooms |
| CN112035463A (en) * | 2020-07-22 | 2020-12-04 | 武汉达梦数据库有限公司 | Bidirectional synchronization method and synchronization device of heterogeneous database based on log analysis |
| CN112000684A (en) * | 2020-08-25 | 2020-11-27 | 浪潮云信息技术股份公司 | Method and tool for realizing bidirectional synchronization of database of loop control based on TRXID |
| CN112035418A (en) * | 2020-08-28 | 2020-12-04 | 掌阅科技股份有限公司 | Multi-computer room synchronization method, computing device and computer storage medium |
| CN112241437A (en) * | 2020-12-15 | 2021-01-19 | 深圳市易博天下科技有限公司 | Loop control method, device and equipment for multi-master synchronization of database and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3968175B1 (en) | Data replication method and apparatus, and computer device and storage medium | |
| CN107506451B (en) | Abnormal information monitoring method and device for data interaction | |
| US7783601B2 (en) | Replicating and sharing data between heterogeneous data systems | |
| CN110990432B (en) | Device and method for synchronizing distributed cache clusters across machine room | |
| CN113535656B (en) | Data access method, device, equipment and storage medium | |
| US20070255763A1 (en) | Database replication method and system | |
| CN108509462B (en) | Method and device for synchronizing activity transaction table | |
| CN105512266A (en) | Method and device for achieving operational consistency of distributed database | |
| US20170031948A1 (en) | File synchronization method, server, and terminal | |
| WO2021184761A1 (en) | Data access method and apparatus, and data storage method and device | |
| CN111597015A (en) | Transaction processing method and device, computer equipment and storage medium | |
| CN108108431B (en) | Data synchronization method and system | |
| CN107943618B (en) | Data quick recovery method of simulation system and storage medium | |
| CN113438275B (en) | Data migration method and device, storage medium and data migration equipment | |
| CN113703917B (en) | Multi-cluster resource data processing system and method and non-transient storage medium | |
| CN111708835B (en) | Block chain data storage method and device | |
| CN113157813A (en) | Synchronous node device for realizing bidirectional synchronization of database | |
| US11768741B2 (en) | Replicating changes written by a transactional virtual storage access method | |
| CN114328464A (en) | Data maintenance method, device, equipment and readable medium for distributed storage equipment | |
| CN111240933B (en) | Method, system, device and medium for monitoring performance data of multiple data centers | |
| CN114528049A (en) | Method and system for realizing API call information statistics based on InfluxDB | |
| CN115878721A (en) | Data synchronization method, device, terminal and computer readable storage medium | |
| CN112948494A (en) | Data synchronization method and device, electronic equipment and computer readable medium | |
| US8838910B2 (en) | Multi-part aggregated variable in structured external storage | |
| CN117390078B (en) | Data processing method, device, storage medium and computer equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210723 |