CN110602250A - Data synchronization method and device, server and terminal equipment - Google Patents
Data synchronization method and device, server and terminal equipment Download PDFInfo
- Publication number
- CN110602250A CN110602250A CN201910939061.7A CN201910939061A CN110602250A CN 110602250 A CN110602250 A CN 110602250A CN 201910939061 A CN201910939061 A CN 201910939061A CN 110602250 A CN110602250 A CN 110602250A
- Authority
- CN
- China
- Prior art keywords
- synchronized
- cloud platform
- server
- message queue
- data synchronization
- 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
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/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention provides a data synchronization method, a data synchronization device, a server and terminal equipment, wherein the method is applied to the server; the method comprises the following steps: acquiring an object identifier of an object to be synchronized from a preset message queue; reading an object to be synchronized corresponding to the object identification from the first cloud platform; and synchronizing the read object to be synchronized to the second cloud platform. In the method, the message queue is preset in the server, and data synchronization among the cloud platforms is realized through the message queue, so that the problem of poor data interaction capability of the platforms due to compatibility problems is solved, and the transmission speed and flexibility during data synchronization are improved. Further, in the above manner, after the client uploads the object to one cloud platform, the server can implement data synchronization between the plurality of cloud platforms through the message queue, and this manner that the client uploads one copy of data can implement data synchronization between the hybrid clouds can further improve data transmission speed and flexibility of data transmission.
Description
Technical Field
The invention relates to the technical field of cloud storage, in particular to a data synchronization method, a data synchronization device, a server and terminal equipment.
Background
In the related technology, when the hybrid cloud is used for storing data, because the manufacturers of the private cloud platform and the public cloud platform in the hybrid cloud are different, the compatibility problem is likely to exist between the private cloud platform and the public cloud platform, and the compatibility problem is easy to cause that the mutual switching and the interaction capacity between the private cloud platform and the public cloud platform are poor; when the private cloud platform and the public cloud platform synchronize, the data transmission speed is low, and the data transmission flexibility is poor.
Disclosure of Invention
In view of this, the present invention provides a data synchronization method, apparatus, server and terminal device, so as to improve data transmission speed and enhance flexibility of data transmission.
In a first aspect, an embodiment of the present invention provides a data synchronization method, where the method is applied to a server, and the method includes: acquiring an object identifier of an object to be synchronized from a preset message queue; the method comprises the following steps that an object identifier of an object to be synchronized is uploaded to a message queue by a client in advance; reading an object to be synchronized corresponding to the object identification from the first cloud platform; and synchronizing the read object to be synchronized to the second cloud platform.
In a preferred embodiment of the present invention, after the step of synchronizing the read object to be synchronized to the second cloud platform, the method further includes: judging whether the object to be synchronized is successfully synchronized to the second cloud platform; if not, sending the object identification of the object to be synchronized to a preset standby queue; and successfully synchronizing the object to be synchronized to the second cloud platform through the standby queue.
In a preferred embodiment of the present invention, the step of successfully synchronizing the object to be synchronized to the second cloud platform through the standby queue includes: and according to a preset time interval, acquiring the object identification of the object to be synchronized from the standby queue, and continuing to execute the step of reading the object to be synchronized corresponding to the object identification from the first cloud platform until the object to be synchronized is successfully synchronized to the second cloud platform.
In a preferred embodiment of the present invention, after the step of synchronizing the read object to be synchronized to the second cloud platform, the method further includes: acquiring object state data of a first cloud platform and a second cloud platform; the object state data comprises object identifications of objects stored in the platform; outputting a state monitoring log according to the object state data; the status monitoring log includes: the total number of object identifications of the first cloud platform, the total number of object identifications of the second cloud platform, and the object identifications of objects stored only in the first cloud platform or the second cloud platform.
In a preferred embodiment of the present invention, the first cloud platform includes a private cloud platform, and the second cloud platform includes a public cloud platform; or the first cloud platform comprises a public cloud platform, and the second cloud platform comprises a private cloud platform.
In a second aspect, an embodiment of the present invention further provides a data synchronization method, where the method is applied to a terminal device, and determines an object to be synchronized; uploading an object to be synchronized to a first cloud platform; uploading the object identification of the object to be synchronized to a preset message queue in a server, so as to obtain the object identification of the object to be synchronized from the preset message queue through the server, reading the object to be synchronized corresponding to the object identification from the first cloud platform, and synchronizing the read object to be synchronized to the second cloud platform.
In a preferred embodiment of the present invention, the step of uploading the object identifier of the object to be synchronized to a message queue preset in the server includes: judging whether the object to be synchronized is successfully uploaded to a first cloud platform; and if so, uploading the object identification of the object to be synchronized to a preset message queue in the server.
In a preferred embodiment of the present invention, after the step of uploading the object identifier of the object to be synchronized to a message queue preset in the server, the method further includes: judging whether the object identification of the object to be synchronized is successfully uploaded to a message queue; and if not, deleting the object to be synchronized from the first cloud platform.
In a third aspect, an embodiment of the present invention further provides a data synchronization apparatus, where the apparatus is disposed in a server, and the apparatus includes: the object identification acquisition module is used for acquiring the object identification of the object to be synchronized from a preset message queue; the method comprises the following steps that an object identifier of an object to be synchronized is uploaded to a message queue by a client in advance; the object reading module is used for reading an object to be synchronized corresponding to the object identifier from the first cloud platform; and the object synchronization module is used for synchronizing the read object to be synchronized to the second cloud platform.
In a fourth aspect, an embodiment of the present invention further provides a data synchronization apparatus, where the apparatus is disposed in a terminal device, and the apparatus includes: the device comprises a to-be-synchronized object determining module, a synchronization module and a synchronization module, wherein the to-be-synchronized object determining module is used for determining an object to be synchronized; the object uploading module is used for uploading the object to be synchronized to the first cloud platform; the object identifier uploading module is used for uploading the object identifier of the object to be synchronized to a preset message queue in the server, so that the object identifier of the object to be synchronized is obtained from the preset message queue through the server, the object to be synchronized corresponding to the object identifier is read from the first cloud platform, and the read object to be synchronized is synchronized to the second cloud platform.
In a fifth aspect, an embodiment of the present invention further provides a server, which includes a processor and a memory, where the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the steps of the data synchronization method.
In a sixth aspect, an embodiment of the present invention further provides a terminal device, which includes a processor and a memory, where the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the steps of the data synchronization method.
In a seventh aspect, the present invention also provides a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called and executed by a processor, the computer-executable instructions cause the processor to implement the steps of the data synchronization method.
The embodiment of the invention has the following beneficial effects:
according to the data synchronization method, the data synchronization device, the server and the terminal equipment, after the client uploads the object to be synchronized to one cloud platform in the hybrid cloud, the object identification of the object to be synchronized is uploaded to the message queue of the server; and then the server acquires the object identification of the object to be synchronized from the message queue, reads the object to be synchronized corresponding to the object identification from the first cloud platform, and further synchronizes the object to be synchronized to the second cloud platform.
Further, in the above manner, after the client uploads the object to one cloud platform, the server can implement data synchronization between the plurality of cloud platforms through the message queue, and this manner that the client uploads one copy of data can implement data synchronization between the hybrid clouds can further improve data transmission speed and flexibility of data transmission.
Additional features and advantages of the disclosure will be set forth in the description which follows, or in part may be learned by the practice of the above-described techniques of the disclosure, or may be learned by practice of the disclosure.
In order to make the aforementioned objects, features and advantages of the present disclosure more comprehensible, preferred embodiments accompanied with figures are described in detail below.
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, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a scene diagram of a data synchronization method according to an embodiment of the present invention;
fig. 2 is a flowchart of a data synchronization method according to an embodiment of the present invention;
FIG. 3 is a flow chart of another data synchronization method according to an embodiment of the present invention;
FIG. 4 is a flow chart of another data synchronization method according to an embodiment of the present invention;
FIG. 5 is a flow chart of another data synchronization method according to an embodiment of the present invention;
FIG. 6 is a diagram illustrating another data synchronization method according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a data synchronization apparatus according to an embodiment of the present invention;
FIG. 8 is a schematic structural diagram of another data synchronization apparatus according to an embodiment of the present invention;
fig. 9 is a schematic structural diagram of a server or a terminal device according to an embodiment of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some, but not all embodiments of the present invention. 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 invention.
Cloud storage platforms are generally divided into public and private clouds. Various public cloud storage platforms are provided by various internet manufacturers, such as AWS (Amazon Web Services, Amazon cloud Services), internet easy clouds, arilocos, huahuahuazhiyu and the like, and the public cloud has the advantages of convenience, quickness and good expansibility. Meanwhile, a private cloud can be built based on a local private server, and the private cloud has the advantages of good safety, high availability and the like. Therefore, in combination with a specific business scenario, enterprises often adopt a hybrid cloud scheme to solve the demand. However, the existing synchronization scheme of cloud storage has certain problems in the aspects of universality and performance.
Two common methods for data synchronization between cloud storage are provided, one is to upload files to a public cloud and a private cloud at the same time, and the other is to perform offline data migration management. The second method, through offline data migration management, can only perform offline migration generally, and the real-time performance of data transmission cannot be guaranteed. In the first method, because the manufacturers of the private cloud platform and the public cloud platform in the hybrid cloud are different, the private cloud platform and the public cloud platform have compatibility problems, and because of the IO (Input/Output) influence of the network, such as unstable network, downtime of the server, and other external influences, the mutual switching and interaction capabilities between the private cloud platform and the public cloud platform are poor, and the data consistency of the hybrid cloud cannot be ensured.
In summary, when a user uses the hybrid cloud to store data, the data is synchronized between the private cloud platform and the public cloud platform, and the situations of low data transmission speed and poor data transmission flexibility are likely to occur. Based on this, the data synchronization method, the data synchronization device, the server and the terminal device provided by the embodiments of the present invention can be applied to data synchronization and transmission in various scenes, and provide a universal hybrid cloud synchronization framework, which provides a universal interface scheme and a storage synchronization module.
For the convenience of understanding the embodiment, a detailed description will be given to a data synchronization method disclosed in the embodiment of the present invention. Referring to a scene diagram of a data synchronization method shown in fig. 1, the server applying the data synchronization method in fig. 1 is in communication connection with a first cloud platform and a second cloud platform, respectively. The purpose of the embodiment is to synchronize data from a first cloud platform to a second cloud platform through a server, where the server is a device providing computing services, and the cloud platform is used for services based on hardware resources and software resources. The embodiment may also involve a client, which may be installed on the server or on a user terminal, which is in communication connection with the server.
The server in this embodiment is used for data transfer, the first cloud platform and the second cloud platform are mainly used for storing data, and the first cloud platform and the second cloud platform may specifically be: the cloud computing platform comprises various private cloud platforms or public cloud platforms such as a storage type cloud platform mainly based on data storage, a computing type cloud platform mainly based on data processing, and a comprehensive cloud computing platform compatible with computing or data storage processing.
Based on the above description, refer to the flowchart of a data synchronization method shown in fig. 2, which includes the following steps:
step S202, obtaining an object identifier of an object to be synchronized from a preset message queue; and the object identification of the object to be synchronized is uploaded to a message queue by the client in advance.
A message queue is a way of communicating between processes or different threads of the same process, handling a series of data inputs, typically from a user, in a software queue. In this embodiment, the message queue may be disposed in the server, and is in communication connection with the first cloud platform and the second cloud platform, respectively. The message queue needs to acquire an object identifier of an object to be synchronized in advance, the object to be synchronized is data which needs to be synchronized from the first cloud platform to the second cloud platform, and the object identifier is used for marking the object to be synchronized. In general, the object identification may be a number of the object to be synchronized, or a name of the object to be synchronized, or the like.
In the message queue, a producer sends a message to the message queue, and a consumer obtains the message from the message queue; the producer may be understood as the above-mentioned process or thread that uploads the object identifier to the message queue; a consumer may be understood as a process or thread that retrieves an object identification from the message queue described above. And processing the object identifier stored in the message Queue in a first-in first-out mode based on the message Queue of the Queue message model so as to ensure the processing sequence of the object identifier. When the consumer confirms that a certain object mark is obtained, the consumer sends a confirmation message to the message queue, and the message queue deletes the corresponding object mark according to the confirmation message; if the consumer does not successfully obtain an object id, the message queue will not delete the object id.
The client pre-stores the object identifier of the object to be synchronized and the object identifier of the object to be synchronized, uploads the object to be synchronized to the first cloud platform, and then uploads the object identifier to the message queue, or uploads the object to be synchronized to the first cloud platform and uploads the object identifier to the message queue. Then, the object identification is obtained from the message queue by the server. It should be noted that the client may be disposed in the server, or may be disposed on other terminal devices outside the server, and if the client is disposed on other terminal devices, the terminal device is in communication connection with the server, the first cloud platform, and the second cloud platform.
Step S204, reading the object to be synchronized corresponding to the object identification from the first cloud platform.
As can be seen from the foregoing, after the object to be synchronized has been uploaded to the first cloud platform by the client, the server needs to directly read the object corresponding to the object identifier from the first cloud platform according to the object identifier, and the read object is the object to be synchronized. The reading method may be that the server sends the object identifier to the first cloud platform, the first cloud platform determines the corresponding object to be synchronized according to the object identifier, and the first cloud platform sends the object with synchronization to the server.
And step S206, synchronizing the read object to be synchronized to the second cloud platform.
After reading the object to be synchronized from the first cloud platform according to the object identifier, the server synchronizes the object to be synchronized to the second cloud platform, and the synchronization method may be to send the object to be synchronized to the second cloud platform. After the object to be synchronized is uploaded to the first cloud platform at the client, the object to be synchronized is synchronized to the second cloud platform from the first cloud platform.
According to the data synchronization method provided by the embodiment of the invention, after uploading an object to be synchronized to a cloud platform in a hybrid cloud, a client uploads an object identifier of the object to be synchronized to a message queue of a server; and then the server acquires the object identification of the object to be synchronized from the message queue, reads the object to be synchronized corresponding to the object identification from the first cloud platform, and further synchronizes the object to be synchronized to the second cloud platform.
Further, in the above manner, after the client uploads the object to one cloud platform, the server can implement data synchronization between the plurality of cloud platforms through the message queue, and this manner that the client uploads one copy of data can implement data synchronization between the hybrid clouds can further improve data transmission speed and flexibility of data transmission.
The embodiment of the invention also provides another data synchronization method, which is realized on the basis of the method of the embodiment; the method mainly describes a specific processing mode after the read object to be synchronized fails to be synchronized to the second cloud platform.
Another data synchronization method, as shown in fig. 3, comprises the steps of:
step S302, obtaining an object identifier of an object to be synchronized from a preset message queue; and the object identification of the object to be synchronized is uploaded to a message queue by the client in advance.
Typically, initialization of the system is required before data synchronization is performed. The initialization of the system comprises: configuring service addresses of the first cloud platform and the second cloud platform, starting a message queue, configuring relevant parameters of the message queue and the like. The message queue can be implemented by Kafka, Redis, RabbitMQ, etc.
After the system initialization is completed, the client may upload the object to be synchronized to the first cloud platform, and then upload the object representation of the object to be synchronized to the message queue. The client configures Internet Protocol (IP) addresses and corresponding passwords of the first cloud platform and the second cloud platform during initialization, and performs data communication through the IP addresses and the corresponding passwords. The client also configures the service type and address of the message queue in the server, and performs data communication with the message queue according to the service type and address. Wherein, the service type can be Kafka, Redis, RabbitMQ and the like.
The first cloud platform and the second cloud platform in this embodiment may both be a public cloud platform and a private cloud platform, and specifically there are the following possibilities: the first cloud platform comprises a private cloud platform, and the second cloud platform comprises a public cloud platform; or the first cloud platform comprises a public cloud platform, and the second cloud platform comprises a private cloud platform. The public cloud is generally a cloud which can be used by a third-party provider for a user, and the private cloud is generally a cloud which is constructed for a client to use alone. These two cases correspond in sequence to synchronizing data from the private cloud to the public cloud, and from the public cloud to the private cloud.
In addition to the two possibilities, the first cloud platform and the second cloud platform may both include public cloud platforms, or the first cloud platform and the second cloud platform may both include private cloud platforms; namely, data is synchronized between public cloud platforms and data is synchronized between private cloud platforms. Therefore, the data transmission method provided by the embodiment can be applied to data synchronization among various platforms, and has high universality.
Step S304, reading the object to be synchronized corresponding to the object identifier from the first cloud platform.
Specifically, the server obtains an IP address and a corresponding password of the first cloud platform in advance, sends a reading instruction corresponding to the object identifier according to the IP address, the password and the object identifier, and the first cloud platform sends the object to be synchronized corresponding to the object identifier to the server according to the reading instruction.
And step S306, synchronizing the read object to be synchronized to a second cloud platform.
The server obtains the IP address and the corresponding password of the second cloud platform in advance, so that the object with the synchronization can be directly sent to the IP address corresponding to the second cloud platform, namely, the object to be synchronized is synchronized to the second cloud platform.
Step S308, determining whether the object to be synchronized is successfully synchronized to the second cloud platform. If yes, it is ended, and if no, step S310 is performed.
After synchronizing the object to be synchronized to the second cloud platform, the second cloud platform may return an upload result. The uploading result can reflect whether the object to be synchronized is successfully synchronized to the second cloud platform, and if the object to be synchronized is successfully synchronized to the second cloud platform, the data synchronization process of the object to be synchronized is finished; if the synchronization to the second cloud platform fails, the object to be synchronized needs to be synchronized to the second cloud platform again at a suitable time, i.e., the step S310 is continuously performed.
Step S310, sending the object identifier of the object to be synchronized to a preset standby queue.
After the synchronization to the second cloud platform fails, the synchronization needs to be performed again at an appropriate time. The standby queue is used for storing the object identifier of the object to be synchronized which fails to synchronize, and the standby queue can be used as a part of the message queue or can be provided with another message queue.
Step S312, successfully synchronizing the object to be synchronized to the second cloud platform through the standby queue.
And the server acquires the object identification in the standby queue according to the preset time, and resynchronizes the object to be synchronized until the object to be synchronized is successfully synchronized to the second cloud platform. The specific step of resynchronizing the objects to be synchronized may be performed by: and according to a preset time interval, acquiring the object identification of the object to be synchronized from the standby queue, and continuing to execute the step of reading the object to be synchronized corresponding to the object identification from the first cloud platform until the object to be synchronized is successfully synchronized to the second cloud platform.
The time interval refers to how many times the object to be synchronized corresponding to the object identifier is uploaded to the second cloud platform again, and the time interval can be manually set according to experience in advance. For example, a configuration file may be preconfigured, and the time interval may be read from the configuration file. In addition, the time interval is not necessarily a fixed time, and may be 1 hour for the first time, 2 hours for the second time, and the like; it is also possible to set a transmission upper limit, that is, re-transmit 10 times, if the synchronization has not been successful, it is considered that the synchronization is not possible, and abandon the data synchronization after that.
After the time interval is determined, the object identification is obtained from the standby queue at regular time according to the time interval, the object to be synchronized corresponding to the object identification is read from the first cloud platform again, and then the object to be synchronized is sent to the second cloud platform until the object to be synchronized is successfully sent to the second cloud platform. By the method, the reliability of data synchronization between platforms can be further improved.
In addition, the objects included in the first cloud platform and the second cloud platform may be monitored, and the specific monitoring method may be executed through steps S31 to S32:
step S31, acquiring object state data of the first cloud platform and the second cloud platform; the object state data comprises object identifications of objects stored in the platform.
The monitoring step may be performed by a server, and the object state data may include an object identifier of an object stored in the cloud platform, and may also include information such as a size and a storage location of the object. By monitoring the object status data, it can be determined whether the objects of the first cloud platform and the second cloud platform are the same and what differences are. The server detects object state data of a cloud platform, can send a corresponding object state query instruction to an IP address of the platform, and the platform can count objects stored by the platform and object identifications corresponding to the stored objects and send the objects to the server.
Step S32, outputting a state monitoring log according to the object state data; the status monitoring log includes: the total number of object identifications of the first cloud platform, the total number of object identifications of the second cloud platform, and the object identifications of objects stored only in the first cloud platform or the second cloud platform.
After the server obtains the object state data of the first cloud platform and the second cloud platform, the object stored by the first cloud platform and the object identifier corresponding to the stored object by the second cloud platform can be determined, so that the total number of the object identifiers of the first cloud platform and the second cloud platform can be counted. The server compares the object state data of the first cloud platform and the object state data of the second cloud platform one by one, so that the object identification of the object only stored in the first cloud platform or the second cloud platform, namely the object identification of the object unsynchronized with the first cloud platform and the second cloud platform, can be obtained, and accordingly, the state monitoring log can be output.
The first cloud platform and the second cloud platform may store objects through buckets (storage spaces), and therefore, the object state data may further include: identification of Bucket; the status monitoring log further comprises: the total number of buckets of the first cloud platform, the total number of buckets of the second cloud platform, and the buckets that exist only on the first cloud platform or the second cloud platform.
In the above manner, for the object to be synchronized that fails to be synchronized to the second cloud platform, the object identifier of the object to be synchronized is stored by the standby queue, and the object to be synchronized is reacquired and synchronized according to the preconfigured time interval; the server can detect object state data of the first cloud platform and the second cloud platform, and accordingly output the state monitoring logs to detect the object and the object identification stored in the first cloud platform and the second cloud platform. In the mode, the standby queue can ensure that even if the first time of synchronizing the object to be synchronized to the second cloud platform fails, the synchronization can be continued, and the fault tolerance rate and the reliability of data synchronization are enhanced; the state monitoring is carried out on the first cloud platform and the second cloud platform, the notification function is mainly played, the user can be guaranteed to know the object storage conditions of the first cloud platform and the second cloud platform in time, and the reliability of data synchronization is high.
The embodiment of the invention also provides another data synchronization method, which is applied to terminal equipment, wherein the terminal equipment is respectively in communication connection with the server, the first cloud platform and the second cloud platform. The method mainly illustrates a specific implementation mode that a client in the terminal equipment uploads an object to be synchronized and an object identifier of the object to be synchronized to a first cloud platform and a message queue.
The terminal device is generally a device capable of communicating with the server through a computer, a mobile phone and a tablet computer, the terminal device needs to be provided with a client in advance, and the terminal device is in data communication with the first cloud platform, the second cloud platform and the server through the client.
Based on the above description, refer to the flowchart of another data synchronization method shown in fig. 4, which includes the following steps:
step S402, determining the object to be synchronized.
The method comprises the steps that a terminal device receives an object to be synchronized and an object identifier of the object to be synchronized through a client, wherein the object to be synchronized and the object identifier of the object to be synchronized are both uploaded by a user in advance, or the object to be synchronized and the object identifier of the object to be synchronized are stored in the terminal device in advance, and the client reads the object identifiers of the object to be synchronized and the object to be synchronized according to an instruction of the user. In another implementation manner, the user may only upload the object to be synchronized, and the client generates the object identifier of the object to be synchronized.
Step S404, uploading the object to be synchronized to the first cloud platform.
The client of the terminal device may communicate with each other through an SDK (Software Development Kit), and the SDK may be installed in the client and send an object to be synchronized uploaded by a user to the first cloud platform.
Step S406, uploading the object identifier of the object to be synchronized to a preset message queue in the server, so as to obtain the object identifier of the object to be synchronized from the preset message queue through the server, reading the object to be synchronized corresponding to the object identifier from the first cloud platform, and synchronizing the read object to be synchronized to the second cloud platform.
After the client of the terminal device sends the object to be synchronized to the first cloud platform through the SDK, the object identification corresponding to the object to be synchronized is uploaded to a message queue of the server. The server performs the following data synchronization work, that is, the server acquires the object identifier of the object to be synchronized from the preset message queue, reads the object to be synchronized corresponding to the object identifier from the first cloud platform, and synchronizes the read object to be synchronized to the second cloud platform. The data synchronization method of the server has been described above, and is not described herein again.
In another data synchronization method provided by the embodiment of the present invention, after a server of a terminal device sends an object to be synchronized specified by a user to a first cloud platform, an object identifier corresponding to the object to be synchronized is uploaded to a message queue of the server, and the server performs data synchronization according to the message queue. In the method, after the client uploads the object to one cloud platform, the server can realize data synchronization among a plurality of cloud platforms through the message queue, and the client uploads one copy of data to realize data synchronization among mixed clouds, so that the data transmission speed and the flexibility of data transmission can be further improved.
The embodiment of the invention also provides another data synchronization method, which is realized on the basis of the method of the embodiment; the method mainly describes a specific implementation mode of uploading an object identifier of an object to be synchronized to a message queue preset in a server.
Based on the above description, refer to the flowchart of another data synchronization method shown in fig. 5, which includes the following steps:
step S502, receiving the object to be synchronized uploaded by the user and the object identification of the object to be synchronized.
Step S504, the object to be synchronized is uploaded to the first cloud platform.
Step S506, it is determined whether the object to be synchronized is successfully uploaded to the first cloud platform. If yes, go to step S508; if not, step S514 is performed.
Determining whether the object to be synchronized is successfully uploaded to the first cloud platform, and continuously sending the object identification with the synchronized object to a message queue of the server only after the object to be synchronized is successfully uploaded; if the uploading fails, a message of the uploading failure needs to be returned to inform the user of the uploading failure. When the object to be synchronized is successfully uploaded to the first cloud platform, the first cloud platform sends a corresponding message indicating successful uploading to the client, and after the client receives the message indicating successful uploading, the uploading is successful; otherwise, the uploading failure is indicated.
Step S508, the object identifier of the object to be synchronized is uploaded to a message queue preset in the server.
Step S510, determine whether the object id of the object to be synchronized is successfully uploaded to the message queue. If not, go to step S512; if so, the process is ended.
After the client uploads the object identifier of the object to be synchronized to the message queue of the client, whether the uploading is successful or not needs to be confirmed, and if the uploading is successful, the process is finished; if the uploading fails, the data synchronization is considered to have errors, and the data synchronization is abandoned. When the object identification of the object to be synchronized is successfully uploaded to the message queue, the message queue sends a corresponding message indicating successful uploading to the client, and after the client receives the message indicating successful uploading, the message indicates successful uploading; otherwise, the uploading failure is indicated.
And S512, deleting the object to be synchronized from the first cloud platform.
Abandoning this data synchronization requires deleting the object with synchronization that was uploaded to the first cloud platform before. For example, the client sends an instruction for deleting the object to be synchronized to the first cloud platform, and the first cloud platform deletes the object to be synchronized according to the instruction. In the step executing process, if a certain step fails, besides returning a failure message, the failed step is rolled back, that is, the first cloud platform, the second cloud platform and the message queue are returned to the states before all the steps are executed, so as to maintain the consistency of data. For example: and if the object identifier of the object to be synchronized is not successfully uploaded to the message queue from the client, deleting the object to be synchronized corresponding to the object identifier from the first cloud platform, and ensuring that the object to be synchronized does not exist in the first cloud platform or the second cloud platform.
And step S514, returning a message of uploading failure.
After deleting the object to be synchronized, the first cloud platform also returns an upload failure message to the client to inform the user that the data synchronization fails.
In the above manner, whether the object to be synchronized is successfully uploaded to the first cloud platform or not is judged, whether the object identification of the object to be synchronized is successfully uploaded to the message queue or not is judged, different measures are taken for different judgment results, it is guaranteed that a user can be timely reminded of the result of the failure of the uploading when the uploading fails, the previously uploaded data is deleted, the integrity and the reliability of a data synchronization process are guaranteed, and confusion in the data synchronization process is avoided.
For the whole process of the equipment terminal and the server, taking the example that the client uploads to the private cloud first and then synchronizes the private cloud to the public cloud: reference may be made to a schematic diagram of a data synchronization method shown in fig. 6, as shown in fig. 6:
step 1, preparing a private cloud and public cloud environment. And starting the message queue module and starting the data monitoring module. The client installs the SDK, and when the client initializes, IP addresses, passwords and the like of private cloud and public cloud and the service type and address of the message queue need to be configured;
and 2, the client specifies the uploaded object and the uploaded object identifier through the SDK and initiates an uploading request to the private cloud.
Step 3, if the execution of the step 2 fails, returning to the client side that the client side fails, and finishing uploading; if the step 2 is successfully executed, the SDK uploads the object identifier to a message queue module;
step 4, if the execution of the step 3 fails, deleting the object uploaded by the private cloud, returning the client end to fail, and finishing the uploading; if the step 3 is successfully executed, returning to the client for successful uploading;
step 5, the storage synchronization module acquires an object identifier from the message queue in real time, reads the object identifier from the private cloud, downloads the object according to the object identifier of the private cloud, and forwards the object to the public cloud;
and 6, if the synchronization in the step 5 fails, forwarding the object identifier to a failure queue in the message queue. The storage synchronization module can regularly acquire the object identification from the failure queue according to the configuration file and perform resynchronization;
and 7, after starting, regularly acquiring the object identifications of the private cloud and the public cloud, and outputting monitoring indexes such as the total number of the object identifications of the public cloud, the total number of the object identifications of the private cloud and the asynchronous object identifications by the log.
It should be noted that the above method embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other.
Corresponding to the method embodiment, the embodiment of the invention provides a data synchronization device, which is arranged on a server, wherein the server is respectively in communication connection with a first cloud platform and a second cloud platform; fig. 7 is a schematic structural diagram of a data synchronization apparatus, which includes:
an object identifier obtaining module 71, configured to obtain an object identifier of an object to be synchronized from a preset message queue; the method comprises the following steps that an object identifier of an object to be synchronized is uploaded to a message queue by a client in advance;
an object reading module 72, configured to read an object to be synchronized corresponding to an object identifier from the first cloud platform;
and the object synchronization module 73 is configured to synchronize the read object to be synchronized to the second cloud platform.
According to the data synchronization device provided by the embodiment of the invention, after a client uploads an object to be synchronized to a cloud platform in a hybrid cloud, an object identifier of the object to be synchronized is uploaded to a message queue of a server; and then the server acquires the object identification of the object to be synchronized from the message queue, reads the object to be synchronized corresponding to the object identification from the first cloud platform, and further synchronizes the object to be synchronized to the second cloud platform.
Further, in the above manner, after the client uploads the object to one cloud platform, the server can implement data synchronization between the plurality of cloud platforms through the message queue, and this manner that the client uploads one copy of data can implement data synchronization between the hybrid clouds can further improve data transmission speed and flexibility of data transmission.
In some embodiments, the above apparatus further comprises: the first judgment module is used for judging whether the object to be synchronized is successfully synchronized to the second cloud platform; the object identification sending module is used for sending the object identification of the object to be synchronized to a preset standby queue if the object identification of the object to be synchronized is not sent to the preset standby queue; and the standby queue synchronization module is used for successfully synchronizing the object to be synchronized to the second cloud platform through the standby queue.
In some embodiments, the standby queue synchronization module is to: and according to a preset time interval, acquiring the object identification of the object to be synchronized from the standby queue, and continuing to execute the step of reading the object to be synchronized corresponding to the object identification from the first cloud platform until the object to be synchronized is successfully synchronized to the second cloud platform.
In some embodiments, the above apparatus further comprises: the object state data acquisition module is used for acquiring object state data of the first cloud platform and the second cloud platform; the object state data comprises object identifications of objects stored in the platform; the state monitoring log output module is used for outputting a state monitoring log according to the object state data; the status monitoring log includes: the total number of object identifications of the first cloud platform, the total number of object identifications of the second cloud platform, and the object identifications of objects stored only in the first cloud platform or the second cloud platform.
In some embodiments, the first cloud platform comprises a private cloud platform and the second cloud platform comprises a public cloud platform; or the first cloud platform comprises a public cloud platform, and the second cloud platform comprises a private cloud platform.
Corresponding to the method embodiment, the embodiment of the invention provides another data synchronization device, which is arranged on a terminal device, wherein the terminal device is respectively in communication connection with a server, a first cloud platform and a second cloud platform; fig. 8 is a schematic structural diagram of another data synchronization apparatus, which includes:
a to-be-synchronized object determining module 81, configured to determine an object to be synchronized;
the object uploading module 82 is used for uploading the object to be synchronized to the first cloud platform;
the object identifier uploading module 83 is configured to upload an object identifier of an object to be synchronized to a preset message queue in the server, so as to obtain the object identifier of the object to be synchronized from the preset message queue through the server, read the object to be synchronized corresponding to the object identifier from the first cloud platform, and synchronize the read object to be synchronized to the second cloud platform.
In another data synchronization apparatus provided in the embodiment of the present invention, after a server of a terminal device sends an object to be synchronized specified by a user to a first cloud platform, an object identifier corresponding to the object to be synchronized is uploaded to a message queue of the server, and the server performs data synchronization according to the message queue. In the mode, the client only needs to upload one part of data to realize data synchronization between the hybrid clouds, so that the data transmission speed can be effectively improved; compatibility of the first cloud platform and the second cloud platform is omitted, and flexibility of data transmission can be enhanced; the data are synchronized through the message queue, the method can be applied to various mixed clouds, and therefore the method has universality.
In some embodiments, the object identification upload module is to: judging whether the object to be synchronized is successfully uploaded to a first cloud platform; and if so, uploading the object identification of the object to be synchronized to a preset message queue in the server.
In some embodiments, the above apparatus further comprises: the second judgment module is used for judging whether the object identification of the object to be synchronized is successfully uploaded to the message queue; and the object to be synchronized deleting module is used for deleting the object to be synchronized from the first cloud platform if the object to be synchronized is not synchronized.
The data synchronization device provided by the embodiment of the invention has the same technical characteristics as the data synchronization method provided by the embodiment, so that the same technical problems can be solved, and the same technical effects can be achieved.
The embodiment of the invention also provides a server and a terminal device, which are used for operating the data synchronization method; referring to fig. 9, a schematic structural diagram of a server or a terminal device includes a memory 100 and a processor 101, where the memory 100 is used for storing one or more computer instructions, and the one or more computer instructions are executed by the processor 101 to implement the data synchronization method.
Further, the server shown in fig. 9 further includes a bus 102 and a communication interface 103, and the processor 101, the communication interface 103, and the memory 100 are connected through the bus 102.
The Memory 100 may include a high-speed Random Access Memory (RAM) and may further include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The communication connection between the network element of the system and at least one other network element is realized through at least one communication interface 103 (which may be wired or wireless), and the internet, a wide area network, a local network, a metropolitan area network, and the like can be used. The bus 102 may be an ISA bus, PCI bus, EISA bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 9, but this does not indicate only one bus or one type of bus.
The processor 101 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 101. The Processor 101 may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the device can 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. The various methods, steps and logic blocks disclosed in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 100, and the processor 101 reads the information in the memory 100, and completes the steps of the method of the foregoing embodiment in combination with the hardware thereof.
The embodiment of the present invention further provides a computer-readable storage medium, where the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are called and executed by a processor, the computer-executable instructions cause the processor to implement the data synchronization method.
The data synchronization method, the data synchronization device, and the computer program product of the terminal device provided in the embodiments of the present invention include a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute the method in the foregoing method embodiments, and specific implementation may refer to the method embodiments, and will not be described herein again.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the apparatus and/or the terminal device described above may refer to the corresponding process in the foregoing method embodiment, and is not described herein again.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present invention, which are used for illustrating the technical solutions of the present invention and not for limiting the same, and the protection scope of the present invention is not limited thereto, although the present invention is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope of the present disclosure; such modifications, changes or substitutions do not depart from the spirit and scope of the embodiments of the present invention, and they should be construed as being included therein. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (13)
1. A data synchronization method is applied to a server, and comprises the following steps:
acquiring an object identifier of an object to be synchronized from a preset message queue; the object identification of the object to be synchronized is uploaded to the message queue by a client in advance;
reading an object to be synchronized corresponding to the object identification from a first cloud platform;
and synchronizing the read object to be synchronized to a second cloud platform.
2. The method according to claim 1, wherein after the step of synchronizing the read object to be synchronized to the second cloud platform, the method further comprises:
judging whether the object to be synchronized is successfully synchronized to the second cloud platform;
if not, sending the object identification of the object to be synchronized to a preset standby queue;
and successfully synchronizing the object to be synchronized to the second cloud platform through the standby queue.
3. The method of claim 2, wherein the step of successfully synchronizing the object to be synchronized to the second cloud platform via the standby queue comprises:
and according to a preset time interval, acquiring the object identifier of the object to be synchronized from the standby queue, and continuing to execute the step of reading the object to be synchronized corresponding to the object identifier from the first cloud platform until the object to be synchronized is successfully synchronized to the second cloud platform.
4. The method according to claim 1, wherein after the step of synchronizing the read object to be synchronized to the second cloud platform, the method further comprises:
acquiring object state data of the first cloud platform and the second cloud platform; wherein the object state data comprises object identifiers of objects stored within the platform;
outputting a state monitoring log according to the object state data; the status monitoring log includes: a total number of object identifications of the first cloud platform, a total number of object identifications of the second cloud platform, and an object identification of an object stored only in the first cloud platform or the second cloud platform.
5. The method of any of claims 1 to 4, wherein the first cloud platform comprises a private cloud platform and the second cloud platform comprises a public cloud platform;
or the first cloud platform comprises a public cloud platform, and the second cloud platform comprises a private cloud platform.
6. A data synchronization method is applied to a terminal device, and comprises the following steps:
determining an object to be synchronized;
uploading the object to be synchronized to a first cloud platform;
uploading the object identification of the object to be synchronized to a preset message queue in a server, so as to obtain the object identification of the object to be synchronized from the preset message queue through the server, reading the object to be synchronized corresponding to the object identification from the first cloud platform, and synchronizing the read object to be synchronized to the second cloud platform.
7. The method according to claim 6, wherein the step of uploading the object identifier of the object to be synchronized to a message queue preset in the server comprises:
judging whether the object to be synchronized is successfully uploaded to the first cloud platform;
and if so, uploading the object identification of the object to be synchronized to a preset message queue in the server.
8. The method according to claim 6 or 7, wherein after the step of uploading the object identifier of the object to be synchronized to a message queue preset in the server, the method further comprises:
judging whether the object identification of the object to be synchronized is successfully uploaded to the message queue;
and if not, deleting the object to be synchronized from the first cloud platform.
9. A data synchronization apparatus, wherein the apparatus is provided in a server, the apparatus comprising:
the object identification acquisition module is used for acquiring the object identification of the object to be synchronized from a preset message queue; the object identification of the object to be synchronized is uploaded to the message queue by a client in advance;
the object reading module is used for reading an object to be synchronized corresponding to the object identifier from the first cloud platform;
and the object synchronization module is used for synchronizing the read object to be synchronized to the second cloud platform.
10. A data synchronization device, characterized in that, the device is arranged in a terminal device, the device includes:
the device comprises a to-be-synchronized object determining module, a synchronization module and a synchronization module, wherein the to-be-synchronized object determining module is used for determining an object to be synchronized;
the object uploading module is used for uploading the object to be synchronized to a first cloud platform;
and the object identifier uploading module is used for uploading the object identifier of the object to be synchronized to a preset message queue in a server, so that the object identifier of the object to be synchronized is acquired from the preset message queue through the server, the object to be synchronized corresponding to the object identifier is read from the first cloud platform, and the read object to be synchronized is synchronized to the second cloud platform.
11. A server comprising a processor and a memory, the memory storing computer-executable instructions executable by the processor to perform the steps of the data synchronization method of any one of claims 1 to 5.
12. A terminal device comprising a processor and a memory, the memory storing computer-executable instructions executable by the processor, the processor executing the computer-executable instructions to implement the steps of the data synchronization method of any one of claims 6 to 8.
13. A computer-readable storage medium having stored thereon computer-executable instructions that, when invoked and executed by a processor, cause the processor to perform the steps of the data synchronization method of any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910939061.7A CN110602250A (en) | 2019-09-29 | 2019-09-29 | Data synchronization method and device, server and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910939061.7A CN110602250A (en) | 2019-09-29 | 2019-09-29 | Data synchronization method and device, server and terminal equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110602250A true CN110602250A (en) | 2019-12-20 |
Family
ID=68865073
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910939061.7A Pending CN110602250A (en) | 2019-09-29 | 2019-09-29 | Data synchronization method and device, server and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110602250A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112905320A (en) * | 2021-02-05 | 2021-06-04 | 北京邮电大学 | System, method and device for executing tasks of Internet of things |
| CN113133107A (en) * | 2019-12-30 | 2021-07-16 | 北京百度网讯科技有限公司 | Method and device for synchronizing information |
| CN113242313A (en) * | 2021-05-28 | 2021-08-10 | 北京达佳互联信息技术有限公司 | Data synchronization method, system, device, server and storage medium |
| CN113407500A (en) * | 2021-06-21 | 2021-09-17 | 北京金山云网络技术有限公司 | Data synchronization method, device, cloud platform, system and storage medium |
| CN113746931A (en) * | 2021-09-10 | 2021-12-03 | 联想(北京)有限公司 | Data synchronization method and device |
| CN113973075A (en) * | 2020-07-22 | 2022-01-25 | 北京金山云网络技术有限公司 | Data processing method and device |
| CN114567644A (en) * | 2022-02-21 | 2022-05-31 | 深圳希施玛数据科技有限公司 | Data synchronization method and device and electronic equipment |
| CN115640100A (en) * | 2022-11-08 | 2023-01-24 | 安超云软件有限公司 | Virtual machine information synchronization method and computer readable medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106095957A (en) * | 2016-06-16 | 2016-11-09 | 北京航空航天大学 | Cross-domain many wave files synchronous method of distributed file system and device |
| CN107277152A (en) * | 2017-06-29 | 2017-10-20 | 郑州云海信息技术有限公司 | A kind of public cloud data safety backup system |
| CN109885617A (en) * | 2019-01-29 | 2019-06-14 | 中国工商银行股份有限公司 | The method of data synchronization and device of Distributed Heterogeneous Database system |
-
2019
- 2019-09-29 CN CN201910939061.7A patent/CN110602250A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106095957A (en) * | 2016-06-16 | 2016-11-09 | 北京航空航天大学 | Cross-domain many wave files synchronous method of distributed file system and device |
| CN107277152A (en) * | 2017-06-29 | 2017-10-20 | 郑州云海信息技术有限公司 | A kind of public cloud data safety backup system |
| CN109885617A (en) * | 2019-01-29 | 2019-06-14 | 中国工商银行股份有限公司 | The method of data synchronization and device of Distributed Heterogeneous Database system |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113133107A (en) * | 2019-12-30 | 2021-07-16 | 北京百度网讯科技有限公司 | Method and device for synchronizing information |
| CN113133107B (en) * | 2019-12-30 | 2022-12-23 | 北京百度网讯科技有限公司 | Method and device for synchronizing information |
| CN113973075A (en) * | 2020-07-22 | 2022-01-25 | 北京金山云网络技术有限公司 | Data processing method and device |
| CN112905320A (en) * | 2021-02-05 | 2021-06-04 | 北京邮电大学 | System, method and device for executing tasks of Internet of things |
| CN113242313A (en) * | 2021-05-28 | 2021-08-10 | 北京达佳互联信息技术有限公司 | Data synchronization method, system, device, server and storage medium |
| CN113407500A (en) * | 2021-06-21 | 2021-09-17 | 北京金山云网络技术有限公司 | Data synchronization method, device, cloud platform, system and storage medium |
| CN113746931A (en) * | 2021-09-10 | 2021-12-03 | 联想(北京)有限公司 | Data synchronization method and device |
| CN113746931B (en) * | 2021-09-10 | 2022-11-22 | 联想(北京)有限公司 | Data synchronization method and device |
| CN114567644A (en) * | 2022-02-21 | 2022-05-31 | 深圳希施玛数据科技有限公司 | Data synchronization method and device and electronic equipment |
| CN114567644B (en) * | 2022-02-21 | 2023-10-20 | 深圳希施玛数据科技有限公司 | Data synchronization method and device and electronic equipment |
| CN115640100A (en) * | 2022-11-08 | 2023-01-24 | 安超云软件有限公司 | Virtual machine information synchronization method and computer readable medium |
| CN115640100B (en) * | 2022-11-08 | 2023-05-23 | 安超云软件有限公司 | Virtual machine information synchronization method and computer readable medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110602250A (en) | Data synchronization method and device, server and terminal equipment | |
| US10805363B2 (en) | Method, device and system for pushing file | |
| US11940965B2 (en) | Data migration method and apparatus | |
| CN109788068B (en) | Heartbeat state information reporting method, device and equipment and computer storage medium | |
| CN108347476B (en) | Cross-machine-room data synchronization method and device and server | |
| CN109561054B (en) | Data transmission method, controller and access device | |
| EP3493468A1 (en) | Network function processing method and related device | |
| CN110650098B (en) | Variable frequency acquisition method and device for data of Internet of things | |
| CN112965817B (en) | Resource management method and device and electronic equipment | |
| CN111291008A (en) | Data processing method, device, system, electronic equipment and computer storage medium | |
| CN106817387B (en) | Data synchronization method, device and system | |
| CN112612769A (en) | File processing method, device and storage medium | |
| CN111988391A (en) | Message sending method and device | |
| CN109788251B (en) | Video processing method, device and storage medium | |
| CN108038127B (en) | Data synchronization method, device, terminal equipment and storage medium | |
| CN111092956A (en) | Resource synchronization method, device, storage medium and equipment | |
| CN111935029B (en) | Gateway load balancing method and device, storage medium and electronic equipment | |
| CN114240651A (en) | Cross-chain transaction sending method, device, equipment and storage medium | |
| CN114625578A (en) | Data processing method and device, electronic equipment and computer readable storage medium | |
| CN109962962B (en) | Socket connection method and device | |
| CN112383617A (en) | Method, device, terminal equipment and medium for long connection | |
| CN111464395A (en) | Method and device for creating block chain and readable storage medium | |
| CN112055058A (en) | Data storage method and device and computer readable storage medium | |
| CN111596933A (en) | File processing method and device, electronic equipment and computer readable storage medium | |
| CN110633164B (en) | Message-oriented middleware fault recovery method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20191220 |