CN110941623A - Data synchronization method and device - Google Patents
Data synchronization method and device Download PDFInfo
- Publication number
- CN110941623A CN110941623A CN201911100526.6A CN201911100526A CN110941623A CN 110941623 A CN110941623 A CN 110941623A CN 201911100526 A CN201911100526 A CN 201911100526A CN 110941623 A CN110941623 A CN 110941623A
- Authority
- CN
- China
- Prior art keywords
- log
- service
- update
- target
- identifier
- 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
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/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- 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/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- 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
Abstract
The application relates to a data synchronization method and a data synchronization device, wherein the method is applied to a server and comprises the following steps: when a preset updating period is reached, acquiring a first updating log stored in a log queue, wherein the first updating log is generated according to a service updating instruction sent by a user and comprises a user identifier and a service identifier; acquiring target service data corresponding to the user identifier and the service identifier contained in the first update log from a cache, and updating the service data corresponding to the user identifier and the service identifier contained in the first update log in a database into the target service data; deleting the first update log stored in the log queue. By adopting the method and the device, the service data stored in the cache can be updated to the database in real time.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data synchronization method and apparatus.
Background
Currently, gaming application services need to support a large number of online users. In order to reduce the pressure of massive online users on the database, when a certain user logs in, the server can acquire the service data of the user from the database and store the service data into the cache. When receiving a service update instruction sent by the user, the server may update the service data of the user stored in the cache according to the service update instruction. Because the data volume of the service data stored in the cache is large, in order to prevent the service data updating from influencing the performance of the server, the server needs less time for the user volume to update all the service data stored in the cache to the database. Therefore, a solution for updating the service data stored in the cache to the database in real time is needed.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method and an apparatus for synchronizing data.
In a first aspect, a method for synchronizing data is provided, where the method is applied to a server, and the method includes:
when a preset updating period is reached, acquiring a first updating log stored in a log queue, wherein the first updating log is generated according to a service updating instruction sent by a user and comprises a user identifier and a service identifier;
acquiring target service data corresponding to the user identifier and the service identifier contained in the first update log from a cache, and updating the service data corresponding to the user identifier and the service identifier contained in the first update log in a database into the target service data;
deleting the first update log stored in the log queue.
In a second aspect, an apparatus for synchronizing data is provided, where the apparatus is applied to a server, and the apparatus includes:
the device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a first update log stored in a log queue when a preset update period is reached, the first update log is generated according to a service update instruction sent by a user, and the first update log comprises a user identifier and a service identifier;
the updating module is used for acquiring target service data corresponding to the user identifier and the service identifier contained in the first updating log from a cache, and updating the service data corresponding to the user identifier and the service identifier contained in the first updating log in a database into the target service data;
and the deleting module is used for deleting the first updating log stored in the log queue.
In a third aspect, a server is provided, comprising a memory and a processor, the memory having stored thereon a computer program operable on the processor, the processor implementing the steps of the method of any one of the first aspect when executing the computer program.
In a fourth aspect, a computer-readable storage medium is provided, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method of any one of the first aspects.
The embodiment of the application provides a data synchronization method and device. And when a preset updating period is reached, the server acquires a first updating log stored in the log queue. The first update log is generated according to a service update instruction sent by a user, and the first update log comprises a user identifier and a service identifier. Then, the server obtains the target service data corresponding to the user identifier and the service identifier included in the first update log from the cache, and updates the service data corresponding to the user identifier and the service identifier included in the first update log in the database into the target service data. Thereafter, the server deletes the first update log stored in the log queue. Therefore, when the service data stored in the cache is updated to the database, the server only needs to update the updated service data stored in the cache to the database according to the update log, so that the service data stored in the cache can be updated to the database in real time.
Drawings
Fig. 1 is a flowchart of a method for generating an update log according to an embodiment of the present application;
fig. 2 is a flowchart of a data synchronization method according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The embodiment of the application provides a data synchronization method. The method may be applied to a server. The server runs application services for providing different types of service services for each user, such as point service, recharge service, activity service, and the like. The server can also be provided with a cache and a database. The database is used for storing service data of different users with different service types. And the cache is used for storing the service data of each service type of a certain user when the user logs in the server.
For convenience of understanding, the present application preferentially introduces a method for generating an update log provided in an embodiment of the present application, as shown in fig. 1, a specific processing procedure is as follows:
step 101, receiving a target service update instruction aiming at a target service sent by a target user.
In implementation, when a certain user (i.e., a target user) logs in the server, the server may obtain service data of each service corresponding to the target user from the database, and store the service data in the cache. When the service data of a certain service (i.e. a target service) of the target user is changed, the target user may send a target service update instruction for the target service to the server. Accordingly, the server may receive the target service update instruction.
And step 102, updating the service data of the target service corresponding to the target user stored in the cache according to the target service updating instruction, and generating a second updating log. And the second updating log comprises the user identification of the target user and the service identification of the target service.
In implementation, after receiving the target service update instruction, the server may update the service data of the target service corresponding to the target user, which is stored in the cache, according to the target service update instruction. Meanwhile, the server may also generate an update log (i.e., a second update log) of the target service corresponding to the target user according to the target service update instruction. The second update log contains a user identification of the target user and a service identification of the target service. The format of the second update log may be "service identifier: user identification ". For example, the user identification of the target user is: 10000, the service identifier of the target service is: and the format of the second update log is' active service: 10000".
Step 103, storing the second update log into a log queue.
In an implementation, after the server generates the second update log, the second update log may be stored in a log queue. The server can store the second update log into the log queue in an asynchronous mode, so that the service performance of the server is prevented from being affected. Optionally, for a case that the server includes multiple log queues, the server may store the second update log into a target log queue corresponding to the target user according to the user identifier of the target user, where the specific processing procedure is as follows:
step one, according to the user identification of the target user, determining a target log queue corresponding to the target user in each log queue.
In implementation, after the server generates the second update log, the server may further determine, in each log queue, a target log queue corresponding to the target user according to the user identifier of the target user. Optionally, the server may perform a modulo operation on the user identifier of the target user to obtain a target remainder, and query the target log queue corresponding to the target remainder in a correspondence between the prestored remainder and the log queue.
And step two, storing the second updating log into the target log queue.
In implementation, after obtaining the target log queue corresponding to the target user, the server may store the second update log in the target log queue. In this way, for the case that the server includes multiple log queues, the update logs of the same user can be guaranteed to be stored in the same log queue, so that the subsequent deduplication processing of the update logs is facilitated, and possible conflicts and inconsistencies caused by updating the service data under the high concurrency condition can be avoided.
The following will describe a data synchronization method provided in an embodiment of the present application in detail with reference to a specific embodiment, as shown in fig. 2, the specific steps are as follows:
step 201, when a preset update period is reached, acquiring a first update log stored in a log queue. The first update log is generated according to a service update instruction sent by a user, and the first update log comprises a user identifier and a service identifier.
In implementation, a plurality of update services may be run in the server. Meanwhile, the server may also store the update cycle corresponding to each update service in advance. Wherein, the update cycle corresponding to each update service can be set by technical personnel according to experience; the update periods corresponding to the update services may be the same or different, and the embodiment of the present application is not limited. For each update service in the update services, when an update period corresponding to the update service is reached, the update service may poll the log queues, and when an update log exists in a certain log queue and the log queue is not occupied by other update services, the update service may preempt a queue lock of the log queue. The update service may then retrieve a first update log stored in the log queue. The first update log is generated according to a service update instruction sent by a user; the first update log contains a user identification and a service identification. Optionally, the update service may obtain all the first update logs stored in the log queue, or obtain a preset number of first update logs, which is not limited in the embodiment of the present application. Table one is a first update log stored in the log queue, as shown in table one:
watch 1
| Serial number | First update Log |
| 1 | And (4) active service: 10000 |
| 2 | And (4) point service: 10000 |
| 3 | And (4) active service: 10010 |
| 4 | And (4) recharging service: 10000 |
| 5 | And (4) active service: 10000 |
Step 202, obtaining the target service data corresponding to the user identifier and the service identifier included in the first update log from the cache, and updating the service data corresponding to the user identifier and the service identifier included in the first update log in the database into the target service data.
In implementation, after the update service acquires the first update log in the log queue, for each first update log, the update service may acquire, from the cache, target service data corresponding to the user identifier and the service identifier included in the first update log according to the user identifier and the service identifier included in the first update log. Then, the update service may update the service data corresponding to the user identifier and the service identifier included in the first update log in the database to the target service data according to the user identifier and the service identifier included in the first update log. Therefore, when the service data stored in the cache is updated to the database, the server only needs to update the updated service data stored in the cache to the database according to the update log, so that the service data stored in the cache can be updated to the database in real time.
Optionally, because the first update logs stored in the log queue may be repeated, the server may perform deduplication processing on the first update logs with the same user identifier and the same service identifier in each first update log to obtain the deduplicated first update logs.
In implementation, the server generates an update log for each time the target user updates the service data for the target service. For example, as shown in table one, a target user with a user identifier of 10000 updates service data twice for a target service with a service identifier of an active service, and the server generates two first update logs, where the two first update logs are both active services: 10000. in order to prevent the performance of the server from being affected by repeated updating of the same service data, the update service may perform deduplication processing on the first update logs with the same user identifier and service identifier in each first update log to obtain the deduplicated first update logs. For example, as shown in Table one, the update service may perform deduplication processing on the first update logs with sequence numbers 1 and 5. Table two is the first update log after deduplication, as shown in table two:
watch two
| Serial number | First update Log |
| 1 | And (4) active service: 10000 |
| 2 | And (4) point service: 10000 |
| 3 | And (4) active service: 10010 |
| 4 | And (4) recharging service: 10000 |
Correspondingly, for each of the deduplicated first update logs, the server may obtain, from the cache, target service data corresponding to the user identifier and the service identifier included in the first update log, and update, in the database, the service data corresponding to the user identifier and the service identifier included in the first update log into the target service data.
In implementation, after the update service obtains the first update log after deduplication, for each first update log, the update service may obtain, from the cache, target service data corresponding to the user identifier and the service identifier included in the first update log according to the user identifier and the service identifier included in the first update log. Then, the update service may update the service data corresponding to the user identifier and the service identifier included in the first update log in the database to the target service data according to the user identifier and the service identifier included in the first update log.
Step 203, deleting the first update log stored in the log queue.
In implementation, after the update service completes the update of the service data from the cache to the database, the first update log stored in the log queue may be deleted, and the queue lock of the preempted log queue is released.
Optionally, the server may further determine, in the first update log, the first update log with the same service identifier as the target update log. Then, the server can update the service data corresponding to the user identifier and the service identifier included in the target update log in the database into the target service data corresponding to the user identifier and the service identifier included in the target update log through a batch update instruction.
In practice, service data for different users of the same service type is typically stored in the same table in the database. Therefore, the update service may also determine, in the first update log, the first update log with the same service identifier as the target update log. For example, as shown in table two, if the service identifiers of the first update log with sequence number 1 (active service: 10000) and the first update log with sequence number 3 (active service: 10000) are the same, the first update logs with sequence numbers 1 and 3 are the target update logs. Then, for the target update log, the update service may update the service data corresponding to the user identifier and the service identifier included in the target update log in the database to the target service data corresponding to the user identifier and the service identifier included in the target update log through a batch update instruction. In this way, the batch update processing is performed on the first update log with the same service identifier through the batch update instruction, so that the cache performance can be improved, and the query rate per second (QPS) of the database can be reduced.
The embodiment of the application provides a data synchronization method. And when a preset updating period is reached, the server acquires a first updating log stored in the log queue. The first update log is generated according to a service update instruction sent by a user, and the first update log comprises a user identifier and a service identifier. Then, the server obtains the target service data corresponding to the user identifier and the service identifier included in the first update log from the cache, and updates the service data corresponding to the user identifier and the service identifier included in the first update log in the database into the target service data. Thereafter, the server deletes the first update log stored in the log queue. Therefore, when the service data stored in the cache is updated to the database, the server only needs to update the updated service data stored in the cache to the database according to the update log, so that the service data stored in the cache can be updated to the database in real time.
An embodiment of the present application further provides a data synchronization apparatus, which is applied to a server, and as shown in fig. 3, the apparatus includes:
an obtaining module 310, configured to obtain, when a preset update period is reached, a first update log stored in a log queue, where the first update log is generated according to a service update instruction sent by a user, and the first update log includes a user identifier and a service identifier;
the updating module 320 is configured to obtain target service data corresponding to the user identifier and the service identifier included in the first update log from the cache, and update the service data corresponding to the user identifier and the service identifier included in the first update log in the database into the target service data;
the deleting module 330 is configured to delete the first update log stored in the log queue.
As an alternative embodiment, as shown in fig. 4, the apparatus further includes:
a receiving module 340, configured to receive a target service update instruction for a target service sent by a target user;
a generating module 350, configured to update, according to the target service update instruction, service data of the target service corresponding to the target user stored in the cache, and generate a second update log, where the second update log includes a user identifier of the target user and a service identifier of the target service;
the storage module 360 is configured to store the second update log into the log queue.
As an optional implementation manner, the storage module 360 is specifically configured to:
determining a target log queue corresponding to the target user in each log queue according to the user identifier of the target user;
and storing the second updating log into the target log queue.
As an alternative embodiment, as shown in fig. 5, the apparatus further includes:
the duplicate removal module 370 is configured to perform duplicate removal processing on the first update logs with the same user identifier and the same service identifier in each first update log to obtain duplicate-removed first update logs;
the update module 320 is specifically configured to:
and aiming at each first update log in the deduplicated first update logs, acquiring target service data corresponding to the user identifier and the service identifier contained in the first update log from a cache, and updating the service data corresponding to the user identifier and the service identifier contained in the first update log in a database into the target service data.
As an optional implementation manner, the updating module 320 is specifically configured to:
determining a first update log with the same service identifier as a target update log in the first update log;
and updating the service data corresponding to the user identifier and the service identifier contained in the target update log in the database into target service data corresponding to the user identifier and the service identifier contained in the target update log through a batch update instruction.
The embodiment of the application provides a data synchronization device. And when a preset updating period is reached, the server acquires a first updating log stored in the log queue. The first update log is generated according to a service update instruction sent by a user, and the first update log comprises a user identifier and a service identifier. Then, the server obtains the target service data corresponding to the user identifier and the service identifier included in the first update log from the cache, and updates the service data corresponding to the user identifier and the service identifier included in the first update log in the database into the target service data. Thereafter, the server deletes the first update log stored in the log queue. Therefore, when the service data stored in the cache is updated to the database, the server only needs to update the updated service data stored in the cache to the database according to the update log, so that the service data stored in the cache can be updated to the database in real time.
In one embodiment, a server is provided, as shown in fig. 6, and includes a memory and a processor, where the memory stores a computer program that can be executed on the processor, and the processor implements the synchronization method steps of the data when executing the computer program.
In an embodiment, a computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the synchronization method of the above-mentioned data.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for synchronizing data, the method being applied to a server and comprising:
when a preset updating period is reached, acquiring a first updating log stored in a log queue, wherein the first updating log is generated according to a service updating instruction sent by a user and comprises a user identifier and a service identifier;
acquiring target service data corresponding to the user identifier and the service identifier contained in the first update log from a cache, and updating the service data corresponding to the user identifier and the service identifier contained in the first update log in a database into the target service data;
deleting the first update log stored in the log queue.
2. The method of claim 1, further comprising:
receiving a target service updating instruction aiming at a target service sent by a target user;
updating the service data of the target service corresponding to the target user stored in the cache according to the target service updating instruction, and generating a second updating log, wherein the second updating log comprises a user identifier of the target user and a service identifier of the target service;
storing the second update log into the log queue.
3. The method of claim 2, wherein storing the second update log in the log queue comprises:
determining a target log queue corresponding to the target user in each log queue according to the user identifier of the target user;
and storing the second updating log into the target log queue.
4. The method of claim 1, wherein after obtaining the first update log stored in the log queue, the method further comprises:
in each first update log, performing duplicate removal processing on the first update log with the same user identifier and service identifier to obtain a duplicate-removed first update log;
the obtaining, from the cache, target service data corresponding to the user identifier and the service identifier included in the first update log, and updating, to the target service data, service data corresponding to the user identifier and the service identifier included in the first update log in a database, includes:
and for each first update log in the deduplicated first update logs, acquiring target service data corresponding to the user identifier and the service identifier included in the first update log from a cache, and updating the service data corresponding to the user identifier and the service identifier included in the first update log in a database into the target service data.
5. The method according to claim 1, wherein the obtaining target service data corresponding to the user identifier and the service identifier included in the first update log from the cache, and updating the service data corresponding to the user identifier and the service identifier included in the first update log in the database into the target service data comprises:
determining a first update log with the same service identifier as a target update log in the first update log;
and updating the service data corresponding to the user identifier and the service identifier contained in the target update log in the database into target service data corresponding to the user identifier and the service identifier contained in the target update log through a batch update instruction.
6. An apparatus for synchronizing data, the apparatus being applied to a server, the apparatus comprising:
the device comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a first update log stored in a log queue when a preset update period is reached, the first update log is generated according to a service update instruction sent by a user, and the first update log comprises a user identifier and a service identifier;
the updating module is used for acquiring target service data corresponding to the user identifier and the service identifier contained in the first updating log from a cache, and updating the service data corresponding to the user identifier and the service identifier contained in the first updating log in a database into the target service data;
and the deleting module is used for deleting the first updating log stored in the log queue.
7. The apparatus of claim 6, further comprising:
the receiving module is used for receiving a target service updating instruction aiming at a target service and sent by a target user;
a generating module, configured to update, according to the target service update instruction, service data of the target service corresponding to the target user stored in the cache, and generate a second update log, where the second update log includes a user identifier of the target user and a service identifier of the target service;
and the storage module is used for storing the second updating log into the log queue.
8. The apparatus of claim 6, further comprising:
the duplication removing module is used for carrying out duplication removing processing on the first update logs with the same user identification and service identification in each first update log to obtain the duplicate-removed first update logs;
the update module is specifically configured to:
and for each first update log in the deduplicated first update logs, acquiring target service data corresponding to the user identifier and the service identifier included in the first update log from a cache, and updating the service data corresponding to the user identifier and the service identifier included in the first update log in a database into the target service data.
9. A server comprising a memory and a processor, the memory having stored thereon a computer program operable on the processor, wherein the processor, when executing the computer program, performs the steps of the method of any of claims 1 to 5.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911100526.6A CN110941623A (en) | 2019-11-12 | 2019-11-12 | Data synchronization method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911100526.6A CN110941623A (en) | 2019-11-12 | 2019-11-12 | Data synchronization method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110941623A true CN110941623A (en) | 2020-03-31 |
Family
ID=69907696
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911100526.6A Pending CN110941623A (en) | 2019-11-12 | 2019-11-12 | Data synchronization method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110941623A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112597151A (en) * | 2020-12-03 | 2021-04-02 | 长沙市到家悠享家政服务有限公司 | Data processing method, device, equipment and storage medium |
| CN113342824A (en) * | 2021-06-30 | 2021-09-03 | 平安资产管理有限责任公司 | Data storage method, device, equipment and medium based on target storage equipment |
| CN113434525A (en) * | 2021-06-24 | 2021-09-24 | 青岛海尔科技有限公司 | Cache data updating method and device, storage medium and electronic device |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101364217A (en) * | 2007-08-08 | 2009-02-11 | 华为技术有限公司 | Data maintenance method, equipment and system thereof in data-base |
| CN101369283A (en) * | 2008-09-25 | 2009-02-18 | 中兴通讯股份有限公司 | Data synchronization method and system for internal memory database physical data base |
| CN104572689A (en) * | 2013-10-17 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Data synchronizing method, device and system |
| CN104750740A (en) * | 2013-12-30 | 2015-07-01 | 北京新媒传信科技有限公司 | Data renewing method and device |
| US20150213100A1 (en) * | 2012-10-18 | 2015-07-30 | Tencent Technology (Shenzhen) Company Limited | Data synchronization method and system |
| CN105208060A (en) * | 2014-06-19 | 2015-12-30 | 阿里巴巴集团控股有限公司 | Service data synchronization method, service data synchronization device and service data synchronization system |
| CN108647237A (en) * | 2018-03-30 | 2018-10-12 | 厦门海迈科技股份有限公司 | Method of data synchronization between isomeric relationship type database |
| CN109271447A (en) * | 2018-09-04 | 2019-01-25 | 中国平安人寿保险股份有限公司 | Method of data synchronization, device, computer equipment and storage medium |
| CN109597818A (en) * | 2018-11-28 | 2019-04-09 | 优刻得科技股份有限公司 | Data-updating method, device, storage medium and equipment |
| CN109739929A (en) * | 2018-12-18 | 2019-05-10 | 中国人民财产保险股份有限公司 | Method of data synchronization, apparatus and system |
| CN110019062A (en) * | 2017-08-14 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Method of data synchronization and system |
-
2019
- 2019-11-12 CN CN201911100526.6A patent/CN110941623A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101364217A (en) * | 2007-08-08 | 2009-02-11 | 华为技术有限公司 | Data maintenance method, equipment and system thereof in data-base |
| CN101369283A (en) * | 2008-09-25 | 2009-02-18 | 中兴通讯股份有限公司 | Data synchronization method and system for internal memory database physical data base |
| US20150213100A1 (en) * | 2012-10-18 | 2015-07-30 | Tencent Technology (Shenzhen) Company Limited | Data synchronization method and system |
| CN104572689A (en) * | 2013-10-17 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Data synchronizing method, device and system |
| CN104750740A (en) * | 2013-12-30 | 2015-07-01 | 北京新媒传信科技有限公司 | Data renewing method and device |
| CN105208060A (en) * | 2014-06-19 | 2015-12-30 | 阿里巴巴集团控股有限公司 | Service data synchronization method, service data synchronization device and service data synchronization system |
| CN110019062A (en) * | 2017-08-14 | 2019-07-16 | 北京京东尚科信息技术有限公司 | Method of data synchronization and system |
| CN108647237A (en) * | 2018-03-30 | 2018-10-12 | 厦门海迈科技股份有限公司 | Method of data synchronization between isomeric relationship type database |
| CN109271447A (en) * | 2018-09-04 | 2019-01-25 | 中国平安人寿保险股份有限公司 | Method of data synchronization, device, computer equipment and storage medium |
| CN109597818A (en) * | 2018-11-28 | 2019-04-09 | 优刻得科技股份有限公司 | Data-updating method, device, storage medium and equipment |
| CN109739929A (en) * | 2018-12-18 | 2019-05-10 | 中国人民财产保险股份有限公司 | Method of data synchronization, apparatus and system |
Non-Patent Citations (3)
| Title |
|---|
| 何颖: "《计算机系统平台》", 31 July 2018, 北京邮电大学出版社, pages: 166 * |
| 张骁: "应用软件运行日志的收集与服务处理框架", 《计算机工程与应用》, pages 477 - 89 * |
| 赵敏媛: "《数据结构》", 中国铁道出版社, pages: 146 - 147 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112597151A (en) * | 2020-12-03 | 2021-04-02 | 长沙市到家悠享家政服务有限公司 | Data processing method, device, equipment and storage medium |
| CN113434525A (en) * | 2021-06-24 | 2021-09-24 | 青岛海尔科技有限公司 | Cache data updating method and device, storage medium and electronic device |
| CN113434525B (en) * | 2021-06-24 | 2023-06-09 | 青岛海尔科技有限公司 | Cache data updating method and device, storage medium and electronic device |
| CN113342824A (en) * | 2021-06-30 | 2021-09-03 | 平安资产管理有限责任公司 | Data storage method, device, equipment and medium based on target storage equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110941623A (en) | Data synchronization method and device | |
| CN110636130A (en) | Delayed message processing method and device, computer equipment and storage medium | |
| CN111245548A (en) | Data synchronization method and device based on timestamp and computer equipment | |
| CN108512948B (en) | Address book updating method and device, computer equipment and storage medium | |
| US9026493B1 (en) | Multi-master RDBMS improvements for distributed computing environment | |
| CN109032527B (en) | Data processing method, storage medium and computer device | |
| CN111414424A (en) | Method, system, medium and device for automatically synchronizing redis of configuration data | |
| CN110795171A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN113900842B (en) | Message consumption method and device, electronic equipment and computer storage medium | |
| CN111427931A (en) | Distributed query engine and method for querying relational database by using same | |
| CN108875035B (en) | Data storage method of distributed file system and related equipment | |
| CN107222555B (en) | Message processing method and device | |
| CN110188081B (en) | Log data storage method and device based on cassandra database and computer equipment | |
| CN110882535A (en) | Method and device for synchronizing archived files | |
| CN112527479A (en) | Task execution method and device, computer equipment and storage medium | |
| CN109165305B (en) | Characteristic value storage and retrieval method and device | |
| CN112784318A (en) | Method, device and storage medium for generating unique identification code of equipment | |
| CN113742681B (en) | Account management method and device, computer equipment and storage medium | |
| CN111339170A (en) | Data processing method and device, computer equipment and storage medium | |
| CN110765125A (en) | Data storage method and device | |
| CN107315693B (en) | Data storage method and device | |
| CN115086355A (en) | User information processing method and device based on block chain | |
| US20160320974A1 (en) | System, method, and apparatus for updating data in a distributed storage system | |
| CN106453455A (en) | Audio file synchronization method and audio file synchronization device | |
| CN112783866A (en) | Data reading method and device, computer equipment and storage medium |
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 |