WO2017124938A1 - 一种数据同步方法、装置及系统 - Google Patents
一种数据同步方法、装置及系统 Download PDFInfo
- Publication number
- WO2017124938A1 WO2017124938A1 PCT/CN2017/070648 CN2017070648W WO2017124938A1 WO 2017124938 A1 WO2017124938 A1 WO 2017124938A1 CN 2017070648 W CN2017070648 W CN 2017070648W WO 2017124938 A1 WO2017124938 A1 WO 2017124938A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- real
- time notification
- data
- modification
- database
- Prior art date
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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/273—Asynchronous replication or reconciliation
-
- 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/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- 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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- 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
Definitions
- the present application relates to the field of database technologies, and in particular, to a data synchronization method, apparatus, and system.
- the distributed multi-active data center (referred to as multi-live) technology is proposed for the problems existing in the cold standby technology.
- the implementation idea is that the services of multiple data centers are not divided into active and standby, and work in the normal mode, in parallel.
- Service access provides services to prevent the backup data center from being idle, and can double the service capacity of the system. In the event of a failure in one of the data centers, other data centers can quickly take over all of the business.
- the present application provides a data synchronization method, device and system, and the technical solution is as follows:
- a data synchronization method comprising:
- the real-time notification is generated for the current data modification, and the real-time notification is sent to the data synchronization target end, where the real-time notification is carried. Bring relevant information about this data modification;
- the data synchronization target end After receiving the real-time notification, the data synchronization target end parses the data modification related information from the real-time notification, and updates the target end database cache according to the parsing result.
- a data synchronization method which is applied to a data synchronization source, and the method includes:
- a real-time notification is generated for the current data modification, and the real-time notification carries the relevant information of the current data modification;
- a data synchronization method which is applied to a data synchronization target, and the method includes:
- the real-time notification is generated and sent for the current data modification after the data synchronization source determines the data modification of the source database, and the real-time notification carries the relevant information of the current data modification.
- a data synchronization source device includes: a real-time notification generation module, and a real-time notification transmission module;
- the real-time notification generating module is configured to generate a real-time notification for the current data modification after determining the data modification of the source-end database; the real-time notification carries the relevant information of the current data modification;
- the real-time notification sending module is configured to send the real-time notification to the data synchronization target end, so that after the data synchronization target end receives the real-time notification, the data modification related information is parsed from the real-time notification, according to the analysis result. Update the target database cache.
- a data synchronization target device comprising: a real-time notification receiving module and a cache data update module;
- the real-time notification receiving module is configured to receive a real-time notification sent by the data synchronization source end;
- the cache data update module is configured to parse the data modification related information from the real-time notification, and update the target end database cache according to the parsing result;
- the real-time notification is that the data synchronization source end generates and sends the data modification after determining the data of the source end database, and the real-time notification carries the relevant information of the current data modification.
- a data synchronization system comprising a data synchronization source device and a data synchronization target device:
- the data synchronization source device includes: a real-time notification generation module, and a real-time notification sending module;
- the real-time notification generating module is configured to generate a real-time notification for the current data modification after determining the data modification of the source-end database; the real-time notification carries the relevant information of the current data modification;
- the real-time notification sending module is configured to send the real-time notification to a data synchronization target end;
- the data synchronization target device includes: a real-time notification receiving module and a cache data update module;
- the real-time notification receiving module is configured to receive the real-time notification
- the cache data update module is configured to parse the data modification related information from the real-time notification, and update the target end database cache according to the parsing result.
- the technical solution provided by the present application after the data synchronization source side modifies the data, immediately sends a real-time notification to the data synchronization target end, and after receiving the real-time notification, the target end can directly update the local database cache according to the information carried in the real-time notification, It is not necessary to wait for the synchronization of the underlying database to complete the cache update, thereby reducing the delay of the cache synchronization update; if the target end cannot directly update the local database cache according to the information carried in the real-time notification, it can be known that the local database is about to be updated synchronously. Further, the local database can be monitored to update the cached data at the first time after the local data is synchronized, thereby reducing the cache synchronization update delay.
- FIG. 1 is a first structural schematic view of a prior art dual active system
- FIG. 2 is a second schematic structural view of a prior art dual active system
- Figure 3 is a first schematic structural view of the active-active system of the present application.
- FIG. 5 is a schematic diagram of a first process of the data synchronization method of the present application.
- FIG. 6 is a first schematic flowchart of a data synchronization method of the present application.
- FIG. 7 is a schematic structural diagram of a data synchronization source device of the present application.
- FIG. 8 is a schematic structural diagram of a data synchronization target device of the present application.
- FIG. 9 is a schematic structural diagram of a data synchronization system of the present application.
- Figure 10 is a block diagram showing the structure of an apparatus for configuring the apparatus of the present application.
- Figure 1 shows the architecture of a dual-active system.
- the two data centers are respectively installed in the equipment room A and the machine room B.
- the database A and the database B are respectively located in the equipment room A and the equipment room B.
- the application server directly interacts with the database, and the application server reads and writes the local database according to instructions sent by the user side or other systems.
- the database of a certain computer room is modified, it is necessary to synchronize the modification to other computer rooms as soon as possible during the synchronization process.
- the database that is modified first is called the source database
- the database that is subsequently synchronized is called the target data database.
- Cache is a common technique in database operations. Compared with the basic underlying database storage area, the cache has better data read and write performance and can avoid direct interaction between the application side and the underlying database. For example, for stateful data, a more obvious feature is that reading and writing are less. Taking user information data as an example, after the user fills in personal information in the registration phase, it is unlikely that the personal information will be modified frequently. Based on such characteristics, most systems use a layer of cache on the upper layer of the database to withstand a large number of data query requests, thereby reducing the query request actually sent to the database and improving the overall query performance of the system.
- the cache technology can also be applied in a multi-live system. As shown in Figure 2, a layer of cache is set on the upper layer of the database, and the common data is put into the cache in advance. When the application server needs to use the data, the data is preferentially read from the cache. Thereby improving the efficiency of data reading, and avoiding the application server directly interacting with the underlying database, reducing the read and write burden of the underlying database.
- the cache becomes the main source for the application server to read data. Therefore, when data synchronization is performed between data centers, the synchronization update problem of the target server room cache must be further considered to ensure the correctness of the target data query. . Taking the active-active system shown in FIG.
- two databases can also be deployed in the equipment room A, one of which serves as a writing library, one database as a reading library, and other computer rooms, such as the computer room B, to read the reading library, so that data writing operations pass through the equipment room.
- the write library in A is performed, and after the write library writes the data, the newly written data can be the same Steps in the local computer room read library and other computer room read library, so in the cache operation, write the data written by the library, you need to go to the reading room of each computer room before you can update the corresponding cache.
- the application server on the target side will preferentially read data from the cache, so the synchronous update of the data cached on the target side is the ultimate goal.
- the serial data synchronization efficiency between the underlying databases is relatively low. Especially in the case of data center deployment in different places, the delay is quite obvious, and adding the cache update step will lead to further increase of delay.
- the two data centers are deployed in two cities with a distance of 1000km.
- the data synchronization delay between the database write library and the remote read library is about 3s, so if the data synchronization of the two places is all using the database.
- the original data synchronous replication scheme the data timeliness will reach the second level, it may happen that the user writes data in the data center of one city, and then the data center of another city cannot immediately read the data just written, need The user waits for a few seconds and then tries again to resolve it, which affects the user experience.
- the present application provides a data synchronization method to reduce the synchronization update delay of a database cache between data centers, and the method includes the following steps:
- the real-time notification is generated for the current data modification, and the real-time notification is sent to the data synchronization target end, and the real-time notification carries the relevant information of the current data modification;
- the data synchronization target end After receiving the real-time notification, the data synchronization target end parses the data modification related information from the real-time notification, and updates the target-end database cache according to the analysis result.
- the execution body of the foregoing method may be a synchronization device respectively located at the data synchronization source end and the data synchronization target end.
- the synchronization device A located at the data synchronization source end is in communication connection with the application server A, and determines the application server A to the database A.
- a real-time notification is generated and sent to the synchronization device B located at the data synchronization target end, and the synchronization device B directly updates the cache B according to the real-time notification.
- the related functional modules of the above synchronization device may all be located in a physical entity (for example, a dedicated server) that is relatively independent from the application server, as shown in FIG. 3 . It may also be partially or completely located in the application server.
- the functions of the synchronization device on both sides of the data synchronization source end and the data synchronization target end are integrated on both sides.
- the corresponding system architecture can be simplified as shown in FIG. 4, and the interaction between the aforementioned synchronization device and the application server is simplified to the internal interaction of the application server.
- the technical solution provided by the present application reduces the update delay of the data synchronization target database cache by introducing real-time notification, and does not need to make excessive adjustments to the original data synchronization scheme of the underlying database.
- the local cache update operation of the data synchronization source can be directly implemented by using the prior art solution, and is basically independent of the update delay of the data synchronization target database cache, and therefore is not described in this application.
- database A is a write library
- database B is a read library.
- the application scheme and the database read and write separation mechanism are not necessarily related.
- database A and database B can also be write libraries, or you can deploy write library and read library in one computer room, and other computer room deployment read library, etc. It does not affect the implementation of the solution of the present application.
- FIG. 5 shows a data synchronization process in which the solution of the present application is applied in an active-active system.
- the following embodiment will explain the entire process in conjunction with the simplified system architecture shown in FIG. 4.
- the data synchronization source determines data modification of the source database.
- Determining the timing of determining the data modification may be after the application server A sends a data write request to the database A, or after determining that the database A has been successfully written, the former method can theoretically further reduce the delay of the overall process. The latter method can avoid the situation that the data synchronization target end cache update is inconsistent with the database caused by the data synchronization source database write failure.
- Those skilled in the art can flexibly set according to the stability performance and application scenarios of the system.
- the data synchronization target end generates real-time notification for the current data modification, and the real-time notification is Know to send to the data synchronization target.
- the application server A writes the details of the data modification corresponding to the data write operation of the database A into the real-time notification, and also writes the detailed details into the message body corresponding to the real-time notification.
- the steps S102 and S103 correspond to two relatively independent operations, so there is no timing limit between the two steps; for the data synchronization target, the steps 104 should be located in time series after receiving real-time notifications.
- the data synchronization target end parses the data modification detailed information from the real-time notification, and directly updates the target end database cache according to the parsing result;
- the application server B detects the real-time notification receiving port in real time, and immediately parses the real-time notification after receiving the real-time notification. According to the processing of the real-time notification by the application server A, the application server B may need to perform the corresponding analysis in the parsing. Decompression, decryption, etc., will not be described in detail here.
- the local database cache B is directly updated according to the analysis result. Since the synchronization of the underlying database data is not transmitted in real time to different places, but a certain number of modified data blocks are accumulated and then packaged and packaged by batch, the average transmission speed of real-time notification is higher than the synchronization speed of the underlying database, see figure As shown in S105 of 4, in general, the data synchronization target end can directly change according to the real-time notification before the underlying database synchronization is completed. The new local cache does not need to rely on the synchronization of the underlying database.
- the synchronous average delay of the underlying database is about 3s, and the real-time notification can reduce the synchronization update delay of the cached data to about 30ms, or even The latency is lower and the timeliness of database cache synchronization is significantly improved.
- an update message is sent to the cache server to perform the update operation.
- the cache server after receiving the update message, it may further determine whether the cached data needs to be updated according to the actual situation, for example, according to the write timestamp of the data, or the notification message may carry some other information.
- the version number information can be carried, the version number is checked to determine whether a cache update is required, and the like. That is to say, in some cases, although the application server B performs the update operation, whether the cache data is finally updated successfully needs to be judged by the cache server itself. This update manner does not affect the implementation of the present application.
- the data synchronization source end carries the detailed modification information of the local database in the real-time notification, and utilizes the low delay feature of the real-time notification, so that the data synchronization target end can complete the local database without relying on the underlying database synchronization completion. Cached synchronization updates.
- the amount of information that can be transmitted in the real-time notification may be limited by various factors such as the transmission bandwidth and the notification message center storage capacity. If the data synchronization source has a large amount of data modified at one time, these details are detailed. The modification will be difficult to transmit to the data synchronization target through real-time notification. For this case, the corresponding solution is also provided in this application.
- the foregoing real-time notification can be implemented by using a message system, for example, an existing message system or a message system established for this purpose can be utilized, and the architecture and form of the message system are not limited.
- FIG. 6 shows another data synchronization process in which the solution of the present application is applied in a dual-active system.
- the following embodiment will explain the entire process in conjunction with the system architecture shown in FIG. 3.
- the data synchronization source end determines data modification of the source end database
- This step is similar to that of S101, and is not described in this embodiment.
- the data synchronization target end generates a real-time notification for the current data modification, and sends the real-time notification to the data synchronization target end.
- An identification information may be generated, which may be a serial number, or an identification string generated by a specific algorithm, etc.
- the application server A will need to modify the details of the data (value , data table identifier, row identifier, column identifier, etc.) are submitted to database A together with the identification information.
- the application server A writes the identification information into the real-time notification by the limitation of the real-time notification message body carrying capacity. Immediately after the real-time notification is generated, it is sent to the data synchronization target.
- the database A starts to initiate a synchronization operation on the database for the current modification.
- the above modified identification information is also transmitted to the database B together with the specific data modification content.
- steps S202 and S203 correspond to two relatively independent operations, so there is no timing limit between the two steps; for the data synchronization target, Step 204 should be located in time series after receiving the real-time notification.
- the data synchronization target end parses the data modification operation identifier from the real-time notification, and monitors the target end database according to the analysis result.
- the application server B detects the real-time notification receiving port in real time, and immediately analyzes the real-time notification after receiving the real-time notification.
- the application server B obtains the source-side database A from the real-time notification analysis. After modifying the operation identifier, the database B is monitored for the identifier.
- the data synchronization source end is synchronized to the bottom database of the data synchronization target end.
- the data synchronization source end updates the target database cache according to the content of the synchronized target database.
- the modification operation corresponding to the application server monitoring identifier After the modification operation corresponding to the application server monitoring identifier has been synchronized from the database A to the database B, the corresponding data is read from the database B, and then the local database cache B is updated according to the reading result.
- the application server B Since the transmission speed of the real-time notification is higher than the synchronization speed of the underlying database, in general, after receiving the real-time notification, the application server B needs to wait for a period of time to update the cache B. Compared with the previous embodiment, in this embodiment, the data synchronization target needs to wait for the underlying database synchronization to complete before updating the local cache. But due to the use of real time The notification enables the data synchronization target to know in advance that the underlying database will be modified, and can acquire the data to update the cache at the first time after the synchronization is completed by means of monitoring, so that it can still be compared with the existing technical solution. Reduce the delay of cache synchronization updates to a certain extent.
- the two data synchronization methods described in the above embodiments can reduce the synchronization update delay of the data synchronization target end cache to different degrees.
- the first scheme can be selected to achieve lower The delay effect.
- the amount of data modification by the application server to the database is often uncertain. Taking the CIF (Customer Information File) system as an example, the amount of data modified for individual user information is generally small, and for some For large accounts associated with many sub-accounts, one modification may involve data changes for a large number of sub-accounts.
- the present application also provides an adaptive data synchronization scheme:
- the data of the source database is determined. First, it is determined whether the amount of data to be modified exceeds a preset threshold.
- the threshold is determined according to the bearer capability of the real-time notification, and the bearer capability of the real-time notification depends on Transmission bandwidth, notification message center storage capacity and other factors, of course, the threshold determination may also need to consider the compression, coding and other factors when generating real-time notifications.
- the modification including at least the modification of the specific numerical information is written into the real-time notification; if it is determined that the real-time notification cannot carry the modification For the specific modification involved in the operation, only the operation identifier of this modification is written into the real-time notification.
- the real-time notification is first parsed. If the parsing result includes the specific numerical information involved in the modification, the target database cache is directly updated according to the parsing result; otherwise, the target end database is monitored according to the parsed modified operation identifier, and the corresponding modification is detected when the identifier is detected. After the operation has been synchronized from the source database to the target database, the corresponding data is obtained from the target database to update the target database cache.
- the data synchronization source adaptively generates real-time notifications carrying different content according to the amount of data involved in the modification.
- the data synchronization target end can update the local cache data without waiting for the underlying database synchronization to complete, and for large-scale data modification, the local cache data can also be performed at the first time after the synchronization is completed. Update.
- the present application also provides a data synchronization source device, as shown in FIG. 7, the device may include: a real-time notification generation module 110, a real-time notification sending module 120;
- the real-time notification generating module 110 is configured to generate a real-time notification for the current data modification after determining the data modification of the source-end database; the real-time notification carries the relevant information of the current data modification;
- the real-time notification sending module 120 is configured to send the real-time notification to the data synchronization target end; after the data synchronization target end receives the real-time notification, the data modification related information is parsed from the real-time notification, and the target-end database cache is updated according to the parsing result. .
- the real-time notification generating module 110 may be specifically configured to: after determining the data modification of the source-end database, write the specific numerical information involved in the modification into the real-time notification.
- the real-time notification generating module 110 may be specifically configured to: after determining the data modification of the source end database, write the modified operation identifier into the real-time notification.
- the real-time notification generating module 110 may be specifically configured to: after determining data modification of the source end database, determine whether the data amount of the current modification exceeds a preset threshold; if not, The specific numerical information involved in this modification is written in the real-time notification; if yes, the modified operation identifier is written in the real-time notification.
- the data synchronization source device may be configured in the data synchronization source application server.
- the present application further provides a data synchronization target device, as shown in FIG. 8, the device may include: a real-time notification receiving module 210, a cache data update module 220;
- the real-time notification receiving module 210 is configured to receive a real-time notification sent by the data synchronization source end;
- the cache data update module 220 is configured to parse the data modification related information from the real-time notification. Update the target database cache according to the analysis result;
- the real-time notification is that the data synchronization source end generates and sends the data modification after determining the data of the source end database, and the real-time notification carries the relevant information of the current data modification.
- the specific value information involved in the modification may be included in the real-time notification
- the cache data update module 220 may be specifically configured to directly update the target database cache according to the specific numerical information involved in the parsing.
- the real-time notification may include the operation identifier of the current modification
- the cache data update module 220 may be specifically configured to: monitor the target end database according to the parsed modified operation identifier, and after detecting that the modification operation corresponding to the identifier has been synchronized from the source database to the target database, The synchronized target database content is updated to the target database cache.
- the real-time notification may include: specific numerical information related to the current modification, or an operation identifier of the current modification;
- the cache data update module 220 may be specifically configured to: if the parsing result is the specific numerical information involved in the modification, directly update the target database cache according to the parsing result; in the case that the parsing result is the modified operation identifier, The target end database is monitored according to the identifier. After the modification operation corresponding to the identifier has been synchronized from the source database to the target database, the target database cache is updated according to the content of the synchronized target database.
- the data synchronization target device may be configured in a data synchronization target application server.
- the present application also provides a data synchronization system.
- the apparatus may include a data synchronization source device 100 and a data synchronization target device 200:
- the data synchronization source device 100 may include: a real-time notification generating module 110, and a real-time notification sending module 120;
- the real-time notification generating module 110 is configured to generate a real-time notification for the current data modification after determining the data modification of the source-end database; the real-time notification carries the relevant information of the current data modification;
- the real-time notification sending module 120 is configured to send the real-time notification to the data synchronization target end;
- the data synchronization target device 200 may include: a real-time notification receiving module 210, a cache data update module 220;
- the real-time notification receiving module 210 is configured to receive real-time notifications.
- the cache data update module 220 is configured to parse the data modification related information from the real-time notification, and update the target end database cache according to the parsing result.
- the real-time notification generating module 120 may be specifically configured to: after determining the data modification of the source end database, write the specific numerical information involved in the modification into the real-time notification;
- the cache data update module 220 may be specifically configured to directly update the target database cache according to the specific numerical information involved in the parsing.
- the real-time notification generating module 120 may be specifically configured to: after determining the data modification of the source database, write the modified operation identifier into the real-time notification;
- the cache data update module 220 may be specifically configured to monitor the target end database according to the modified operation identifier obtained by the parsing, and after detecting that the modification operation corresponding to the identifier has been synchronized from the source database to the target database, according to the synchronization After the target database content, update the target database cache.
- the real-time notification generating module 120 may be specifically configured to determine whether the data amount of the current modification exceeds a preset threshold after determining data modification of the source database; if not, The specific numerical information involved in this modification is written into the real-time notification; if yes, the modified operation identifier is written into the real-time notification;
- the cache data update module 220 may be specifically configured to: if the parsing result is the specific value information involved in the modification, directly update the target end database cache according to the parsing result; in the case that the parsing result is the modified operation identifier, The target end database is monitored according to the identifier, and when the monitoring operation corresponding to the identifier is detected, the target database is synchronized to the target database. After the database is updated, the target database cache is updated according to the content of the synchronized target database.
- the related functional modules of the data synchronization source device and the data synchronization target device may all be located in a physical entity (for example, a dedicated server) that is relatively independent from the application server, as shown in FIG. 3 . It may also be partially or completely located in the application server.
- the functions of the synchronization device on both sides of the data synchronization source end and the data synchronization target end are integrated on both sides.
- the corresponding system architecture can be simplified as shown in FIG. 4, and the interaction between the aforementioned synchronization device and the application server is simplified to the internal interaction of the application server.
- FIG. 10 is a schematic diagram of a hardware structure of a device for configuring the device provided by the present application.
- the device can include a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050.
- the processor 1010, the memory 1020, the input/output interface 1030, and the communication interface 1040 implement communication connections within the device with each other through the bus 1050.
- the processor 1010 can be implemented by using a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits for performing correlation. Programs to implement the technical solutions provided by the present application.
- a general-purpose CPU Central Processing Unit
- ASIC Application Specific Integrated Circuit
- the memory 1020 can be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like.
- the memory 1020 can store an operating system and other applications.
- the technical solution provided by the present application is implemented by software or firmware, the related program code is saved in the memory 1020 and executed by the processor 1010.
- the input/output interface 1030 is used to connect an input/output module to implement information input and output.
- the input/output/module can be configured as a component in the device (not shown) or externally connected to the device to provide the corresponding function.
- the input device may include a keyboard, a mouse, a touch screen, a microphone, various types of sensors, and the like, and the output device may include a display, a speaker, a vibrator, an indicator light, and the like.
- the communication interface 1040 is configured to connect a communication module (not shown) to implement communication interaction between the device and other devices.
- the communication module can communicate by wired means (such as USB, network cable, etc.), or can communicate by wireless means (such as mobile network, WIFI, Bluetooth, etc.).
- Bus 1050 includes a path for communicating information between various components of the device, such as processor 1010, memory 1020, input/output interface 1030, and communication interface 1040.
- the above device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040, and the bus 1050, in a specific implementation, the device may also include necessary for normal operation. Other components.
- the above-mentioned devices may also include only the components necessary for implementing the solution of the present application, and do not necessarily include all the components shown in the drawings.
- the present application can be implemented by means of software plus a necessary general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product in essence or in the form of a software product, which may be stored in a storage medium such as a ROM/RAM or a disk. , an optical disk, etc., includes instructions for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present application or portions of the embodiments.
- a computer device which may be a personal computer, server, or network device, etc.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Computational Linguistics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
- Synchronisation In Digital Transmission Systems (AREA)
- Hardware Redundancy (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims (23)
- 一种数据同步方法,其特征在于,该方法包括:数据同步源端确定源端数据库的数据修改后,针对本次数据修改生成实时通知,将所述实时通知发送至数据同步目标端,所述实时通知中,携带本次数据修改的相关信息;数据同步目标端接收到所述实时通知后,从所述实时通知中解析得到数据修改相关信息,根据解析结果对目标端数据库缓存进行更新。
- 根据权利要求1所述的方法,其特征在于,所述数据同步源端针对本次数据修改生成实时通知的步骤,包括:将本次修改涉及的具体数值信息写入所述实时通知中;所述数据同步目标端根据解析结果对目标端数据库缓存进行更新的步骤,包括:根据解析得到的修改涉及的具体数值信息,直接对目标端数据库缓存进行更新。
- 根据权利要求1所述的方法,其特征在于,所述数据同步源端针对本次数据修改生成实时通知的步骤,包括:将本次修改的操作标识写入所述实时通知中;所述数据同步目标端根据解析结果对目标端数据库缓存进行更新的步骤,包括:根据解析得到的修改操作标识,对目标端数据库进行监测,当监测到该标识对应的修改操作已经从源端数据库同步到目标端数据库后,根据同步后的目标端数据库内容,对目标端数据库缓存进行更新。
- 根据权利要求1所述的方法,其特征在于,所述数据同步源端针对本次数据修改生成实时通知的步骤,包括:判断本次修改的数据量是否超过预设的阈值;如果否,则将本次修改涉及的具体数值信息写入所述实时通知中;如果是,则将本次修改的操作标识写入所述实时通知中;所述数据同步目标端根据解析结果对目标端数据库缓存进行更新的步骤,包括:如果解析结果为修改涉及的具体数值信息,则直接根据解析结果对目 标端数据库缓存进行更新;如果解析结果为修改操作标识,则根据该标识对目标端数据库进行监测,当监测到该标识对应的修改操作已经从源端数据库同步到目标端数据库后,根据同步后的目标端数据库内容,对目标端数据库缓存进行更新。
- 一种数据同步方法,应用于数据同步源端,其特征在于,该方法包括:确定源端数据库的数据修改后,针对本次数据修改生成实时通知,所述实时通知中,携带本次数据修改的相关信息;将所述实时通知发送至数据同步目标端,以使得数据同步目标端接收到所述实时通知后,从所述实时通知中解析得到数据修改相关信息,根据解析结果对目标端数据库缓存进行更新。
- 根据权利要求5所述的方法,其特征在于,所述针对本次数据修改生成实时通知的步骤,包括:将本次修改涉及的具体数值信息写入所述实时通知中。
- 根据权利要求5所述的方法,其特征在于,所述针对本次数据修改生成实时通知的步骤,包括:将本次修改的操作标识写入所述实时通知中。
- 根据权利要求5所述的方法,其特征在于,所述针对本次数据修改生成实时通知的步骤,包括:判断本次修改的数据量是否超过预设的阈值;如果否,则将本次修改涉及的具体数值信息写入所述实时通知中;如果是,则将本次修改的操作标识写入所述实时通知中。
- 一种数据同步方法,应用于数据同步目标端,其特征在于,该方法包括:接收数据同步源端发送的实时通知;从所述实时通知中解析得到数据修改相关信息,根据解析结果对目标端数据库缓存进行更新;其中,所述实时通知,是在数据同步源端确定源端数据库的数据修改后,针对本次数据修改生成并发送,所述实时通知中,携带本次数据修改的相关信息。
- 根据权利要求9所述的方法,其特征在于,所述实时通知中包括本次修改涉及的具体数值信息;所述根据解析结果对目标端数据库缓存进行更新的步骤,包括:根据解析得到的修改涉及的具体数值信息,直接对目标端数据库缓存进行更新。
- 根据权利要求9所述的方法,其特征在于,所述实时通知中包括本次修改的操作标识;所述根据解析结果对目标端数据库缓存进行更新的步骤,包括:根据解析得到的修改操作标识,对目标端数据库进行监测,当监测到该标识对应的修改操作已经从源端数据库同步到目标端数据库后,根据同步后的目标端数据库内容,对目标端数据库缓存进行更新。
- 根据权利要求9所述的方法,其特征在于,所述实时通知中包括:本次修改涉及的具体数值信息、或本次修改的操作标识;所述针对本次数据修改生成实时通知的步骤,包括:判断本次修改的数据量是否超过预设的阈值;如果否,则将本次修改涉及的具体数值信息写入所述实时通知中;如果是,则将本次修改的操作标识写入所述实时通知中;所述数据同步目标端根据解析结果对目标端数据库缓存进行更新的步骤,包括:如果解析结果为修改涉及的具体数值信息,则直接根据解析结果对目标端数据库缓存进行更新;如果解析结果为修改操作标识,则根据该标识对目标端数据库进行监测,当监测到该标识对应的修改操作已经从源端数据库同步到目标端数据库后,根据同步后的目标端数据库内容,对目标端数据库缓存进行更新。
- 一种数据同步源端装置,其特征在于,该装置包括:实时通知生成模块、实时通知发送模块;所述实时通知生成模块用于在确定源端数据库的数据修改后,针对本次数据修改生成实时通知;所述实时通知中,携带本次数据修改的相关信息;所述实时通知发送模块用于将所述实时通知发送至数据同步目标端;以使得数据同步目标端接收到所述实时通知后,从所述实时通知中解析得到数据修改相关信息,根据解析结果对目标端数据库缓存进行更新。
- 根据权利要求13所述的装置,其特征在于,所述实时通知生成模块具体用于:在确定源端数据库的数据修改后,将本次修改涉及的具体数值信息写入所述实时通知中。
- 根据权利要求13所述的装置,其特征在于,所述实时通知生成模块具体用于:在确定源端数据库的数据修改后,将本次修改的操作标识写入所述实时通知中。
- 根据权利要求13所述的装置,其特征在于,所述实时通知生成模块具体用于:在确定源端数据库的数据修改后,判断本次修改的数据量是否超过预设的阈值;如果否,则将本次修改涉及的具体数值信息写入所述实时通知中;如果是,则将本次修改的操作标识写入所述实时通知中。
- 根据权利要求13所述的装置,其特征在于,数据同步源端装置配置在数据同步源端应用服务器中。
- 一种数据同步目标端装置,其特征在于,该装置包括:实时通知接收模块、缓存数据更新模块;所述实时通知接收模块用于接收数据同步源端发送的实时通知;所述缓存数据更新模块用于从所述实时通知中解析得到数据修改相关信息,根据解析结果对目标端数据库缓存进行更新;其中,所述实时通知,是数据同步源端在确定源端数据库的数据修改后,针对本次数据修改生成并发送,所述实时通知中,携带本次数据修改的相关信息。
- 根据权利要求18所述的装置,其特征在于,所述实时通知中包括本次修改涉及的具体数值信息;所述缓存数据更新模块具体用于:根据解析得到的修改涉及的具体数 值信息,直接对目标端数据库缓存进行更新。
- 根据权利要求18所述的装置,其特征在于,所述实时通知中包括本次修改的操作标识;所述缓存数据更新模块具体用于:根据解析得到的修改操作标识,对目标端数据库进行监测,当监测到该标识对应的修改操作已经从源端数据库同步到目标端数据库后,根据同步后的目标端数据库内容,对目标端数据库缓存进行更新。
- 根据权利要求18所述的装置,其特征在于,所述实时通知中包括:本次修改涉及的具体数值信息、或本次修改的操作标识;所述缓存数据更新模块具体用于:在解析结果为修改涉及的具体数值信息的情况下,直接根据解析结果对目标端数据库缓存进行更新;在解析结果为修改操作标识的情况下,根据该标识对目标端数据库进行监测,当监测到该标识对应的修改操作已经从源端数据库同步到目标端数据库后,根据同步后的目标端数据库内容,对目标端数据库缓存进行更新。
- 根据权利要求18所述的装置,其特征在于,数据同步目标端装置配置在数据同步目标端应用服务器中。
- 一种数据同步系统,其特征在于,该系统包括数据同步源端装置及数据同步目标端装置:所述数据同步源端装置包括:实时通知生成模块、实时通知发送模块;所述实时通知生成模块用于在确定源端数据库的数据修改后,针对本次数据修改生成实时通知;所述实时通知中,携带本次数据修改的相关信息;所述实时通知发送模块用于将所述实时通知发送至数据同步目标端;所述数据同步目标端装置包括:实时通知接收模块、缓存数据更新模块;所述实时通知接收模块用于接收所述实时通知,所述缓存数据更新模块用于从所述实时通知中解析得到数据修改相关信息,根据解析结果对目标端数据库缓存进行更新。
Priority Applications (9)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17740969.5A EP3407527B1 (en) | 2016-01-18 | 2017-01-09 | Method, device, and system for data synchronization |
SG11201806007RA SG11201806007RA (en) | 2016-01-18 | 2017-01-09 | Data synchronization method, apparatus, and system |
KR1020187023616A KR102153804B1 (ko) | 2016-01-18 | 2017-01-09 | 데이터 동기화 방법, 장치, 및 시스템 |
MYPI2018702458A MY185258A (en) | 2016-01-18 | 2017-01-09 | Method, device, and system for data system for data synchronization |
JP2018537667A JP6745884B2 (ja) | 2016-01-18 | 2017-01-09 | データ同期方法、装置及びシステム |
PH12018501520A PH12018501520A1 (en) | 2016-01-18 | 2018-07-16 | Method, device, and system for data synchronization |
US16/037,785 US11010404B2 (en) | 2016-01-18 | 2018-07-17 | Data synchronization method, apparatus, and system |
US16/719,402 US10754873B2 (en) | 2016-01-18 | 2019-12-18 | Data synchronization method, apparatus, and system |
US17/321,845 US20210271689A1 (en) | 2016-01-18 | 2021-05-17 | Data synchronization method, apparatus, and system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610031809.X | 2016-01-18 | ||
CN201610031809.XA CN106980625B (zh) | 2016-01-18 | 2016-01-18 | 一种数据同步方法、装置及系统 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/037,785 Continuation US11010404B2 (en) | 2016-01-18 | 2018-07-17 | Data synchronization method, apparatus, and system |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017124938A1 true WO2017124938A1 (zh) | 2017-07-27 |
Family
ID=59340589
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/070648 WO2017124938A1 (zh) | 2016-01-18 | 2017-01-09 | 一种数据同步方法、装置及系统 |
Country Status (10)
Country | Link |
---|---|
US (3) | US11010404B2 (zh) |
EP (1) | EP3407527B1 (zh) |
JP (1) | JP6745884B2 (zh) |
KR (1) | KR102153804B1 (zh) |
CN (1) | CN106980625B (zh) |
MY (1) | MY185258A (zh) |
PH (1) | PH12018501520A1 (zh) |
SG (1) | SG11201806007RA (zh) |
TW (1) | TW201730784A (zh) |
WO (1) | WO2017124938A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2021507377A (ja) * | 2017-12-14 | 2021-02-22 | インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation | データ・ストレージ・システムにおけるコピー・ソース・ツー・ターゲット管理 |
US11172023B2 (en) * | 2017-09-29 | 2021-11-09 | Wangsu Science & Technology Co., Ltd. | Data synchronization method and system |
Families Citing this family (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106980625B (zh) | 2016-01-18 | 2020-08-04 | 阿里巴巴集团控股有限公司 | 一种数据同步方法、装置及系统 |
US11550557B2 (en) | 2016-02-12 | 2023-01-10 | Nutanix, Inc. | Virtualized file server |
US11218418B2 (en) | 2016-05-20 | 2022-01-04 | Nutanix, Inc. | Scalable leadership election in a multi-processing computing environment |
CN106412071A (zh) * | 2016-10-08 | 2017-02-15 | 中国工商银行股份有限公司 | 一种数据同步方法及装置 |
US11562034B2 (en) | 2016-12-02 | 2023-01-24 | Nutanix, Inc. | Transparent referrals for distributed file servers |
US11568073B2 (en) | 2016-12-02 | 2023-01-31 | Nutanix, Inc. | Handling permissions for virtualized file servers |
US11294777B2 (en) | 2016-12-05 | 2022-04-05 | Nutanix, Inc. | Disaster recovery for distributed file servers, including metadata fixers |
US11281484B2 (en) | 2016-12-06 | 2022-03-22 | Nutanix, Inc. | Virtualized server systems and methods including scaling of file system virtual machines |
US11288239B2 (en) | 2016-12-06 | 2022-03-29 | Nutanix, Inc. | Cloning virtualized file servers |
CN108337303A (zh) * | 2018-01-24 | 2018-07-27 | 中国银联股份有限公司 | 一种数据同步方法和分布式系统 |
CN110309157A (zh) * | 2018-03-06 | 2019-10-08 | 北京京东尚科信息技术有限公司 | 一种数据同步更新方法和装置 |
CN108200219B (zh) * | 2018-03-13 | 2020-04-14 | Oppo广东移动通信有限公司 | 数据同步方法、装置、服务器及存储介质 |
CN108551484B (zh) * | 2018-04-23 | 2021-04-20 | 平安科技(深圳)有限公司 | 用户信息同步方法、装置、计算机装置及存储介质 |
CN109254997B (zh) * | 2018-08-27 | 2020-12-11 | 广州城市信息研究所有限公司 | 数据同步方法、系统、计算机设备和可读存储介质 |
CN109284300A (zh) * | 2018-08-31 | 2019-01-29 | 江苏龙虎网信息科技股份有限公司 | 一种客户端海量数据实时更新方法 |
US11770447B2 (en) | 2018-10-31 | 2023-09-26 | Nutanix, Inc. | Managing high-availability file servers |
CN109714394B (zh) * | 2018-12-05 | 2021-11-09 | 深圳店匠科技有限公司 | 跨境多服务端的信息同步方法、系统和存储介质 |
CN109814791B (zh) * | 2018-12-20 | 2020-11-13 | 东软集团股份有限公司 | 处理流程节点的方法、装置、存储介质及电子设备 |
CN109753511B (zh) * | 2018-12-28 | 2020-12-04 | 北京东方国信科技股份有限公司 | 一种大数据平台的跨地域实时同步方法及系统 |
CN109783580A (zh) * | 2019-01-24 | 2019-05-21 | 北京致远互联软件股份有限公司 | 数据同步方法及装置 |
CN110046167B (zh) * | 2019-02-18 | 2024-03-26 | 创新先进技术有限公司 | 数据更新方法和系统 |
CN109936481B (zh) * | 2019-03-22 | 2021-06-18 | 北京达佳互联信息技术有限公司 | 主从服务器切换方法、装置、电子设备及存储介质 |
CN110222065A (zh) * | 2019-05-29 | 2019-09-10 | 深圳市思迪信息技术股份有限公司 | 基于移动平台的机房站点更新方法及系统 |
KR102211403B1 (ko) * | 2019-06-19 | 2021-02-03 | 주식회사 코비젼 | 다중 웹서버 환경의 공용자원 동기화 시스템 |
CN110633324B (zh) * | 2019-09-18 | 2022-07-26 | 中化信息技术有限公司 | 用于同步数据的方法、装置、电子设备和计算机可读介质 |
CN110990200B (zh) * | 2019-11-26 | 2022-07-05 | 苏宁云计算有限公司 | 一种基于多活数据中心的流量切换方法及装置 |
CN111125247A (zh) * | 2019-12-06 | 2020-05-08 | 北京浪潮数据技术有限公司 | 一种redis客户端缓存方法、装置、设备及存储介质 |
CN111061768A (zh) * | 2019-12-23 | 2020-04-24 | 珠海格力电器股份有限公司 | 数据处理方法及系统 |
CN111162995A (zh) * | 2019-12-26 | 2020-05-15 | 苏州浪潮智能科技有限公司 | 一种数据变更通知方法、装置、设备及可读存储介质 |
US11500850B1 (en) * | 2020-02-26 | 2022-11-15 | Snap Inc. | Synchronizing content with third-party application |
CN111464332B (zh) * | 2020-03-06 | 2023-02-24 | 中国人民财产保险股份有限公司 | 容灾方法、装置及设备 |
CN113556371B (zh) * | 2020-04-26 | 2022-09-30 | 深信服科技股份有限公司 | 一种数据同步方法、系统、设备及计算机可读存储介质 |
US11768809B2 (en) | 2020-05-08 | 2023-09-26 | Nutanix, Inc. | Managing incremental snapshots for fast leader node bring-up |
CN112069256A (zh) * | 2020-08-27 | 2020-12-11 | 苏州浪潮智能科技有限公司 | 一种服务器集群上数据同步装置及其同步方法 |
CN112559025A (zh) * | 2020-12-16 | 2021-03-26 | 中国人寿保险股份有限公司 | 配置信息更新同步方法及设备 |
CN112905694A (zh) * | 2021-02-05 | 2021-06-04 | 广州虎牙科技有限公司 | 数据同步方法、装置、服务器及存储介质 |
CN115150411A (zh) * | 2021-03-31 | 2022-10-04 | 华为技术有限公司 | 数据同步的方法和装置 |
CN113656366B (zh) * | 2021-08-03 | 2024-05-03 | 北京数码大方科技股份有限公司 | 电子仓库的数据处理方法和装置 |
US20230066137A1 (en) | 2021-08-19 | 2023-03-02 | Nutanix, Inc. | User interfaces for disaster recovery of distributed file servers |
CN113992680B (zh) * | 2021-11-10 | 2024-02-02 | 中国工商银行股份有限公司 | 应用于分布式多活系统的调度方法、装置、设备及介质 |
CN113986909B (zh) * | 2021-12-24 | 2022-04-22 | 畅捷通信息技术股份有限公司 | 一种反向记录同步状态的实时数据同步方法、系统及介质 |
CN114415984B (zh) * | 2022-03-31 | 2022-08-16 | 阿里云计算有限公司 | 数据处理方法及装置 |
CN114722046A (zh) * | 2022-04-18 | 2022-07-08 | 聚好看科技股份有限公司 | 一种服务器及首页缓存数据分版本生成方法 |
CN116561089B (zh) * | 2023-07-10 | 2023-09-19 | 成都泛联智存科技有限公司 | 数据同步方法、装置、客户端和计算机可读存储介质 |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6792436B1 (en) * | 2000-02-11 | 2004-09-14 | Persistence Software, Inc. | Method for synchronizing multiple software caches in a memory |
CN101188566A (zh) * | 2007-12-13 | 2008-05-28 | 沈阳东软软件股份有限公司 | 一种集群环境下数据缓存同步的方法及系统 |
CN101291342A (zh) * | 2008-06-18 | 2008-10-22 | 中兴通讯股份有限公司 | 一种分布式体系中的数据同步方法及系统 |
CN103138912A (zh) * | 2011-12-05 | 2013-06-05 | 阿里巴巴集团控股有限公司 | 数据同步方法及系统 |
CN103581262A (zh) * | 2012-08-06 | 2014-02-12 | 腾讯科技(深圳)有限公司 | 一种主备数据同步方法、装置和系统 |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7644125B2 (en) * | 2000-09-11 | 2010-01-05 | Ianywhere Solutions, Inc. | Method, system, and computer program product for synchronization of similar data objects with event information |
JP3983516B2 (ja) * | 2001-10-25 | 2007-09-26 | 株式会社日立製作所 | 記憶装置システム |
EP1459213B1 (en) * | 2001-11-15 | 2017-05-10 | Good Technology Holdings Limited | System and methods for asychronous synchronization |
US7162472B2 (en) * | 2003-06-24 | 2007-01-09 | Microsoft Corporation | System and method for database change notification |
US7716377B2 (en) * | 2005-05-25 | 2010-05-11 | Harris Steven T | Clustering server providing virtual machine data sharing |
JP4806037B2 (ja) * | 2009-01-26 | 2011-11-02 | 株式会社東芝 | データ記憶システム及び非同期レプリケーション方法 |
US8037136B2 (en) * | 2009-03-11 | 2011-10-11 | Business Objects Software Ltd | Tracking a state of a document accessible over a computer network |
US8756195B2 (en) * | 2009-08-27 | 2014-06-17 | The Boeing Company | Universal delta set management |
US8321392B2 (en) * | 2009-12-30 | 2012-11-27 | Sybase, Inc. | Pending state management for mobile business objects |
US20120028660A1 (en) * | 2010-07-28 | 2012-02-02 | Matthew Stafford | Method and apparatus for notifying devices of new messages |
CN102346740B (zh) * | 2010-08-02 | 2016-08-10 | 联想(北京)有限公司 | 一种文件同步方法、电子设备和同步系统 |
CN102741843B (zh) * | 2011-03-22 | 2014-03-26 | 青岛海信传媒网络技术有限公司 | 从数据库中读取数据的方法及装置 |
CN102279880B (zh) * | 2011-07-28 | 2014-07-16 | 赵香芳 | 一种实时更新缓存的方法和系统 |
US20140229435A1 (en) * | 2013-01-27 | 2014-08-14 | Travel Holdings, Inc. | In-memory real-time synchronized database system and method |
US9020893B2 (en) * | 2013-03-01 | 2015-04-28 | Datadirect Networks, Inc. | Asynchronous namespace maintenance |
US10747746B2 (en) * | 2013-04-30 | 2020-08-18 | Amazon Technologies, Inc. | Efficient read replicas |
JP2015162091A (ja) * | 2014-02-27 | 2015-09-07 | 富士通株式会社 | 記憶制御装置、ストレージシステム、記憶制御方法、および記憶制御プログラム |
WO2015152956A1 (en) * | 2014-03-31 | 2015-10-08 | Oracle International Corporation | Infrastructure for synchronization of mobile device with mobile cloud service |
CN106980625B (zh) | 2016-01-18 | 2020-08-04 | 阿里巴巴集团控股有限公司 | 一种数据同步方法、装置及系统 |
-
2016
- 2016-01-18 CN CN201610031809.XA patent/CN106980625B/zh active Active
- 2016-12-27 TW TW105143378A patent/TW201730784A/zh unknown
-
2017
- 2017-01-09 KR KR1020187023616A patent/KR102153804B1/ko active IP Right Grant
- 2017-01-09 MY MYPI2018702458A patent/MY185258A/en unknown
- 2017-01-09 JP JP2018537667A patent/JP6745884B2/ja active Active
- 2017-01-09 EP EP17740969.5A patent/EP3407527B1/en active Active
- 2017-01-09 WO PCT/CN2017/070648 patent/WO2017124938A1/zh active Application Filing
- 2017-01-09 SG SG11201806007RA patent/SG11201806007RA/en unknown
-
2018
- 2018-07-16 PH PH12018501520A patent/PH12018501520A1/en unknown
- 2018-07-17 US US16/037,785 patent/US11010404B2/en active Active
-
2019
- 2019-12-18 US US16/719,402 patent/US10754873B2/en active Active
-
2021
- 2021-05-17 US US17/321,845 patent/US20210271689A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6792436B1 (en) * | 2000-02-11 | 2004-09-14 | Persistence Software, Inc. | Method for synchronizing multiple software caches in a memory |
CN101188566A (zh) * | 2007-12-13 | 2008-05-28 | 沈阳东软软件股份有限公司 | 一种集群环境下数据缓存同步的方法及系统 |
CN101291342A (zh) * | 2008-06-18 | 2008-10-22 | 中兴通讯股份有限公司 | 一种分布式体系中的数据同步方法及系统 |
CN103138912A (zh) * | 2011-12-05 | 2013-06-05 | 阿里巴巴集团控股有限公司 | 数据同步方法及系统 |
CN103581262A (zh) * | 2012-08-06 | 2014-02-12 | 腾讯科技(深圳)有限公司 | 一种主备数据同步方法、装置和系统 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11172023B2 (en) * | 2017-09-29 | 2021-11-09 | Wangsu Science & Technology Co., Ltd. | Data synchronization method and system |
JP2021507377A (ja) * | 2017-12-14 | 2021-02-22 | インターナショナル・ビジネス・マシーンズ・コーポレーションInternational Business Machines Corporation | データ・ストレージ・システムにおけるコピー・ソース・ツー・ターゲット管理 |
JP7058020B2 (ja) | 2017-12-14 | 2022-04-21 | インターナショナル・ビジネス・マシーンズ・コーポレーション | データ・ストレージ・システムにおけるコピー・ソース・ツー・ターゲット管理のための方法、システム及びコンピュータ・プログラム |
Also Published As
Publication number | Publication date |
---|---|
KR20180105675A (ko) | 2018-09-28 |
US20200125580A1 (en) | 2020-04-23 |
CN106980625A (zh) | 2017-07-25 |
US20180341693A1 (en) | 2018-11-29 |
SG11201806007RA (en) | 2018-08-30 |
KR102153804B1 (ko) | 2020-09-09 |
MY185258A (en) | 2021-04-30 |
US11010404B2 (en) | 2021-05-18 |
US10754873B2 (en) | 2020-08-25 |
US20210271689A1 (en) | 2021-09-02 |
PH12018501520A1 (en) | 2019-03-18 |
CN106980625B (zh) | 2020-08-04 |
EP3407527A4 (en) | 2019-07-03 |
TW201730784A (zh) | 2017-09-01 |
EP3407527A1 (en) | 2018-11-28 |
JP2019508796A (ja) | 2019-03-28 |
EP3407527B1 (en) | 2021-07-07 |
JP6745884B2 (ja) | 2020-08-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017124938A1 (zh) | 一种数据同步方法、装置及系统 | |
US20130238552A1 (en) | Systems and methods for synchronizing files in a networked communication system | |
US10877990B2 (en) | Remote database synchronization | |
WO2018014650A1 (zh) | 分布式数据库数据同步方法、相关装置及系统 | |
JP5548829B2 (ja) | 計算機システム、データ管理方法及びデータ管理プログラム | |
JP2015520435A (ja) | クラウド同期システムのためのテレメトリ・システム | |
CN110149382A (zh) | 数据同步的方法、系统、主服务器、同步客户端及介质 | |
US10826812B2 (en) | Multiple quorum witness | |
CN112260853B (zh) | 容灾切换方法、装置、存储介质及电子设备 | |
US20230098190A1 (en) | Data processing method, apparatus, device and medium based on distributed storage | |
WO2020224098A1 (zh) | 基于全局负载均衡的云存取方法、装置及存储介质 | |
CN107861691B (zh) | 一种多控存储系统的负载均衡方法和装置 | |
US11860849B2 (en) | Watermark-based techniques for change-data-capture | |
CN104980307A (zh) | 数据访问请求的处理方法、装置及数据库服务器 | |
CN110633046A (zh) | 一种分布式系统的存储方法、装置、存储设备及存储介质 | |
WO2019108461A1 (en) | Collaborative hosted virtual systems and methods | |
CN115580667B (zh) | 数据传输方法、装置、设备及存储介质 | |
CN116193481A (zh) | 一种5g核心网处理方法、装置、设备及介质 | |
CN112685486B (zh) | 数据库集群的数据管理方法、装置、电子设备及存储介质 | |
CN114928620A (zh) | 用户信息同步方法、装置、设备、存储介质和程序产品 | |
WO2021143039A1 (zh) | 一种确定分布式存储系统中的数据回滚时段的方法 | |
CN112925770A (zh) | 一种数据库扩容方法、装置、设备和介质 | |
WO2013096666A1 (en) | Network packet capture in emulated environments | |
CN118368296B (zh) | 一种跨数据中心的应用数据实时同步方法、装置和系统 | |
US11836058B2 (en) | System and method for automated secondary or disaster-recovery data center site failover |
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: 17740969 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12018501520 Country of ref document: PH |
|
ENP | Entry into the national phase |
Ref document number: 2018537667 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 20187023616 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020187023616 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017740969 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2017740969 Country of ref document: EP Effective date: 20180820 |