CN111143745A - HTML-based data synchronization and interaction method and system - Google Patents
HTML-based data synchronization and interaction method and system Download PDFInfo
- Publication number
- CN111143745A CN111143745A CN201911371302.9A CN201911371302A CN111143745A CN 111143745 A CN111143745 A CN 111143745A CN 201911371302 A CN201911371302 A CN 201911371302A CN 111143745 A CN111143745 A CN 111143745A
- Authority
- CN
- China
- Prior art keywords
- data
- server
- record
- database
- 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
- 238000000034 method Methods 0.000 title claims abstract description 51
- 230000003993 interaction Effects 0.000 title claims abstract description 33
- 230000008569 process Effects 0.000 claims abstract description 19
- 230000004048 modification Effects 0.000 claims description 58
- 238000012986 modification Methods 0.000 claims description 58
- 238000012545 processing Methods 0.000 claims description 34
- 230000009191 jumping Effects 0.000 claims description 14
- 230000001360 synchronised effect Effects 0.000 claims description 14
- 238000004891 communication Methods 0.000 claims description 4
- 238000005516 engineering process Methods 0.000 claims description 2
- 238000004519 manufacturing process Methods 0.000 claims description 2
- 230000007547 defect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000009826 distribution Methods 0.000 description 2
- 230000008520 organization Effects 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 238000003860 storage Methods 0.000 description 1
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/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/548—Queue
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method and a system for data synchronization and interaction based on HTML (Hypertext markup language), which can synchronize and interact data among a plurality of third-party systems by means of a server, store the unified data in a database and avoid the problems of inconsistency and low synchronization efficiency of a plurality of third-party data in the synchronization process.
Description
Technical Field
The invention relates to the field of data processing, in particular to a method and a system for data synchronization and interaction based on HTML (hypertext markup language).
Background
In an information system with multiple organizations or multiple places and having data synchronization requirements, the data synchronization is performed by establishing a direct connection relationship between data systems or databases among the organizations or places to be synchronized, and performing the data synchronization by means of middleware or communication software. The most serious drawback of the data synchronization in the above manner is that data synchronization is not uniform between systems or databases that need to perform data synchronization, and data sent by the same system at different time points may be inconsistent. Meanwhile, no effective data synchronization control means exists, so that the synchronization efficiency is reduced, and further the data synchronization is not timely. In addition, the systems have different purposes, and thus have a problem of poor data compatibility.
Aiming at the defects, the invention provides a method for processing data pushing and pulling requests through an HTML format flow queue to carry out uniform data synchronization and interaction among all third-party systems accessed to a synchronization system, and the method overcomes the defects.
Disclosure of Invention
The invention provides a method and a system for data synchronization and interaction based on HTML (hypertext markup language), and the specific scheme is as follows:
a data synchronization and interaction method based on HTML comprises two types of operations of data pushing and data pulling, and is characterized in that the data pushing and data pulling operations are processed in an HTML format flow queue mode, and the specific processing mode is as follows:
s1: a request for modifying data is made by a third-party system, and the data modification record is moved into a submission queue;
s2: the server acquires a record with the earliest trigger time from the submission queue for processing;
s3: if the server processing is successful, deleting the successfully processed record, if the server processing is failed, moving the unsuccessfully processed record from the submission queue into the retry queue, and simultaneously moving the record with the same ID as the failed record from the submission queue into the retry queue;
s4: checking whether the submission queue is empty, if the submission queue is not empty, jumping to step S2 for processing, and if the submission queue is empty, checking whether the retry queue is empty;
s5: if the retry queue is not empty, after waiting for a period of time, all data modification records are moved into the commit queue, and the process goes to step S1, and if the retry queue is empty, the synchronization process is ended.
Further, the processing flow of the data pushing operation at the server and the database side is as follows:
s211: the third-party system pushes data to the server and adds a pushing request into a submission queue;
s212: updating the main data set and storing the modification record by the server, and transferring the main data set to the database to store the updated main data set;
s213: the database returns a main data set updating success message to the server;
s214: and the server returns a main data set updating success message to the third-party system.
The processing flow of the data pulling operation at the server and the database side is as follows:
s221: the third-party system sends a data pulling request to the server;
s222: the server inquires the modification record which is not synchronized by the user from the database;
s223: the database returns the modification record which is not synchronized by the user, and the modification record is forwarded to a third-party system through the server;
s224: the third-party system synchronizes in the self-established database and sends back the successfully synchronized modification record ID to the server;
s225: and after the server marks the corresponding modification record as 'synchronized', synchronizing the modification record to the database.
Further, the data synchronization and interaction method includes the step that an OA system serving as a third-party system interacts with a server and a database at the rear end of the server, and the specific process is as follows:
s31: in a certain time period, the server pulls a batch of unsynchronized data modification records and checks whether the unsynchronized data modification records are successfully pulled or not;
s32: if the unsynchronized data modification records are successfully pulled, selecting one data modification record with the earliest trigger time for operation, and if the data modification records are not successfully pulled, pulling again in the next period;
s33: converting the new data to be modified into a format compatible with the OA system, and submitting the format to the OA system;
s34: if the submission is successful, submitting a synchronization success report to the server, if the submission is unsuccessful, firstly alarming to inform relevant personnel, then skipping the record and the record with the same data ID, selecting a data record with the earliest trigger time from the pulled data modification records, and jumping to the step S33;
s35: checking if there are more modified records, jumping to step S33, if there are no more modified records, then pulling a new batch of unsynchronized data modified records again.
Further, the communication of pulling the un-synchronized data modification record, submitting the data to the OA system, and submitting the synchronization success report to the server is completed through the API interface of the server.
Further, the data synchronization and interaction method includes interacting with the server and a database at the back end thereof by using a nudge platform as a third-party system, and the specific process is as follows:
s51: in a certain time period, the server pulls a batch of unsynchronized data modification records and checks whether the unsynchronized data modification records are successfully pulled or not;
s52: if the unsynchronized data modification records are successfully pulled, selecting one data modification record with the earliest trigger time for operation, and if the data modification records are not successfully pulled, pulling again in the next period;
s53: converting new data to be modified into a format compatible with the nudge platform, and submitting the nudge platform;
s54: if the submission is successful, submitting a synchronization success report to the server, if the submission is unsuccessful, firstly alarming to inform relevant personnel, then skipping the record and the record with the same data ID, selecting a data record with the earliest trigger time from the pulled data modification records, and jumping to the step S33;
s55: checking if there are more modified records, jumping to step S33, if there are no more modified records, then pulling a new batch of unsynchronized data modified records again.
Further, the communication of pulling the non-synchronous data modification record, submitting the data to the nudge platform and submitting the synchronous success report to the server is completed through an API (application programming interface) of the server.
Further, the specific process of the alarm notification is as follows:
s71: reading the alarm message from the message queue, checking whether the new alarm message is read, if the new alarm message is read, checking whether the number of the alarm message reaches the set limit, and if the new alarm message is not read, checking whether the read alarm message exists;
s72: if the number of the read alarm messages does not reach the set limit, reading the alarm messages from the message queue again after waiting for a short period, and if the alarm messages reach the set limit, jumping to the step S74;
s73: if no alarm message is detected to be read, waiting for a long period, and then jumping to step 71;
s74: and deleting repeated alarm messages in the read alarm messages, removing the sent alarm messages, summarizing the processed alarm messages, sending alarm notification to related personnel, and skipping to the step 71.
Further, the method can set up a database cluster and a plurality of servers to process data synchronization requests submitted by a plurality of third-party systems.
An HTML-based data synchronization and interaction system comprising a third party system, a server and a database, wherein:
the third-party system is a data production and use terminal and submits data pushing and data pulling requests to a server;
the server processes data pushing and/or data pulling requests submitted by a third-party system in a queue mode;
the database is used for storing the data processed by the server;
the method is characterized in that: the system adopts the method of any one of claims 1-8 for data synchronization and data interaction.
Further, the third-party system can be provided with a plurality of systems, and the systems are connected with the server in a star shape according to business relations; the server can be provided with a plurality of servers which are connected with the database in a star shape; the database may be a database cluster.
Furthermore, a database or a database cluster used by the system is erected by adopting the MongoDB technology.
By the data synchronization and interaction method and system, data synchronization and interaction can be uniformly performed among a plurality of third-party systems, real-time consistency of data contents among the plurality of third-party systems is achieved, and reliability and consistency of data when different systems are intercommunicated and interconnected are improved.
Drawings
FIG. 1 is a flow diagram of queue processing in the present invention;
FIG. 2 is a flow chart of the present invention for pushing data to a third-party OA system;
FIG. 3 is a flow chart of the present invention for data push for a third party nudge platform;
FIG. 4 is a flow chart of the present invention for handling alarm messages during data push;
FIG. 5 is a schematic diagram of the system of the present invention;
FIG. 6 is a data distribution schema design of various systems connected in an embodiment of the present invention;
FIG. 7 is a layout of distribution patterns for the various fields of an organization according to an embodiment of the present invention.
Detailed Description
The data synchronization and interaction method and system of the present invention will be described in further detail with reference to the accompanying drawings:
in an embodiment of the present invention, the data synchronization and interaction system is divided into three parts, namely a third-party system, a server and a database, wherein the third-party system refers to various specific functional systems that need to be intercommunicated and interconnected, such as an OA system, such as an information nudging system, such as a wechat public platform, and the like. Depending on the size of the data volume, the synchronized data may be directly stored in a database deployed in a server hard disk, or may be separately deployed in an independent storage server database. In this embodiment, each server in the system is connected to at least 1 third-party system, and the system has a plurality of servers, and the plurality of servers are connected to one database cluster. The connection mode forms a huge data synchronous interaction system.
In the system, the data synchronization mode is divided into two operations of pushing data to the server and pulling data by the server by a third-party system. The push data and the pull data are added into a processing flow queue for processing, and each request in the flow queue is transmitted in an HTML format. The advantage of this process is that the HTML language is a mark-up language, and a series of tags are used to represent information, so that various information can be combined into a logic whole, thus the HTML text becomes a descriptive text, which can be communicated between different systems, and the problem of information transmission between different computer languages or architectures is solved. In addition to the flow queue, in order to solve the problem of data synchronization failure, a retry queue is also set up in this embodiment, and is used to store data requests that have failed to synchronize.
As shown in fig. 1, after data is updated, all third-party systems send data pushing requests to the server; and when the third-party data needs to use the data which is not stored locally, sending a data pulling request to the server. When each request is sent, a data modification record ID number is attached to each request, all data push requests and data pull requests are not distinguished in type and need to be edited into HTML texts, the data push requests and the data pull requests are sent to a request queue of a server through an appointed API when the data push requests and the data pull requests are communicated through a system according to the sequence of sending time, and the sending requests enter the queue first. The server extracts 1 request with earliest trigger time from the request queue for processing each time according to the time sequence. If the processing is successful, deleting the record of successful processing from the submission queue, if the processing is failed, moving the data request of failed processing into a retry queue, and sorting and processing the retry queue in a first-in first-out mode as the process queue. And after the server finishes processing a data request in the submission queue, preferentially and continuously processing the data request in the flow queue. After all the data requests in the flow queue are processed, the server determines whether the retry queue is empty, if the retry queue is empty, the data synchronization is finished, and the data synchronization program is restarted in the next period. And if the retry queue is not empty, waiting for 3 minutes, moving the data request in the retry queue into the flow queue, and processing according to the flow of processing the data request in the flow queue.
For each third-party system, the system communicates with the third-party system through a specified API, and data synchronization requests are pulled in batches in a server. The data synchronization and interaction method and system according to the present invention will be described below by taking the OA system as a third party system as an example.
In the server, the data modification records submitted by the OA system within a period of time are pulled through the designated API. If a batch of data modification records are successfully pulled, the server converts the latest data into a data format compatible with the OA system according to the time sequence, and submits the data to the OA system for data updating or returns a message that the data is successfully updated on the server side. And if the data modification record is not pulled successfully, waiting for 3 minutes, and then pulling the data modification record again through the API. Meanwhile, it is also necessary to determine whether the message submission of the OA system is successful. If the submission is successful, continuing to select the next data modification record, and circularly processing according to the flow; and if the submission is unsuccessful, sending an alarm message to a related role defined by the system through the OA system, skipping the currently processed data modification record, and then processing the next data modification record according to the time sequence. And after all the data modification records of the batch are processed, pulling the data modification records again, and processing according to the initial processing sequence.
In addition to being able to interface with the OA system as a third party system, the OA system may also interface with various dedicated systems such as a nudge platform, a wechat platform, a centralized management and control system, a cooperative office system, and a human resource management system. The data modification records from the above system are processed in the same manner as the data modification records process of the OA system described above. Only when the data is converted, the updated data is converted into a data format which can be used by various special systems.
In this embodiment, an OA system, a nudge system, an enterprise wechat platform, and a business trip reporting system are connected to dynamically implement real-time management of personnel, and a specific data update mode is designed as shown in fig. 6.
In the present embodiment, the dynamic update mode design for each field in the organization is shown in fig. 7.
When the updating mode is automatic updating, the data synchronization and interaction method is used for processing, and automatic synchronization and real-time updating of data are achieved. When the updating mode is set to be manually adjusted or not pushed, synchronous updating is carried out in other modes, and the technical scheme recorded in the invention is not used.
The method and system for data synchronization and interaction provided by the present invention are described in detail above, and a specific example is applied in the text to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understand the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and the content of the present specification should not be construed as a limitation to the technical solution of the present invention.
Claims (11)
1. A data synchronization and interaction method based on HTML comprises two types of operations of data pushing and data pulling, and is characterized in that the data pushing and data pulling operations are processed in a process queue mode of an HTML format, and the specific processing mode is as follows:
s1: a request for modifying data is made by a third-party system, and the data modification record is moved into a submission queue;
s2: the server acquires a record with the earliest trigger time from the submission queue for processing;
s3: if the server processing is successful, deleting the successfully processed record, if the server processing is failed, moving the unsuccessfully processed record from the submission queue into the retry queue, and simultaneously moving the record with the same ID as the failed record from the submission queue into the retry queue;
s4: checking whether the submission queue is empty, if the submission queue is not empty, jumping to step S2 for processing, and if the submission queue is empty, checking whether the retry queue is empty;
s5: if the retry queue is not empty, after waiting for a period of time, all data modification records are moved into the commit queue, and the process goes to step S1, and if the retry queue is empty, the synchronization process is ended.
2. The method for data synchronization and interaction according to claim 1, wherein the processing flow of the data push operation on the server and database sides is as follows:
s211: the third-party system pushes data to the server and adds a pushing request into a submission queue;
s212: updating the main data set and storing the modification record by the server, and transferring the main data set to the database to store the updated main data set;
s213: the database returns a main data set updating success message to the server;
s214: and the server returns a main data set updating success message to the third-party system.
The processing flow of the data pulling operation at the server and the database side is as follows:
s221: the third-party system sends a data pulling request to the server;
s222: the server inquires the modification record which is not synchronized by the user from the database;
s223: the database returns the modification record which is not synchronized by the user, and the modification record is forwarded to a third-party system through the server;
s224: the third-party system synchronizes in the self-established database and sends back the successfully synchronized modification record ID to the server;
s225: and after the server marks the corresponding modification record as 'synchronized', synchronizing the modification record to the database.
3. The data synchronization and interaction method according to claim 2, wherein the data synchronization and interaction method includes an OA system as a third-party system interacting with a server and a database at a back end thereof, and the specific process is as follows:
s31: in a certain time period, the server pulls a batch of unsynchronized data modification records and checks whether the unsynchronized data modification records are successfully pulled or not;
s32: if the unsynchronized data modification records are successfully pulled, selecting one data modification record with the earliest trigger time for operation, and if the data modification records are not successfully pulled, pulling again in the next period;
s33: converting the new data to be modified into a format compatible with the OA system, and submitting the format to the OA system;
s34: if the submission is successful, submitting a synchronization success report to the server, if the submission is unsuccessful, firstly alarming to inform relevant personnel, then skipping the record and the record with the same data ID, selecting a data record with the earliest trigger time from the pulled data modification records, and jumping to the step S33;
s35: checking if there are more modified records, jumping to step S33, if there are no more modified records, then pulling a new batch of unsynchronized data modified records again.
4. The method of data synchronization and interaction of claim 3, wherein the communication of pulling the un-synchronized data modification record, submitting the data to the OA system, and submitting the synchronization success report to the server is accomplished through an API of the server.
5. The data synchronization and interaction method according to claim 2, wherein the data synchronization and interaction method includes interacting with a server and a database at a back end thereof as a nudge platform of a third-party system, and the specific process includes:
s51: in a certain time period, the server pulls a batch of unsynchronized data modification records and checks whether the unsynchronized data modification records are successfully pulled or not;
s52: if the unsynchronized data modification records are successfully pulled, selecting one data modification record with the earliest trigger time for operation, and if the data modification records are not successfully pulled, pulling again in the next period;
s53: converting new data to be modified into a format compatible with the nudge platform, and submitting the nudge platform;
s54: if the submission is successful, submitting a synchronization success report to the server, if the submission is unsuccessful, firstly alarming to inform relevant personnel, then skipping the record and the record with the same data ID, selecting a data record with the earliest trigger time from the pulled data modification records, and jumping to the step S33;
s55: checking if there are more modified records, jumping to step S33, if there are no more modified records, then pulling a new batch of unsynchronized data modified records again.
6. The method for data synchronization and interaction according to claim 5, wherein the communication of pulling the un-synchronized data modification record, submitting the data to the nudge platform, and submitting the synchronization success report to the server is performed through an API of the server.
7. The data synchronization and interaction method according to any one of claims 3 and 5, wherein the specific process of the alarm notification is as follows:
s71: reading the alarm message from the message queue, checking whether the new alarm message is read, if the new alarm message is read, checking whether the number of the alarm message reaches the set limit, and if the new alarm message is not read, checking whether the read alarm message exists;
s72: if the number of the read alarm messages does not reach the set limit, reading the alarm messages from the message queue again after waiting for a short period, and if the alarm messages reach the set limit, jumping to the step S74;
s73: if no alarm message is detected to be read, waiting for a long period, and then jumping to step 71;
s74: and deleting repeated alarm messages in the read alarm messages, removing the sent alarm messages, summarizing the processed alarm messages, sending alarm notification to related personnel, and skipping to the step 71.
8. The method for data synchronization and interaction according to claim 1, wherein the method can set up a database cluster and a plurality of servers to process data synchronization requests submitted from a plurality of third-party systems.
9. An HTML-based data synchronization and interaction system comprising a third party system, a server and a database, wherein:
the third-party system is a data production and use terminal and submits data pushing and data pulling requests to a server;
the server processes data pushing and/or data pulling requests submitted by a third-party system in a queue mode;
the database is used for storing the data processed by the server;
the method is characterized in that: the system adopts the method of any one of claims 1-8 for data synchronization and data interaction.
10. The system for data synchronization and interaction according to claim 9, wherein the third-party system may have a plurality of star-connected with the server according to business relationship; the server can be provided with a plurality of servers which are connected with the database in a star shape; the database may be a database cluster.
11. The system for data synchronization and interaction according to claim 10, wherein the database or database cluster used by the system is constructed by using the MongoDB technology.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911371302.9A CN111143745A (en) | 2019-12-27 | 2019-12-27 | HTML-based data synchronization and interaction method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911371302.9A CN111143745A (en) | 2019-12-27 | 2019-12-27 | HTML-based data synchronization and interaction method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111143745A true CN111143745A (en) | 2020-05-12 |
Family
ID=70520744
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911371302.9A Pending CN111143745A (en) | 2019-12-27 | 2019-12-27 | HTML-based data synchronization and interaction method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111143745A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1219257A (en) * | 1996-05-24 | 1999-06-09 | 国际商业机器公司 | Providing communication links in a computer network |
| US7290015B1 (en) * | 2003-10-02 | 2007-10-30 | Progress Software Corporation | High availability via data services |
| CN105740418A (en) * | 2016-01-29 | 2016-07-06 | 杭州亿方云网络科技有限公司 | File monitoring and message pushing based real-time synchronization system |
| CN107659492A (en) * | 2017-10-31 | 2018-02-02 | 珠海信达九州科技有限公司 | A kind of high reliability instant communicating system |
| CN108647237A (en) * | 2018-03-30 | 2018-10-12 | 厦门海迈科技股份有限公司 | Method of data synchronization between isomeric relationship type database |
| CN109067669A (en) * | 2018-09-06 | 2018-12-21 | 华泰证券股份有限公司 | Synchronization call method and application based on asynchronous interface |
-
2019
- 2019-12-27 CN CN201911371302.9A patent/CN111143745A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1219257A (en) * | 1996-05-24 | 1999-06-09 | 国际商业机器公司 | Providing communication links in a computer network |
| US7290015B1 (en) * | 2003-10-02 | 2007-10-30 | Progress Software Corporation | High availability via data services |
| CN105740418A (en) * | 2016-01-29 | 2016-07-06 | 杭州亿方云网络科技有限公司 | File monitoring and message pushing based real-time synchronization system |
| CN107659492A (en) * | 2017-10-31 | 2018-02-02 | 珠海信达九州科技有限公司 | A kind of high reliability instant communicating system |
| CN108647237A (en) * | 2018-03-30 | 2018-10-12 | 厦门海迈科技股份有限公司 | Method of data synchronization between isomeric relationship type database |
| CN109067669A (en) * | 2018-09-06 | 2018-12-21 | 华泰证券股份有限公司 | Synchronization call method and application based on asynchronous interface |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111143352B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN106874334B (en) | Data processing method and device and information processing system | |
| US20090282125A1 (en) | Synchronizing Events Between Mobile Devices and Servers | |
| CN111143382B (en) | Data processing method, system and computer readable storage medium | |
| US10122665B2 (en) | Distributed synchronization data in a message management service | |
| US7917651B2 (en) | Apparatus, system, and method for asynchronous complex inbound transactions from SAP applications using service oriented architecture | |
| CN108701157A (en) | Guaranteed submission result in distributing real time system system | |
| CN113127564B (en) | Parameter synchronization method and device | |
| CN112597249A (en) | Synchronous distribution and storage method and system for service data | |
| CN102625156B (en) | information synchronization method and system | |
| CN110334147A (en) | A kind of method of data synchronization and device | |
| CN113438275A (en) | Data migration method and device, storage medium and data migration equipment | |
| CN111143745A (en) | HTML-based data synchronization and interaction method and system | |
| CN110019131A (en) | A kind of method and apparatus of discs business | |
| US20220382585A1 (en) | Method, apparatus and system for processing data, electronic device, and computer readable medium | |
| CN111581227A (en) | Event pushing method and device, computer equipment and storage medium | |
| CN116662035A (en) | Method and device for processing transaction message of message queue | |
| CN111506668B (en) | Robot cluster intelligent data synchronization method and system | |
| CN117692418A (en) | Message processing method, device, computer equipment and storage medium | |
| CN113641760A (en) | Data synchronization method and device | |
| CN114895955A (en) | Method, device and equipment for controlling metadata version of low-code platform | |
| CN109558417B (en) | Data processing method and system | |
| CN112053150A (en) | Data processing method, device and storage medium | |
| CN113765773B (en) | Method and device for processing communication record | |
| CN114661819A (en) | Database online synchronization method |
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 |
Application publication date: 20200512 |