CN109542981B - Data synchronization system and method, electronic device and storage medium - Google Patents
Data synchronization system and method, electronic device and storage medium Download PDFInfo
- Publication number
- CN109542981B CN109542981B CN201811392424.1A CN201811392424A CN109542981B CN 109542981 B CN109542981 B CN 109542981B CN 201811392424 A CN201811392424 A CN 201811392424A CN 109542981 B CN109542981 B CN 109542981B
- Authority
- CN
- China
- Prior art keywords
- data
- node
- nodes
- data node
- server
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Transfer Between Computers (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a system and a method for data synchronization, electronic equipment and a storage medium, wherein the system comprises a plurality of data nodes; a first data node in the data nodes is used for acquiring synchronous data generated by an application node corresponding to the first data node by adopting a client component of the first data node, and sending the synchronous data to a server component of a second data node meeting preset conditions in the plurality of data nodes; the second data node in the data nodes is used for aggregating the received synchronous data by adopting the server side component of the second data node to obtain a synchronous data set, and the client side component of the second data node is used for sending the synchronous data set to the server side components of other data nodes except the second data node in the plurality of data nodes, so that the decoupling of the client side and the application node for data synchronization is realized, the reliability of the system is improved, the synchronous data is cached and locally, and the condition that the synchronous data is excessively dependent on the server side is avoided.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to a system and method for data synchronization, an electronic device, and a storage medium.
Background
At present, a plurality of application nodes are deployed in part of applications, and data synchronization needs to be performed among the plurality of application nodes to ensure normal operation of the applications.
In the prior art, a client for data synchronization is generally arranged in each application node, then the data of the application node is synchronized to a server by the client, and when certain data is needed, the application node can perform data query at the server through the client to acquire the data.
However, data in this way is centralized on the server, and is excessively dependent on the server, which affects the efficiency of data query, and the client is tightly coupled with the application node, and the client cannot independently perform data synchronization.
Disclosure of Invention
In view of the above, the present application is proposed to provide a system and method, an electronic device, a storage medium for data synchronization that overcome or at least partially solve the above problems, comprising:
a system for data synchronization, the system comprising a plurality of data nodes, each data node comprising a client component and a server component;
the first data node in the data nodes is used for acquiring synchronous data generated by an application node corresponding to the first data node by adopting a client component of the first data node, and sending the synchronous data to a server component of a second data node meeting preset conditions in the data nodes;
and the second data node in the data nodes is used for aggregating the received synchronous data by adopting a server side component of the second data node to obtain a synchronous data set, and sending the synchronous data set to server side components of other data nodes except the second data node in the plurality of data nodes by adopting a client side component of the second data node.
Optionally, when the system is a client/server architecture composed of a plurality of the data nodes, the second data node meeting the preset condition is a server node in the client/server architecture or a data node determined according to a determination instruction;
when the system is a point-to-point architecture formed by a plurality of data nodes, the second data node meeting the preset condition is a data node except the first data node in the plurality of data nodes.
Optionally, the first data node is decoupled from the application node, and the client component of the first data node is specifically configured to:
and after the application node writes synchronous data by adopting a predefined first file interface, acquiring the synchronous data by adopting the first file interface.
Optionally, the server-side component of the second data node communicates with the client-side component of the second data node by using a predefined second file interface, and the second file interface is the same as the first file interface in type.
Optionally, under a client/server architecture, application nodes corresponding to other data nodes except the second data node form a load balancing cluster;
under the point-to-point architecture, the application nodes corresponding to the plurality of data nodes form a load balancing cluster.
Optionally, the synchronization data is data with a usage probability greater than a preset threshold.
A method of data synchronization involving a plurality of data nodes, each data node comprising a client component and a server component, the method comprising:
a first data node in the data nodes adopts a client component of the first data node to acquire synchronous data generated by an application node corresponding to the first data node;
a first data node in the data nodes sends the synchronous data to a service end component of a second data node which meets a preset condition in the data nodes;
and a second data node in the data nodes is used for aggregating the received synchronous data by adopting a server side component of the second data node to obtain a synchronous data set, and sending the synchronous data set to server side components of other data nodes except the second data node in the plurality of data nodes by adopting the client side component of the second data node.
A method of data synchronization involving a plurality of data nodes, each data node comprising a client component and a server component, the method comprising:
a second data node in the data nodes adopts a service end component of the second data node to aggregate the received synchronous data to obtain a synchronous data set; the synchronous data comprises synchronous data generated by a first data node in the data nodes by adopting a client component of the first data node, and the application node corresponding to the first data node;
and a second data node in the data nodes sends the synchronous data set to the service end components of other data nodes except the second data node in the plurality of data nodes by adopting the client end component of the second data node.
An electronic device comprising a processor, a memory and a computer program stored on the memory and being executable on the processor, the computer program, when executed by the processor, implementing the steps of the method of data synchronization as described above.
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 data synchronization as set forth above.
The application has the following advantages:
in an embodiment of the application, each data node in the system for setting data synchronization includes a client component and a server component, wherein a first data node in the data nodes is used for acquiring synchronization data generated by an application node corresponding to the first data node by using the client component of the first data node, and sending the synchronization data to the server component of a second data node satisfying a preset condition in the plurality of data nodes; the second data node in the data nodes is used for aggregating the received synchronous data by adopting the server side component of the second data node to obtain a synchronous data set, and the client side component of the second data node is used for sending the synchronous data set to the server side components of other data nodes except the second data node in the plurality of data nodes, so that the decoupling of the client side and the application node for data synchronization is realized, the reliability of the system is improved, the synchronous data is cached and locally, the excessive dependence on the server side is avoided, the safety of the data and the query efficiency are improved, and the occupation of network bandwidth is reduced.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings needed to be used in the description of the present application will be briefly introduced below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive labor.
Fig. 1 is a schematic structural diagram of a system for data synchronization according to an embodiment of the present application;
FIG. 2 is a flow chart illustrating steps of a method for data synchronization according to an embodiment of the present application;
fig. 3 is a flowchart illustrating steps of another method for data synchronization according to an embodiment of the present application.
Detailed Description
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, the present application is described in further detail with reference to the accompanying drawings and the detailed description. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, a schematic structural diagram of a data synchronization system provided by an embodiment of the present application is shown, where the system may include a plurality of data nodes, and the plurality of data nodes may include a first data node 101 and a second data node 102 that satisfies a preset condition.
In practical applications, the plurality of data nodes may constitute a Peer-to-Peer architecture (Peer-to-Peer, P2P) or a Client/Server architecture (Client/Server, C/S).
When the system is a client/server architecture composed of a plurality of data nodes, the first data node 101 may be a data node of the plurality of data nodes except a server node in the client/server architecture, and the second data node 102 satisfying the preset condition may be a server node in the client/server architecture or a data node determined according to the determination instruction.
When the system is a point-to-point architecture composed of a plurality of data nodes, the first data node 101 may be any one of the plurality of data nodes, and the second data node 102 satisfying the preset condition may be a data node other than the first data node 101 in the plurality of data nodes.
In an embodiment of the present application, in order to sufficiently decouple the system interior, the system may be componentized, and each data node may include a client component and a server component, as in fig. 1, a first data node 101 may include a client component 1011 and a server component 1012, and a second data node 102 may include a client component 1021 and a server component 1022.
Each node is explained in detail below:
a) the first data node 101 is configured to acquire, by using a client component 1011 of the first data node 101, synchronization data generated by an application node corresponding to the first data node 101, and send the synchronization data to a server component 1022 of a second data node 102 that meets a preset condition among the plurality of data nodes.
As an example, the synchronization data may be data with a usage probability greater than a preset threshold, i.e., hot spot data, such as Session data, and the usage probability may be calculated by a data type, a data access number, and the like.
In fact, there may be a plurality of first data nodes 101, each first data node 101 may have a corresponding application node, such as a game engine, a Web application, and the first data node 101 may be deployed on the same server as the corresponding application node.
Under the client/server architecture, application nodes corresponding to other data nodes except the second data node 102 may form a load balancing cluster, and under the peer-to-peer architecture, application nodes corresponding to a plurality of data nodes form a load balancing cluster.
When an application node generates synchronous data, the client component 1011 of the first data node 101 corresponding to the application node may obtain the synchronous data, and then may send the synchronous data to the server component 1022 of the second data node 102 that meets a preset condition by using Socket.
In an embodiment of the present application, the first data node 101 may be decoupled from the application node, and the client component 1011 of the first data node 101 is specifically configured to:
and after the application node writes the synchronous data in the predefined first file interface, acquiring the synchronous data by adopting the first file interface.
In a specific implementation, the first file interface may be predefined, then the Source (input end) of the client component 1011 of the first data node 101 may be set as the first file interface, the application node may write the synchronous data into the cache file by using the first file interface, and the client component 1011 of the first data node 101 may obtain the synchronous data from the cache file through the first file interface.
Correspondingly, the Sink (output end) of the client component 1011 of the first data node 101 may be set as the server component 1022 of the second data node 102, and specifically may be set as a Socket port monitored by the server component 1022 of the second data node 102.
In the embodiment of the application, because a file interface is adopted, the client component 1011 of the first data node 101 does not need to be embedded into a code layer of an application node, and the first data node 101 is independent of the application node, i.e., is decoupled from the application node, when the application node fails, the first data node 101 can continue to perform data synchronization, and after the application node fails and restarts, the application node can be ensured to normally operate.
b) The second data node 102 is configured to aggregate the received synchronized data by using a service end component 1022 of the second data node 102 to obtain a synchronized data set, and send the synchronized data set to service end components of other data nodes except the second data node 102 in the plurality of data nodes by using a client component 1021 of the second data node 102.
After receiving the synchronization data sent by each first data node 101, the service end component 1022 of the second data node 102 may aggregate the received synchronization data, and reserve only one copy of the same synchronization data, so as to obtain a synchronization data set.
For example, the synchronization data is Session data, and the service end component 1022 of the second data node 102 may perform Session parsing on the received Session data, for example, parse the Session data in asn.1 format, and then aggregate the Session data, and insert the aggregated Session data into a preset red-black tree.
After obtaining the synchronized data set, the second data node 102 may employ the client component 1021 of the second data node 102 to send the synchronized data set to a server-side component of a data node of the plurality of data nodes other than the second data node 102.
In an embodiment of the present application, a second file interface may be predefined, where the second file interface may be the same as the first file interface in type, and specifically may be the same as a data format corresponding to the interface, and a predefined second file interface is used for communication between the server component 1022 of the second data node 102 and the client component 1021 of the second data node 102.
That is, the Source of the service end component 1021 of the second data node 102 may be set as the client component 1011 of the first data node 101, and specifically may be set as a Socket port corresponding to the client component 1011 of the first data node 101, so as to perform Socket monitoring, and the Sink of the service end component 1021 of the second data node 102 may be set as the second file interface.
The Source of the client component 1021 of the second data node 102 may be configured as a second file interface, and the Sink of the client component 1021 of the second data node 102 may be configured as a server-side component of other data nodes than the second data node 102.
In an embodiment of the present application, the third file interface may be predefined, and the type of the third file interface is the same as that of the first file interface.
The Source of the service-side components of the data nodes other than the second data node 102, including the service-side component 1012 of the first data node 101, may be set as the client-side component 1021 of the second data node 102, and the Sink of the service-side components of the data nodes other than the second data node 102 may be set as the third file interface.
After receiving the synchronized data set, the server components of the other data nodes except the second data node 102 may store the synchronized data set in the local cache through the third file interface, and the application node may query the synchronized data set from the local cache through the third file interface, so that even when the second data node 102 fails, the application node corresponding to each data node may continue to use the synchronized data set in the local cache to ensure normal operation of the application.
In an embodiment of the application, each data node in the system for setting data synchronization includes a client component and a server component, wherein a first data node in the data nodes is used for acquiring synchronization data generated by an application node corresponding to the first data node by using the client component of the first data node, and sending the synchronization data to the server component of a second data node satisfying a preset condition in the plurality of data nodes; the second data node in the data nodes is used for aggregating the received synchronous data by adopting the server side component of the second data node to obtain a synchronous data set, and the client side component of the second data node is used for sending the synchronous data set to the server side components of other data nodes except the second data node in the plurality of data nodes, so that the decoupling of the client side and the application node for data synchronization is realized, the reliability of the system is improved, the synchronous data is cached and locally, the excessive dependence on the server side is avoided, the safety of the data and the query efficiency are improved, and the occupation of network bandwidth is reduced.
Referring to fig. 2, a flowchart illustrating steps of a method for data synchronization according to an embodiment of the present application is shown, where the method involves a plurality of data nodes, each of which may include a client component and a server component, and specifically may include the following steps:
step 202, a first data node in the data nodes sends synchronization data to a service end component of a second data node satisfying a preset condition in the plurality of data nodes.
The second data node in the data nodes is used for aggregating the received synchronous data by adopting a server side component of the second data node to obtain a synchronous data set, and sending the synchronous data set to the server side components of other data nodes except the second data node in the plurality of data nodes by adopting a client side component of the second data node.
When an application node generates synchronous data, a client component of a first data node corresponding to the application node can acquire the synchronous data, and then Socket can be adopted to send the synchronous data to a server component of a second data node meeting preset conditions.
After receiving the synchronization data sent by each first data node, the server end component of the second data node may aggregate the received synchronization data, and reserve only one copy of the same synchronization data to obtain a synchronization data set.
After obtaining the synchronized data set, the second data node may send the synchronized data set to a server-side component of another data node of the plurality of data nodes other than the second data node using the client-side component of the second data node.
Referring to fig. 3, a flowchart illustrating steps of a method for data synchronization according to an embodiment of the present application is shown, where the method involves a plurality of data nodes, each of which may include a client component and a server component, and specifically may include the following steps:
the synchronous data comprises the synchronous data generated by the application node corresponding to the first data node, wherein the first data node in the data nodes adopts the client component of the first data node.
In step 302, a second data node of the plurality of data nodes sends the synchronized data set to server-side components of other data nodes except the second data node using a client-side component of the second data node.
When an application node generates synchronous data, a client component of a first data node corresponding to the application node can acquire the synchronous data, and then Socket can be adopted to send the synchronous data to a server component of a second data node meeting preset conditions.
After receiving the synchronization data sent by each first data node, the server end component of the second data node may aggregate the received synchronization data, and reserve only one copy of the same synchronization data to obtain a synchronization data set.
After obtaining the synchronized data set, the second data node may send the synchronized data set to a server-side component of another data node of the plurality of data nodes other than the second data node using the client-side component of the second data node.
It should be noted that, as for the method embodiment, since it is basically similar to the system embodiment, the description is relatively simple, and for the relevant points, reference may be made to partial description of the system embodiment.
Also, while method embodiments have been described for simplicity of explanation as a series of acts, it will be appreciated by those skilled in the art that the claimed embodiments are not limited by the illustrated ordering of acts, as some steps may occur in other orders or concurrently with other steps in accordance with the claimed embodiments. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no particular act is required of the embodiments of the application.
An embodiment of the present application also provides an electronic device, which may include a processor, a memory, and a computer program stored on the memory and capable of running on the processor, wherein the computer program, when executed by the processor, implements the steps of the method for data synchronization as above.
An embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements the steps of the above method for data synchronization.
The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.
As will be appreciated by one of skill in the art, embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present application have been described, additional variations and modifications of these embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the true scope of the embodiments of the application.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.
The above detailed description is given to a system and method for data synchronization, an electronic device, and a storage medium, and specific examples are applied in this document to explain the principles and embodiments of the present application, and the descriptions of the above embodiments are only used to help understand the method and the core ideas of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (9)
1. A system for data synchronization, the system comprising a plurality of data nodes, each data node comprising a client component and a server component;
the first data node in the data nodes is used for acquiring synchronous data generated by an application node corresponding to the first data node by adopting a client component of the first data node, and sending the synchronous data to a server component of a second data node meeting preset conditions in the data nodes;
the second data node in the data nodes is used for aggregating the received synchronous data by adopting a server side component of the second data node to obtain a synchronous data set, and sending the synchronous data set to the server side components of other data nodes except the second data node in the plurality of data nodes by adopting the client side component of the second data node;
when the system is a client/server architecture formed by a plurality of data nodes, the second data node meeting the preset condition is a server node in the client/server architecture or a data node determined according to a determination instruction;
when the system is a point-to-point architecture formed by a plurality of data nodes, the second data node meeting the preset condition is a data node except the first data node in the plurality of data nodes.
2. The system of claim 1, wherein the first data node is decoupled from the application node, and wherein the client component of the first data node is specifically configured to:
and after the application node writes synchronous data by adopting a predefined first file interface, acquiring the synchronous data by adopting the first file interface.
3. The system of claim 2, wherein the server component of the second data node communicates with the client component of the second data node using a predefined second file interface, the second file interface being of the same type as the first file interface.
4. The system of claim 1,
under the client/server architecture, application nodes corresponding to other data nodes except the second data node form a load balancing cluster;
under the point-to-point architecture, the application nodes corresponding to the plurality of data nodes form a load balancing cluster.
5. The system of claim 1, wherein the synchronization data is data having a probability of use greater than a predetermined threshold.
6. A method of data synchronization involving a plurality of data nodes, each data node comprising a client component and a server-side component, the method comprising:
a first data node in the data nodes adopts a client component of the first data node to acquire synchronous data generated by an application node corresponding to the first data node;
a first data node in the data nodes sends the synchronous data to a service end component of a second data node which meets a preset condition in the data nodes;
a second data node in the data nodes is configured to aggregate the received synchronous data by using a server side component of the second data node to obtain a synchronous data set, and send the synchronous data set to server side components of other data nodes except the second data node in the plurality of data nodes by using the client side component of the second data node;
when a plurality of data nodes form a client/server architecture, the second data node meeting the preset condition is a server node in the client/server architecture or a data node determined according to a determination instruction; when a plurality of data nodes form a point-to-point architecture, the second data node meeting the preset condition is a data node except the first data node in the plurality of data nodes.
7. A method of data synchronization involving a plurality of data nodes, each data node comprising a client component and a server-side component, the method comprising:
a second data node meeting preset conditions in the data nodes adopts a server end component of the second data node to aggregate received synchronous data to obtain a synchronous data set; the synchronous data comprises synchronous data generated by a first data node in the data nodes by adopting a client component of the first data node, and the application node corresponding to the first data node;
a second data node of the data nodes sends the synchronous data set to server end components of other data nodes except the second data node by adopting a client end component of the second data node;
when a plurality of data nodes form a client/server architecture, the second data node meeting the preset condition is a server node in the client/server architecture or a data node determined according to a determination instruction; when a plurality of data nodes form a point-to-point architecture, the second data node meeting the preset condition is a data node except the first data node in the plurality of data nodes.
8. An electronic device, comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, the computer program, when executed by the processor, implementing the steps of the method of data synchronization according to any of claims 6 to 7.
9. 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 data synchronization according to any one of claims 6 to.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811392424.1A CN109542981B (en) | 2018-11-21 | 2018-11-21 | Data synchronization system and method, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811392424.1A CN109542981B (en) | 2018-11-21 | 2018-11-21 | Data synchronization system and method, electronic device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109542981A CN109542981A (en) | 2019-03-29 |
| CN109542981B true CN109542981B (en) | 2020-10-27 |
Family
ID=65848813
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811392424.1A Active CN109542981B (en) | 2018-11-21 | 2018-11-21 | Data synchronization system and method, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109542981B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111651522B (en) * | 2020-05-27 | 2023-05-19 | 泰康保险集团股份有限公司 | Data synchronization method and device |
| CN113590475B (en) * | 2021-07-13 | 2024-05-31 | 北京快乐茄信息技术有限公司 | Joint debugging test method and joint debugging test device of online development platform |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101771723A (en) * | 2010-01-05 | 2010-07-07 | 深圳中兴网信科技有限公司 | Data synchronization method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7890091B2 (en) * | 2003-05-08 | 2011-02-15 | Good Technology, Inc. | Collaborative data and intelligent synchronization for mobile devices |
| US20070168352A1 (en) * | 2005-12-30 | 2007-07-19 | Sap Ag | Middleware scalability with distributed caching |
| CN101344882B (en) * | 2007-07-10 | 2010-06-02 | 中国移动通信集团公司 | Data query method, insertion method and deletion method |
| CN106339408B (en) * | 2016-08-10 | 2019-08-23 | 深圳中兴网信科技有限公司 | Method of data synchronization, data synchronization unit and server |
-
2018
- 2018-11-21 CN CN201811392424.1A patent/CN109542981B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101771723A (en) * | 2010-01-05 | 2010-07-07 | 深圳中兴网信科技有限公司 | Data synchronization method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109542981A (en) | 2019-03-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10764369B2 (en) | Data storage method and server applicable to distributed server cluster | |
| CN107483627B (en) | File distribution method, file download method, distribution server, client and system | |
| US10681127B2 (en) | File upload method and system | |
| CN110929880A (en) | Method and device for federated learning and computer readable storage medium | |
| CN107291750B (en) | Data migration method and device | |
| KR101871383B1 (en) | Method and system for using a recursive event listener on a node in hierarchical data structure | |
| CN109218349A (en) | A kind of method and device of management server cluster | |
| US9173006B2 (en) | Method for live broadcasting in a distributed network and apparatus for the same | |
| CN108062243B (en) | Execution plan generation method, task execution method and device | |
| WO2015188501A1 (en) | Configuration file updating method, device, system and computer storage medium | |
| CN114328618B (en) | Cache data synchronization method, device, equipment and storage medium | |
| CN106817387B (en) | Data synchronization method, device and system | |
| CN111400777B (en) | Network storage system, user authentication method, device and equipment | |
| CN112612769B (en) | File processing method, device and storage medium | |
| CN109542981B (en) | Data synchronization system and method, electronic device and storage medium | |
| US10802896B2 (en) | Rest gateway for messaging | |
| CN111064626A (en) | Configuration updating method, device, server and readable storage medium | |
| CN109257448B (en) | Session information synchronization method and device, electronic equipment and storage medium | |
| CN114900449B (en) | Resource information management method, system and device | |
| CN108111630B (en) | Zookeeper cluster system and connection method and system thereof | |
| CN110798358B (en) | Distributed service identification method and device, computer readable medium and electronic equipment | |
| CN110233791B (en) | Data deduplication method and device | |
| US8250140B2 (en) | Enabling connections for use with a network | |
| CN109344202B (en) | Data synchronization method and management node | |
| EP3349416A1 (en) | Relationship chain processing method and system, 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |