CN112199381A - Data synchronization system, method and device, electronic equipment and storage medium - Google Patents
Data synchronization system, method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112199381A CN112199381A CN202011066464.4A CN202011066464A CN112199381A CN 112199381 A CN112199381 A CN 112199381A CN 202011066464 A CN202011066464 A CN 202011066464A CN 112199381 A CN112199381 A CN 112199381A
- Authority
- CN
- China
- Prior art keywords
- data
- version number
- updating
- message
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- 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/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The embodiment of the invention provides a data synchronization system, a data synchronization method, a data synchronization device, electronic equipment and a storage medium, wherein after updating operation is performed on locally stored first data, front-end equipment updates the version number of the first data according to a preset version number updating rule to obtain a target version number; generating a data updating message carrying a target version number; sending the data updating message to the back-end equipment; the back-end equipment receives the data updating message; determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message; judging whether the version of the second data is earlier than that of the first data or not according to a preset version number updating rule, the version number of the second data and the target version number; if so, updating operation is carried out on the second data according to the data updating message, and the version number of the second data is updated to the target version number, so that the possibility of data updating being covered is reduced, and data synchronization in the front-end equipment and the back-end equipment is realized.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a data synchronization system, method, apparatus, electronic device, and storage medium.
Background
In the operation process of the website, each front-end device is required to send data to the back-end device for aggregation, a user can update the data in the front-end device, and after the front-end device updates the data, the updated data needs to be synchronized to the back-end device, so that the consistency of the data in the front-end device and the back-end device is maintained.
In the prior art, the mode of data synchronization between the front-end device and the back-end device is as follows: firstly, the front-end equipment executes updating operation on first data stored locally according to a received data updating request, generates a data updating message carrying a first time stamp, and sends the data updating message to the back-end equipment, wherein the first time stamp indicates the time for the front-end equipment to execute the updating operation on the first data; then, the back-end equipment judges whether the time indicated by the first timestamp is after the time indicated by a second timestamp, wherein the second timestamp indicates the latest updating time of second data corresponding to the first data and locally stored by the back-end equipment; if the second data version is the same as the first data version, the back-end equipment updates the second data according to the data updating message.
However, the first timestamp and the second timestamp are only accurate to the second level, if the first data is updated in the same second for multiple times, multiple data update messages carrying the same first timestamp may be generated, the back-end device cannot judge the sequence of the multiple data update messages, and the situation that the data update messages sent later are processed first and then the data update messages sent earlier are processed may occur, so that the data update is covered, and thus, the data synchronization in the front-end device and the back-end device fails.
Disclosure of Invention
Embodiments of the present invention provide a data synchronization system, method, apparatus, electronic device, and storage medium, so as to reduce the possibility of data update being covered and implement data synchronization in a front-end device and a back-end device. The specific technical scheme is as follows:
in a first aspect of the present invention, there is provided a data synchronization system, the system including: a back-end device and at least one front-end device, wherein,
the front-end equipment is used for updating the version number of the first data according to a preset version number updating rule after the updating operation is executed on the locally stored first data, so as to obtain a target version number; generating a data updating message carrying the target version number, wherein the data updating message is used for indicating the first data and the updating operation; sending the data updating message to the back-end equipment;
the back-end equipment is used for receiving the data updating message; determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message; judging whether the version of the second data is earlier than that of the first data or not according to the preset version number updating rule, the version number of the second data and the target version number; and if so, executing the updating operation on the second data according to the data updating message, and updating the version number of the second data into the target version number.
Optionally, the version number of the first data is a number;
the front-end equipment is specifically used for adding the version number of the first data to a preset value to obtain a target version number;
the back-end device is specifically configured to determine whether the version number of the second data is smaller than the target version number; and if so, judging that the version of the second data is earlier than that of the first data.
Optionally, the first data is stored in a data table, and the data update message is further used to indicate the data table;
the front-end device is specifically configured to query, after performing an update operation on the first data, a version number of the data table as the version number of the first data;
the back-end device is specifically configured to use the version number of the locally stored data table as the version number of the second data according to the data update message and the corresponding relationship between the data table and the version number stored in advance; updating the version number of the locally stored data table to the target version number in a case where it is determined that the version of the second data is earlier than the first data.
Optionally, the correspondence between the data table and the version number is stored in the backend device in a json format.
Optionally, the front-end device is specifically configured to send the data update message to the back-end device through a message middleware.
Optionally, the backend device is further configured to discard the data update message when determining that the version of the second data is not earlier than the version of the first data.
In a second aspect of the present invention, there is also provided a data synchronization method applied to a front-end device, where the method includes:
after the updating operation is carried out on the locally stored first data, updating the version number of the first data according to a preset version number updating rule to obtain a target version number;
generating a data updating message carrying the target version number, wherein the data updating message is used for indicating the first data and the updating operation;
and sending the data updating message to back-end equipment so that the back-end equipment determines the version number of second data corresponding to the first data and stored locally according to the data updating message, and executes the updating operation on the second data according to the data updating message and updates the version number of the second data to the target version number under the condition that the version of the second data is judged to be earlier than that of the first data according to the preset version number updating rule, the version number of the second data and the target version number.
Optionally, the updating the version number of the first data according to a preset version number updating rule to obtain a target version number includes:
and adding the version number of the first data to a preset value to obtain a target version number.
Optionally, the first data is stored in a data table, the data update message is further used to indicate the data table, and before the version number of the second data is updated according to a preset version number update rule to obtain a target version number, the method further includes:
and inquiring the version number of the data table to which the first data belongs as the version number of the first data.
Optionally, the sending the data update message to the backend device includes:
and sending the data updating message to the back-end equipment through message middleware.
In a third aspect of the present invention, there is further provided a data synchronization method applied to a backend device, where the method includes:
receiving a data updating message which is sent by front-end equipment and carries a target version number, wherein the data updating message is used for indicating first data locally stored by the front-end equipment and updating operation executed on the first data, and the target version number is obtained by updating the version number of the first data according to a preset version number updating rule after the front-end equipment executes the updating operation on the first data;
determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message;
judging whether the version of the second data is earlier than that of the first data or not according to the preset version number updating rule, the version number of the second data and the target version number;
and if so, executing the updating operation on the second data according to the data updating message, and updating the version number of the second data to the target version number.
Optionally, the version number of the first data is a number, and the target version number is the sum of the version number of the first data and a preset value;
the determining whether the version of the second data is earlier than the version of the first data according to the preset version number update rule, the version number of the second data and the target version number includes:
judging whether the version number of the second data is smaller than the target version number; if the first data is less than the second data, judging that the version of the second data is earlier than that of the first data; and if not, judging that the version of the second data is not earlier than the first data.
Optionally, the storing the first data in a data table, where the data update message is further used to indicate the data table, and the determining, according to the data update message, a version number of second data corresponding to the first data, which is locally stored, includes:
according to the data updating message and the corresponding relation between the pre-stored data table and the version number, taking the version number of the locally stored data table as the version number of the second data;
the updating the version number of the second data to the target version number includes:
and updating the version number of the locally stored data table to the target version number.
Optionally, the correspondence between the data table and the version number is stored in the backend device in a json format.
Optionally, in a case that the version of the second data is not earlier than the version of the first data, the method further includes:
discarding the data update message.
In a fourth aspect of the present invention, there is also provided a data synchronization apparatus applied to a front-end device, the apparatus including:
the updating module is used for updating the version number of the first data according to a preset version number updating rule after the updating operation is executed on the locally stored first data to obtain a target version number;
a generating module, configured to generate a data update message carrying the target version number, where the data update message is used to indicate the first data and the update operation;
and the sending module is used for sending the data updating message to back-end equipment so that the back-end equipment determines the version number of second data corresponding to the first data and stored locally according to the data updating message, and executes the updating operation on the second data according to the data updating message and updates the version number of the second data to the target version number under the condition that the version of the second data is judged to be earlier than that of the first data according to the preset version number updating rule, the version number of the second data and the target version number.
In a fifth aspect of the present invention, there is also provided a data synchronization apparatus applied to a backend device, the apparatus including:
the device comprises a receiving module and a processing module, wherein the receiving module is used for receiving a data updating message which is sent by front-end equipment and carries a target version number, the data updating message is used for indicating first data which are locally stored by the front-end equipment and updating operation which is executed on the first data, and the target version number is obtained by updating the version number of the first data according to a preset version number updating rule after the front-end equipment executes the updating operation on the first data;
the determining module is used for determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message;
the judging module is used for judging whether the version of the second data is earlier than the first data according to the preset version number updating rule, the version number of the second data and the target version number;
and the synchronization module is used for executing the updating operation on the second data according to the data updating message and updating the version number of the second data to the target version number under the condition that the version of the second data is earlier than that of the first data.
In a sixth aspect of the present invention, there is also provided an electronic device, including a processor, a communication interface, a memory and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the communication bus;
a memory for storing a computer program;
and the processor is used for realizing any one of the data synchronization methods when executing the program stored in the memory.
In a seventh aspect of the present invention, there is also provided a storage medium having a computer program stored thereon, wherein the computer program is configured to implement any one of the above-mentioned data synchronization methods when executed by a processor.
In yet another aspect of the present invention, there is also provided a computer-readable storage medium having stored therein instructions, which when run on a computer, cause the computer to execute any of the above-described data synchronization methods.
In yet another aspect of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform any of the above described data synchronization methods.
According to the data synchronization system, the method and the device, the electronic device and the storage medium provided by the embodiment of the invention, after the front-end device executes the updating operation on the locally stored first data, the version number of the first data is updated according to the updating rule of the preset version number to obtain the target version number; generating a data updating message carrying a target version number, wherein the data updating message is used for indicating first data and updating operation; sending the data updating message to the back-end equipment; the back-end equipment receives the data updating message; determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message; judging whether the version of the second data is earlier than that of the first data or not according to a preset version number updating rule, the version number of the second data and the target version number; if so, updating operation is carried out on the second data according to the data updating message, and the version number of the second data is updated to the target version number.
That is to say, each time the front-end device executes an update operation on the locally stored first data, the version number of the first data is updated, so that the back-end device can compare the version number of the updated first data with the version number of the locally stored second data, determine the sequence of the version of the second data and the version of the updated first data, and execute the update operation on the second data under the condition that the version of the second data is earlier than the version of the updated first data, thereby reducing the possibility of data update coverage and realizing data synchronization in the front-end device and the back-end device.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a system structure diagram of a data synchronization system according to an embodiment of the present invention;
fig. 2 is a timing diagram illustrating data synchronization performed by a data synchronization system according to an embodiment of the present invention;
FIG. 3 is a timing diagram illustrating data synchronization performed by another data synchronization system according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a data synchronization method according to an embodiment of the present invention;
fig. 5 is a flowchart of a data synchronization method applied to a front-end device according to an embodiment of the present invention;
fig. 6 is a flowchart of a data synchronization method applied to a backend device according to an embodiment of the present invention;
fig. 7 is a structural diagram of a data synchronization apparatus applied to a front-end device according to an embodiment of the present invention;
fig. 8 is a structural diagram of a data synchronization apparatus applied to a backend device according to an embodiment of the present invention;
fig. 9 is a schematic view of an electronic device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention.
The embodiment of the invention provides a data synchronization system, which comprises front-end equipment and back-end equipment, wherein the number of the front-end equipment can be one or more.
For example, fig. 1 is a system structure diagram of a data synchronization system according to an embodiment of the present invention, and the data synchronization system shown in fig. 1 includes two front-end devices 110 and one back-end device 120.
Fig. 2 is a timing diagram of data synchronization performed by a data synchronization system according to an embodiment of the present invention, which specifically includes the following steps:
s201, after the front-end device 110 performs an update operation on the locally stored first data, the version number of the first data is updated according to a preset version number update rule, so as to obtain a target version number.
In this embodiment of the present invention, the front-end devices 110 may perform an update operation on locally stored first data requested to be updated by a user in response to a data update request sent by the user, where each front-end device 110 may receive one or more data update requests, and the data update requests may be sent sequentially or concurrently.
Alternatively, the front-end device 110 may also obtain the data to be updated according to a preset data update rule, and perform an update operation on the locally stored first data according to the data to be updated, which is not limited in the embodiment of the present invention.
The update operation may refer to replacement, deletion, or addition of the first data, or may refer to processing such as format conversion and mathematical operation on the first data, and is not limited specifically.
In one implementation, the version number of each first data may be stored in the front-end device 110. Or, in another implementation, if the first data is stored in the data table, the version number of each data table may also be stored in the front-end device 110, and the version number of the data table to which each first data belongs is taken as the version number of the first data, so that the version number corresponding to each first data does not need to be stored in the front-end device 110, and occupation of system resources of the front-end device 110 and influence on performance of the data table are reduced.
In this step, if the first data is stored in the data table, the specific way for the front-end device 110 to obtain the target version number may be: and after the updating operation is performed on the first data, inquiring the version number of the data table to which the first data belongs as the version number of the first data. Wherein, the version number of the data table can be stored in the data table as a part of the data table; alternatively, it may be stored in the front-end device 110 separately from the data table, so that in case of an error in reading the data table, the version number thereof may still be recorded.
For example, the first data may be a field in a MySQL (Structured Query language) data table locally stored by the front-end device 110, the version number of the MySQL data table to which each first data belongs may be used as the version number of the first data, and the version number of each MySQL data table is also stored as a field in the MySQL data table.
In this step, if the version number of the first data is a number, the manner of updating the version number of the first data by the front-end device 110 according to the preset version number updating rule may be: and adding the version number of the first data to a preset value to obtain a target version number, wherein for example, if the version number of the first data is 0 and the preset value is 1, the target version number is 1.
Alternatively, the version number of the first data may also be a combination of letters and numbers, for example, "1. a", and the manner in which the front-end device 110 updates the version number of the first data according to the preset version number update rule may be: the method includes the steps that the letter part in the version number of the first data is continued according to an alphabet, if the letter part is 'z', the number part in the version number of the first data is added with 1, the letter part is updated to 'a', and a target version number is obtained, for example, if the version number of the first data is '1. z', the target version number is '2. a'.
In addition, the version number of the first data may also be other numbers, letters, or a combination of numbers and letters, and different version number update rules may be preset according to different formats of the version number, which is not limited in the embodiment of the present invention.
S202, the front-end device 110 generates a data update message carrying a target version number, where the data update message is used to indicate the first data and update operation.
For example, in the backend device 120, a correspondence relationship between each locally stored data and the data identifier and a correspondence relationship between each update operation and the operation identifier may be stored in advance, and the data update message generated by the front-end device 110 may include the data identifier of the first data and the operation identifier of the update operation performed by the front-end device 110 on the first data, so that after receiving the data update message, the backend device 120 may determine to perform those update operations on those data according to the data identifier and the operation identifier in the data update message.
In one implementation, the first data is stored in a data table, and the data update message may also indicate the data table, for example, if the first data is stored in a MySQL data table, the data update message may be a bin log message of the MySQL data table, and the bin log message may indicate the MySQL data table, the first data in the MySQL data table, and an update operation performed by the front-end device 110 on the first data.
S203, the front-end device 110 sends the data update message to the back-end device 120.
In this step, the front-end device 110 may directly send the data update message to the back-end device 120 through a predetermined communication Protocol, such as an HTTP (HyperText Transfer Protocol) Protocol.
Alternatively, the front-end device 110 may store the data update message in the message middleware first, and send the data update message to the back-end device 120 through the message middleware, where the message middleware may employ a rockmq. The message middleware can communicate among different platforms, can shield the characteristics among various platforms and protocols, and realizes the cooperation among different platforms.
And S204, the back-end equipment 120 receives the data updating message, and determines the version number of the second data corresponding to the first data, which is locally stored, according to the data updating message.
In this step, the backend device 120 may directly receive the data update message sent by the front-end device 110 through a pre-agreed communication protocol, such as an HTTP protocol. Alternatively, the back-end device 120 may receive the data update message from message middleware that stores the data update message sent by the front-end device 110.
In an application scenario of the embodiment of the present invention, each front-end device 110 may send locally stored data to the back-end device 120 for aggregation, that is, the data in each front-end device 110 is stored in the back-end device 120. For convenience of description, the data locally stored in the front-end device 110 is referred to as first data, the data locally stored in the back-end device 120 is referred to as second data, and the first data and the corresponding second data are the same data respectively stored in the front-end device 110 and the back-end device 120.
In an embodiment of the present invention, each of the second data has a version number. In one implementation, the version number of each second data is different, and then, each second data and its own version number may be stored in the backend device 120 correspondingly.
Or, in another implementation manner, if the first data in the front-end device 110 is stored in a data table, and the data update message received by the back-end device 120 may further indicate a data table to which the first data belongs, then the back-end device 120 may store a corresponding relationship between each data table in the front-end device 110 and a version number thereof, and use the version number of the data table to which the locally stored first data belongs as the version number of the second data corresponding to the first data. In this way, the backend device 120 only needs to store the corresponding relationship between each data table and the version number thereof, and does not need to store each second data and the version number thereof, thereby reducing the occupation of system resources of the backend device 120 and the influence on the performance of the data tables.
The backend device 120 may separately establish a version record data table, and correspondingly store each data table and a corresponding version number in the version record data table. Alternatively, each data table and its version number may be stored in the same data table as the second data as a json (JavaScript Object Notation) format field, which facilitates management and expansion. The embodiment of the present invention is not limited thereto.
S205, the back-end device 120 judges whether the version of the second data is earlier than that of the first data according to the preset version number updating rule, the version number of the second data and the target version number; if yes, go to step S206.
In this step, the method for the back-end device 120 to determine whether the version of the second data is earlier than that of the first data corresponds to the method for the front-end device 110 to obtain the target version number.
For example, if the version number of the first data is a number and the preset version number update rule is to add the version number of the first data to a preset value, the backend device 120 may determine whether the version number of the second data is smaller than the target version number, and if so, determine that the version of the second data is earlier than the first data. For example, if the version number of the second data is 0 and the target version number is 1, the backend device 120 may determine that the version of the second data is earlier than the version of the first data.
Or, if the version number of the first data may also be a combination of letters and numbers, the preset version number update rule is to continue the letter part in the version number of the first data according to the alphabet, if the letter part is "z", add 1 to the number part in the version number of the first data, and update the letter part to "a" to obtain the target version number, then the backend device 120 may first determine the version number of the second data and the number part in the target version number, where a smaller version number of the number part corresponds to an earlier version data, and if the number parts are equal, determine the front-back order of the letter part according to the alphabet, and a version number closer to the letter part corresponds to an earlier version data.
S206, the backend device 120 performs an update operation on the second data according to the data update message, and updates the version number of the second data to the target version number.
In this embodiment of the present invention, if the backend device 120 correspondingly stores the version number of each second data, the backend device 120 may update the version number of the second data to the target version number when determining that the version of the second data is earlier than the version of the first data.
Alternatively, if the first data in the front-end device 110 is stored in a data table, and the backend device 120 stores the corresponding relationship between each data table in the front-end device 110 and the version number thereof, then, in the case that the version of the second data is determined to be earlier than that of the first data, the backend device 120 may update the version number of the locally stored data table to the target version number, that is, in the corresponding relationship between the updated data table and the version number thereof, the data table to which the first data belongs corresponds to the target version number.
In this step, if the backend device 120 determines that the version of the second data is not earlier than the first data, the backend device 120 may discard the data update message.
In summary, in the data synchronization system provided in the embodiment of the present invention, each time the front-end device performs an update operation on the locally stored first data, the version number of the first data is updated, so that the back-end device can compare the version number of the updated first data with the version number of the locally stored second data, determine the sequence of the version of the second data and the version of the updated first data, and perform the update operation on the second data when the version of the second data is earlier than the version of the updated first data, thereby reducing the possibility of data update being covered, and implementing data synchronization in the front-end device and the back-end device.
Fig. 3 is a timing chart of data synchronization performed by another data synchronization system according to an embodiment of the present invention, which specifically includes the following steps:
s301, after performing an update operation on the locally stored first data, the front-end device 110 queries a version number of a data table to which the first data belongs, as the version number of the first data.
In this embodiment of the present invention, the front-end devices 110 may perform an update operation on locally stored first data requested to be updated by a user in response to a data update request sent by the user, where each front-end device 110 may receive one or more data update requests, and the data update requests may be sent sequentially or concurrently.
The version number of the data table may be stored in the data table in json format as a part of the data table. For example, the first data may be a "uid" field in a MySQL data table "user _ basic _ info" locally stored by the front-end device 110, and then a version number of the MySQL data table "user _ basic _ info" to which each "uid" field belongs may be used as a version number of the "uid" field, where each MySQL data table "user _ basic _ info" may further include a "version" field, and the "version" field is a version number of the MySQL data table "user _ basic _ info".
S302, the front-end device 110 adds the version number of the first data to a preset value to obtain a target version number.
For example, if the version number of the first data is 0 and the preset value is 1, the target version number is 1.
S303, the front-end device 110 generates a data update message carrying the target version number, where the data update message is used to indicate the first data, the update operation, and the data table.
For example, in the back-end device 120, a corresponding relationship between each locally stored data and a data identifier, a corresponding relationship between each update operation and an operation identifier, and a corresponding relationship between each data table and a data table identifier may be stored in advance, and the data update message generated by the front-end device 110 may include a data identifier of the first data, an operation identifier of the update operation performed by the front-end device 110 on the first data, and an identifier of the data table to which the first device belongs, so that after receiving the data update message, the back-end device 120 may determine, according to the data identifier and the operation identifier in the data update message, which update operation is performed by the front-end device 110 on which first data in which data table.
In this step, if the first data is stored in the MySQL data table, the data update message may be a bin log message of the MySQL data table.
S304, the front-end device 110 sends the data update message to the back-end device 120 through the message middleware.
Wherein the message middleware may employ a rockmq. The message middleware can communicate among different platforms, can shield the characteristics among various platforms and protocols, and realizes the cooperation among different platforms.
S305, the back-end device 120 receives the data updating message, and takes the version number of the locally stored data table as the version number of the second data according to the data updating message and the corresponding relationship between the pre-stored data table and the version number.
In an application scenario of the embodiment of the present invention, each front-end device 110 may send locally stored data to the back-end device 120 for aggregation, that is, the data in each front-end device 110 is stored in the back-end device 120. For convenience of description, the data locally stored in the front-end device 110 is referred to as first data, the data locally stored in the back-end device 120 is referred to as second data, and the first data and the corresponding second data are the same data respectively stored in the front-end device 110 and the back-end device 120.
In this step, the backend device 120 may store a corresponding relationship between each data table in the front-end device 110 and a version number thereof, and use the version number of the data table to which the locally stored first data belongs as the version number of the second data corresponding to the first data. In this way, the backend device 120 only needs to store the corresponding relationship between each data table and the version number thereof, and does not need to store each second data and the version number thereof, thereby reducing the occupation of system resources of the backend device 120 and the influence on the performance of the data tables.
The backend device 120 may store each data table and its version number as a json format field in the same data table as the second data, so as to facilitate management and expansion.
For example, if the data table to which the first data belongs is MySQL data table "user _ basic _ info", a last _ update field indicating the data table and its version number may be denoted as "" user _ basic _ info ": 3", and a version number of "user _ basic _ info" may be denoted as 3, where the last _ update field is stored in json format in MySQL data table "mp _ user _ info" of the backend device 120, and data of multiple data tables including the MySQL data table "user _ basic _ info" and the version number of each data table are stored in the MySQL data table "mp _ user _ info".
S306, the back-end device 120 determines whether the version number of the second data is smaller than the target version number; if so, executing S307; if not, go to step S308.
For example, if the version number of the second data is 0 and the target version number is 1, the backend device 120 may determine that the version of the second data is earlier than the version of the first data.
S307, the backend device 120 performs an update operation on the second data according to the data update message, and updates the version number of the locally stored data table to the target version number.
That is, in the correspondence relationship between the updated data table and its version number, the data table to which the first data belongs corresponds to the target version number.
S308, the backend device 120 discards the data update message.
For example, as shown in fig. 4, a schematic diagram of a data synchronization method provided in an embodiment of the present invention is shown, where a data synchronization system includes a front-end device a, a front-end device B, and a back-end device, where the front-end device a stores a data table "user _ basic _ info", the front-end device B stores a data table "company _ info", the back-end device stores a data table "mp _ user _ info", the data table "mp _ user _ info" includes all data in the data table "user _ basic _ info" and the data table "company _ info", and version numbers respectively corresponding to the data table "user _ basic _ info" and the data table "company _ info".
First, the front-end device a receives the data update request a and the data update request B for the locally stored data table "user _ basic _ info" at the same time, and the front-end device B receives the data update request C and the data update request D for the locally stored data table "company _ info" at the same time.
For each data updating request, the front-end equipment respectively executes updating operation on locally stored first data, then updates the version number of the first data according to a preset version number updating rule to obtain a target version number, generates a data updating message A, a data updating message B, a data updating message C and a data updating message D which carry the target version number and correspond to each data updating request, and sends the data updating messages to the back-end equipment through the RocktMQ message middleware.
Furthermore, the backend device may determine, according to each piece of data update message, a version number of the data table "user _ basic _ info" or the data table "company _ info" indicated by the piece of data update message stored in the data table "mp _ user _ info" as a version number of second data corresponding to the first data indicated by the data update message, and determine whether the version number of the second data is smaller than a target version number; if the version number is less than the target version number, updating the second data according to the data updating message, and updating the version number of the data table 'user _ basic _ info' or the data table 'company _ info' indicated by the data updating message to the target version number; and if not, discarding the data updating message.
In summary, in the data synchronization system provided in the embodiment of the present invention, each time the front-end device performs an update operation on the first data in the locally stored data table, the version number of the first data is updated, so that the back-end device can compare the version number of the updated first data with the version number of the second data, and determine the sequence of the version of the second data and the version of the first data, where the version number of the second data is the version number of the data table to which the first data locally stored in the back-end device 120 belongs, and perform the update operation on the second data when the version of the second data is earlier than the version of the first data, thereby reducing the possibility of data update being covered, and implementing data synchronization in the front-end device and the back-end device.
As shown in fig. 5, an embodiment of the present invention further provides a data synchronization method, where the method is applied to a front-end device, and specifically includes the following steps:
s501, after the first data stored locally is updated, the version number of the first data is updated according to a preset version number updating rule to obtain a target version number.
S502, generating a data updating message carrying a target version number, wherein the data updating message is used for indicating first data and updating operation.
S503, sending the data updating message to the back-end equipment.
In this way, the backend device may determine, according to the data update message, a version number of second data corresponding to the first data, which is locally stored, and perform, according to the preset version number update rule, the version number of the second data, and the target version number, an update operation on the second data according to the data update message, and update the version number of the second data to the target version number, when it is determined that the version of the second data is earlier than the first data.
In one implementation, the updating of the first data according to a preset version number updating rule to obtain a target version number includes:
and adding the version number of the first data to a preset value to obtain a target version number.
In one implementation, the first data is stored in a data table, the data update message is further used to indicate the data table, and before the version number of the second data is updated according to a preset version number update rule to obtain a target version number, the method further includes:
and inquiring the version number of the data table to which the first data belongs as the version number of the first data.
In one implementation, sending a data update message to a backend device includes:
and sending the data updating message to the back-end equipment through the message middleware.
To sum up, in the data synchronization method provided in the embodiment of the present invention, each time the front-end device performs an update operation on the locally stored first data, the version number of the first data is updated, so that the back-end device can compare the version number of the updated first data with the version number of the locally stored second data, determine the sequence of the version of the second data and the version of the updated first data, and perform an update operation on the second data when the version of the second data is earlier than the version of the updated first data, thereby reducing the possibility of data update being covered and achieving data synchronization in the front-end device and the back-end device.
As shown in fig. 6, an embodiment of the present invention further provides a data synchronization method, where the method is applied to a backend device, and specifically includes the following steps:
s601, receiving a data updating message carrying a target version number sent by front-end equipment.
The data updating message is used for indicating first data stored locally by the front-end equipment and updating operation executed on the first data, and the target version number is obtained by updating the version number of the first data according to a preset version number updating rule after the front-end equipment executes the updating operation on the first data.
S602, according to the data updating message, determining the version number of the second data which is locally stored and corresponds to the first data.
S603, judging whether the version of the second data is earlier than the first data according to the updating rule of the preset version number, the version number of the second data and the target version number, and executing S604 if the version of the second data is earlier than the first data.
S604, updating operation is carried out on the second data according to the data updating message, and the version number of the second data is updated to the target version number.
In one implementation, the version number of the first data is a number, and the target version number is the sum of the version number of the first data and a preset value;
judging whether the version of the second data is earlier than the version of the first data according to the preset version number updating rule, the version number of the second data and the target version number, wherein the judging step comprises the following steps:
judging whether the version number of the second data is smaller than the target version number; if so, judging that the version of the second data is earlier than that of the first data; if not, the version of the second data is determined not to be earlier than the first data.
In one implementation, the storing the first data in a data table, the determining, by the data update message, a version number of the second data corresponding to the first data, which is locally stored, according to the data update message, includes:
taking the version number of the locally stored data table as the version number of the second data according to the data updating message and the corresponding relation between the pre-stored data table and the version number;
updating the version number of the second data to a target version number, including:
and updating the version number of the locally stored data table to a target version number.
In one implementation, the correspondence between the data table and the version number is stored in the backend device in a json format.
In one implementation, in a case where the second data is not earlier in version than the first data, the method further comprises:
the data update message is discarded.
To sum up, in the data synchronization method provided in the embodiment of the present invention, each time the front-end device performs an update operation on the locally stored first data, the version number of the first data is updated, so that the back-end device can compare the version number of the updated first data with the version number of the locally stored second data, determine the sequence of the version of the second data and the version of the updated first data, and perform an update operation on the second data when the version of the second data is earlier than the version of the updated first data, thereby reducing the possibility of data update being covered and achieving data synchronization in the front-end device and the back-end device.
As shown in fig. 7, an embodiment of the present invention further provides a data synchronization method, where the method is applied to a front-end device, and specifically includes the following steps:
the updating module 701 is configured to update the version number of the first data according to a preset version number updating rule after an updating operation is performed on the locally stored first data, so as to obtain a target version number;
a generating module 702, configured to generate a data update message carrying a target version number, where the data update message is used to indicate first data and update operation;
a sending module 703, configured to send the data update message to the backend device, so that the backend device determines, according to the data update message, a version number of second data corresponding to the first data, where the version number of the second data is determined to be earlier than the version number of the first data according to a preset version number update rule, the version number of the second data, and the target version number, and executes an update operation on the second data according to the data update message, and updates the version number of the second data to the target version number.
To sum up, in the data synchronization apparatus provided in the embodiment of the present invention, each time the front-end device performs an update operation on the locally stored first data, the version number of the first data is updated, so that the back-end device can compare the version number of the updated first data with the version number of the locally stored second data, determine the sequence of the version of the second data and the version of the updated first data, and perform an update operation on the second data when the version of the second data is earlier than the version of the updated first data, thereby reducing the possibility of data update being covered, and implementing data synchronization in the front-end device and the back-end device.
As shown in fig. 8, an embodiment of the present invention further provides a data synchronization method, where the method is applied to a backend device, and specifically includes the following steps:
a receiving module 801, configured to receive a data update message that is sent by a front-end device and carries a target version number, where the data update message is used to indicate first data locally stored by the front-end device and update operation performed on the first data, and the target version number is obtained by updating, by the front-end device, a version number of the first data according to a preset version number update rule after the front-end device performs the update operation on the first data;
a determining module 802, configured to determine, according to the data update message, a version number of second data corresponding to the first data stored locally;
a determining module 803, configured to determine whether the version of the second data is earlier than the version of the first data according to the preset version number update rule, the version number of the second data, and the target version number;
and the synchronization module 804 is configured to, when the version of the second data is earlier than the first data, perform an update operation on the second data according to the data update message, and update the version number of the second data to a target version number.
To sum up, in the data synchronization apparatus provided in the embodiment of the present invention, each time the front-end device performs an update operation on the locally stored first data, the version number of the first data is updated, so that the back-end device can compare the version number of the updated first data with the version number of the locally stored second data, determine the sequence of the version of the second data and the version of the updated first data, and perform an update operation on the second data when the version of the second data is earlier than the version of the updated first data, thereby reducing the possibility of data update being covered, and implementing data synchronization in the front-end device and the back-end device.
An embodiment of the present invention further provides an electronic device, as shown in fig. 9, which includes a processor 901, a communication interface 902, a memory 904, and a communication bus 904, where the processor 901, the communication interface 902, and the memory 904 complete mutual communication through the communication bus 904,
a memory 904 for storing a computer program;
the processor 901 is configured to implement the following steps when executing the program stored in the memory 904:
after the updating operation is executed on the locally stored first data, updating the version number of the first data according to a preset version number updating rule to obtain a target version number;
generating a data updating message carrying a target version number, wherein the data updating message is used for indicating first data and updating operation;
and sending the data updating message to the back-end equipment.
Or, the following steps are implemented:
receiving a data updating message which is sent by front-end equipment and carries a target version number, wherein the data updating message is used for indicating first data locally stored by the front-end equipment and updating operation executed on the first data, and the target version number is obtained by updating the version number of the first data according to a preset version number updating rule after the front-end equipment executes the updating operation on the first data;
determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message;
judging whether the version of the second data is earlier than that of the first data or not according to a preset version number updating rule, the version number of the second data and the target version number;
and if so, executing updating operation on the second data according to the data updating message, and updating the version number of the second data to the target version number.
The communication bus mentioned in the above terminal may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the terminal and other equipment.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In yet another embodiment of the present invention, a computer-readable storage medium is further provided, which has instructions stored therein, and when the computer-readable storage medium runs on a computer, the computer is caused to execute the data synchronization method described in any of the above embodiments.
In a further embodiment of the present invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the data synchronization method of any of the above embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is 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 apparatus 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 apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only for the preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall fall within the protection scope of the present invention.
Claims (19)
1.A data synchronization system, the system comprising: a back-end device and at least one front-end device, wherein,
the front-end equipment is used for updating the version number of the first data according to a preset version number updating rule after the updating operation is executed on the locally stored first data, so as to obtain a target version number; generating a data updating message carrying the target version number, wherein the data updating message is used for indicating the first data and the updating operation; sending the data updating message to the back-end equipment;
the back-end equipment is used for receiving the data updating message; determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message; judging whether the version of the second data is earlier than that of the first data or not according to the preset version number updating rule, the version number of the second data and the target version number; and if so, executing the updating operation on the second data according to the data updating message, and updating the version number of the second data into the target version number.
2. The system of claim 1, wherein the version number of the first data is a number;
the front-end equipment is specifically used for adding the version number of the first data to a preset value to obtain a target version number;
the back-end device is specifically configured to determine whether the version number of the second data is smaller than the target version number; and if so, judging that the version of the second data is earlier than that of the first data.
3. The system of claim 1, wherein the first data is stored in a data table, and wherein the data update message is further configured to indicate the data table;
the front-end device is specifically configured to query, after performing an update operation on the first data, a version number of the data table as the version number of the first data;
the back-end device is specifically configured to use the version number of the locally stored data table as the version number of the second data according to the data update message and the corresponding relationship between the data table and the version number stored in advance; updating the version number of the locally stored data table to the target version number in a case where it is determined that the version of the second data is earlier than the first data.
4. The system of claim 3, wherein the correspondence of the data table to a version number is stored in the backend device in json format.
5. The system of claim 1,
the front-end device is specifically configured to send the data update message to the back-end device through a message middleware.
6. The system of claim 1,
the backend device is further configured to discard the data update message if it is determined that the version of the second data is not earlier than the first data.
7. A data synchronization method is applied to front-end equipment, and is characterized in that the method comprises the following steps:
after the updating operation is carried out on the locally stored first data, updating the version number of the first data according to a preset version number updating rule to obtain a target version number;
generating a data updating message carrying the target version number, wherein the data updating message is used for indicating the first data and the updating operation;
and sending the data updating message to back-end equipment so that the back-end equipment determines the version number of second data corresponding to the first data and stored locally according to the data updating message, and executes the updating operation on the second data according to the data updating message and updates the version number of the second data to the target version number under the condition that the version of the second data is judged to be earlier than that of the first data according to the preset version number updating rule, the version number of the second data and the target version number.
8. The method of claim 7, wherein the version number of the first data is a number, and the updating the version number of the first data according to a preset version number updating rule to obtain a target version number comprises:
and adding the version number of the first data to a preset value to obtain a target version number.
9. The method of claim 7, wherein the first data is stored in a data table, and the data update message is further used for indicating the data table, and before the updating the version number of the second data according to a preset version number update rule to obtain a target version number, the method further comprises:
and inquiring the version number of the data table to which the first data belongs as the version number of the first data.
10. The method of claim 7, wherein sending the data update message to a backend device comprises:
and sending the data updating message to the back-end equipment through message middleware.
11. A data synchronization method is applied to a back-end device, and is characterized by comprising the following steps:
receiving a data updating message which is sent by front-end equipment and carries a target version number, wherein the data updating message is used for indicating first data locally stored by the front-end equipment and updating operation executed on the first data, and the target version number is obtained by updating the version number of the first data according to a preset version number updating rule after the front-end equipment executes the updating operation on the first data;
determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message;
judging whether the version of the second data is earlier than that of the first data or not according to the preset version number updating rule, the version number of the second data and the target version number;
and if so, executing the updating operation on the second data according to the data updating message, and updating the version number of the second data to the target version number.
12. The method of claim 11, wherein the version number of the first data is a number, and the target version number is a sum of the version number of the first data and a preset value;
the determining whether the version of the second data is earlier than the version of the first data according to the preset version number update rule, the version number of the second data and the target version number includes:
judging whether the version number of the second data is smaller than the target version number; if the first data is less than the second data, judging that the version of the second data is earlier than that of the first data; and if not, judging that the version of the second data is not earlier than the first data.
13. The method of claim 11, wherein the first data is stored in a data table, wherein the data update message is further used for indicating the data table, and wherein determining a version number of locally stored second data corresponding to the first data according to the data update message comprises:
according to the data updating message and the corresponding relation between the pre-stored data table and the version number, taking the version number of the locally stored data table as the version number of the second data;
the updating the version number of the second data to the target version number includes:
and updating the version number of the locally stored data table to the target version number.
14. The method of claim 13, wherein the correspondence of the data table to a version number is stored in the backend device in json format.
15. The method of claim 11, wherein in the case that the second data is not earlier in version than the first data, the method further comprises:
discarding the data update message.
16. A data synchronization device applied to a front-end device is characterized by comprising:
the updating module is used for updating the version number of the first data according to a preset version number updating rule after the updating operation is executed on the locally stored first data to obtain a target version number;
a generating module, configured to generate a data update message carrying the target version number, where the data update message is used to indicate the first data and the update operation;
and the sending module is used for sending the data updating message to back-end equipment so that the back-end equipment determines the version number of second data corresponding to the first data and stored locally according to the data updating message, and executes the updating operation on the second data according to the data updating message and updates the version number of the second data to the target version number under the condition that the version of the second data is judged to be earlier than that of the first data according to the preset version number updating rule, the version number of the second data and the target version number.
17. A data synchronization device applied to a backend device, the device comprising:
the device comprises a receiving module and a processing module, wherein the receiving module is used for receiving a data updating message which is sent by front-end equipment and carries a target version number, the data updating message is used for indicating first data which are locally stored by the front-end equipment and updating operation which is executed on the first data, and the target version number is obtained by updating the version number of the first data according to a preset version number updating rule after the front-end equipment executes the updating operation on the first data;
the determining module is used for determining the version number of second data which is locally stored and corresponds to the first data according to the data updating message;
the judging module is used for judging whether the version of the second data is earlier than the first data according to the preset version number updating rule, the version number of the second data and the target version number;
and the synchronization module is used for executing the updating operation on the second data according to the data updating message and updating the version number of the second data to the target version number under the condition that the version of the second data is earlier than that of the first data.
18. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any of claims 7-10 or 11-15 when executing a program stored in the memory.
19. A storage medium on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 7-10 or 11-15.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011066464.4A CN112199381A (en) | 2020-09-30 | 2020-09-30 | Data synchronization system, method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011066464.4A CN112199381A (en) | 2020-09-30 | 2020-09-30 | Data synchronization system, method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112199381A true CN112199381A (en) | 2021-01-08 |
Family
ID=74012963
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011066464.4A Pending CN112199381A (en) | 2020-09-30 | 2020-09-30 | Data synchronization system, method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112199381A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190065560A1 (en) * | 2017-08-31 | 2019-02-28 | Sap Se | Caching for query processing systems |
| CN109788027A (en) * | 2018-12-13 | 2019-05-21 | 平安科技（深圳）有限公司 | Method of data synchronization, device, server and computer storage medium |
| CN109901858A (en) * | 2019-01-17 | 2019-06-18 | 平安普惠企业管理有限公司 | Application software updates detection method, device, computer equipment and storage medium |
-
2020
- 2020-09-30 CN CN202011066464.4A patent/CN112199381A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190065560A1 (en) * | 2017-08-31 | 2019-02-28 | Sap Se | Caching for query processing systems |
| CN109788027A (en) * | 2018-12-13 | 2019-05-21 | 平安科技（深圳）有限公司 | Method of data synchronization, device, server and computer storage medium |
| CN109901858A (en) * | 2019-01-17 | 2019-06-18 | 平安普惠企业管理有限公司 | Application software updates detection method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111314459B (en) | Service request method, device, electronic equipment and storage medium | |
| CN115378862B (en) | Method, device, equipment and medium for route configuration with grouping function | |
| US10205813B2 (en) | Method and system for detecting abnormal contact information and server | |
| CN112835885B (en) | Processing method, device and system for distributed form storage | |
| CN114637703B (en) | Data access device, method, readable medium and electronic equipment | |
| CN109600254B (en) | Method for generating full-link log and related system | |
| CN110737548A (en) | Data request method and server | |
| CN110955460B (en) | Service process starting method and device, electronic equipment and storage medium | |
| CN110727895B (en) | Sensitive word sending method and device, electronic equipment and storage medium | |
| CN112506968A (en) | Information aggregation method and device, electronic equipment and computer readable medium | |
| CN111224756B (en) | Method and device for determining data transmission abnormity, storage medium and electronic equipment | |
| CN110990350B (en) | Log analysis method and device | |
| CN110287049B (en) | Data processing method, device and storage medium | |
| CN112422485B (en) | Communication method and device of transmission control protocol | |
| CN111309693A (en) | Data synchronization method, device and system, electronic equipment and storage medium | |
| CN112199381A (en) | Data synchronization system, method and device, electronic equipment and storage medium | |
| US20200019551A1 (en) | Database management system and database management method | |
| CN109254855B (en) | Registration method and device of parameter transmission protocol and electronic equipment | |
| CN114611483A (en) | Method and device for automatically upgrading nuclear power DCS control logic diagram and function diagram association | |
| CN109688204B (en) | File downloading method, node and terminal based on NDN (named data networking) | |
| CN112256700A (en) | Data storage method and device, electronic equipment and computer readable storage medium | |
| CN111538651A (en) | Interface testing method, device, server and storage medium | |
| CN112416401B (en) | Data updating method, device and equipment | |
| CN114281921A (en) | Data processing method and device, storage medium and equipment | |
| CN116260853A (en) | Connection management method and device for node equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |