CN109788053B - Data synchronization method and system - Google Patents
Data synchronization method and system Download PDFInfo
- Publication number
- CN109788053B CN109788053B CN201910007430.9A CN201910007430A CN109788053B CN 109788053 B CN109788053 B CN 109788053B CN 201910007430 A CN201910007430 A CN 201910007430A CN 109788053 B CN109788053 B CN 109788053B
- Authority
- CN
- China
- Prior art keywords
- data
- server
- queue
- synchronized
- consumption
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 36
- 230000001360 synchronised effect Effects 0.000 claims abstract description 229
- 239000000872 buffer Substances 0.000 abstract description 23
- 238000012545 processing Methods 0.000 abstract description 5
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000004590 computer program Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 3
- 238000012550 audit Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 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/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Information Transfer Between Computers (AREA)
- Hardware Redundancy (AREA)
Abstract
The present application relates to data processing technologies, and in particular, to a data synchronization method and system. The method comprises the following steps: the service server pushes data to be synchronized to the queue server; the queue server determines a queue identification corresponding to the data to be synchronized; the queue server caches the data to be synchronized into a data cache queue corresponding to the queue identification; the consumption server sends a data synchronization request to the queue server; the data synchronization request carries a queue identification; and the queue server responds to the data synchronization request and feeds back the data to be synchronized in the data buffer queue corresponding to the queue identification. The method can improve the flexibility of data synchronization.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a data synchronization method and system.
Background
With the development of network technology, the internet brings great convenience to daily life of people. People can conduct transactions or data operations and the like on a network through computer devices. Thus, situations often arise where data synchronization between different systems is required. For example, after a user generates an order transaction on the network, an auditor can audit through the service system. Then it is necessary to synchronize the order information in the business system to another query system providing query function so that the user can view the order information at any time.
When data synchronization is performed between different systems, http direct connection is generally used for data synchronization. Data synchronization is performed by adopting an http direct connection mode, so that the system pressure of two synchronous parties is very high under the condition that a large amount of data needs to be synchronized, synchronization abnormity often occurs, and data synchronization is not flexible.
Disclosure of Invention
In view of the above, it is necessary to provide a flexible data synchronization method and system.
A method of data synchronization, comprising:
the service server pushes data to be synchronized to the queue server;
the queue server determines a queue identification corresponding to the data to be synchronized;
the queue server caches the data to be synchronized into a data cache queue corresponding to the queue identification;
the consumption server sends a data synchronization request to the queue server; the data synchronization request carries a queue identification;
and the queue server responds to the data synchronization request and feeds back the data to be synchronized in the data buffer queue corresponding to the queue identification.
A data synchronization system comprises a business server, a queue server and a consumption server;
the service server is used for pushing data to be synchronized to the queue server;
the queue server is used for determining a queue identifier corresponding to the data to be synchronized; caching the data to be synchronized into a data caching queue corresponding to the queue identification;
the consumption server is used for sending a data synchronization request to the queue server; the data synchronization request carries a queue identification;
and the queue server is used for responding to the data synchronization request and feeding back the data to be synchronized in the data buffer queue corresponding to the queue identification.
According to the data synchronization method and system, the service server pushes the data to be synchronized to the queue server, and the queue server receives the data to be synchronized and then determines the queue identification corresponding to the data to be synchronized. And the queue server caches the data to be synchronized into a data cache queue corresponding to the queue identification. The consumption server sends a data synchronization request carrying a queue identification to the queue server, and the queue server responds to the data synchronization request and feeds back data to be synchronized in a data cache queue corresponding to the queue identification. Therefore, when data synchronization is needed between the service server and the consumption server, the data to be synchronized can be correspondingly cached through the queue server. And when needed, the consumption server can acquire the data to be synchronized from the queue server according to the queue identification. Therefore, when a large amount of data needs to be synchronized, the processing pressure of the service server and the consumption server can be greatly relieved, and the flexibility of data synchronization is improved.
Drawings
FIG. 1 is a diagram illustrating an exemplary implementation of a data synchronization method;
FIG. 2 is a flow diagram illustrating a method for data synchronization in one embodiment;
FIG. 3 is a flow chart illustrating a data synchronization method according to another embodiment;
FIG. 4 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The data synchronization method provided by the application can be applied to the application environment shown in fig. 1. The first terminal 110 communicates with the service server 101 through a network, the service server 101 communicates with the queue server 102 through a network, the queue server 102 communicates with the consumption server 103, and the consumption server 103 communicates with the second terminal 120.
The service server 101 obtains the data to be synchronized through the first terminal 110, and the service server 101 pushes the data to be synchronized to the queue server 102. The queue server 102 determines a queue identifier corresponding to the data to be synchronized, and buffers the data to be synchronized into a data buffer queue corresponding to the queue identifier. The consumption server 103 sends a data synchronization request carrying the queue identification to the queue server 102. The queue server 102 feeds back the data to be synchronized in the data buffer queue corresponding to the queue identification in response to the data synchronization request. The second terminal 120 triggers a data operation instruction for the consumption server 103 and acquires corresponding data from the data synchronized by the consumption server 103.
The first terminal 110 and the second terminal 120 may be, but are not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The business server 101, the queue server 102, and the consumption server 103 may be implemented by separate servers or a server cluster composed of a plurality of servers.
In one embodiment, as shown in fig. 2, a data synchronization method is provided, which is exemplified by the application of the method to the data synchronization system in fig. 1, and includes the following steps:
s202, the service server pushes the data to be synchronized to the queue server.
Wherein, the business server is a server for providing business services. The business service may specifically be a loan business, an order generation business, an order approval business, or an information promotion business. A queue server is a server used to cache data. The queue server may specifically be an ActiveMQ (Message middleware system), Kafka (publish-subscribe Message queue), MSMQ (MicroSoft Message queue), or the like. Data to be synchronized is data that needs to be synchronized from one system to another. In this embodiment, the system may be implemented by a stand-alone server or a cluster of servers.
Specifically, the service server may push current data to be synchronized to the queue server in real time or at regular time. The queue server can receive the data to be synchronized pushed by the service server through network connection.
For example, when the business server is an order approval server, the order approval server may push all information related to the order (e.g., order audit status information) generated within a preset time period to the queue server.
In one embodiment, the queue server may provide an external API (Application Programming Interface). The service server can send the data to be synchronized to the queue server by calling the API interface provided by the queue server.
In one embodiment, the service server includes a plurality of data acquisition modules, and each data acquisition module has a unique identifier, which may be referred to as a source identifier in this embodiment. The service server can acquire the data to be synchronized through the data acquisition modules and then push the data to be synchronized to the queue server.
In one embodiment, after acquiring the data to be synchronized, the service server determines a queue identifier associated with the source identifier according to the source identifier. The service server can add the queue identification to the data to be synchronized and push the queue identification to the queue server.
In one embodiment, a client corresponding to the service server runs on the terminal, and the user can input corresponding data in the client, for example, the user can input transaction information in a transaction interface provided by the client. Or, the user may open a web interface provided by the service server through the terminal, and the user may input corresponding data in the web interface. Furthermore, the terminal can generate the data to be synchronized according to the data input by the user. For example, the terminal may generate order related information based on transaction information input by the user. The order related information may specifically include current time, order number, user identifier, order amount, order status, and the like. The order related information is the data to be synchronized.
In one embodiment, the service server may provide an API interface, the terminal may communicate with the service server through the API interface provided by the service server, and the staff member may transmit the data to be synchronized to the service server through the API interface. Data to be synchronized, such as promotional advertising information about a product, etc.
S204, the queue server determines a queue identification corresponding to the data to be synchronized.
Specifically, after the queue server obtains the data to be synchronized, a source of the data to be synchronized can be determined, and a corresponding queue identifier can be determined according to the source. In one embodiment, an association table corresponding to the source identifier and the queue identifier may be stored in the queue server. For example, if the a source corresponds to the a queue, the queue server stores the data to be synchronized obtained from the a source into the data buffer queue corresponding to the a queue.
In one embodiment, after the service server obtains the data to be synchronized, the corresponding queue identifier may be added to the data to be synchronized. After the queue server obtains the data to be synchronized, the queue server can extract the queue identification from the data to be synchronized.
S206, the queue server buffers the data to be synchronized into a data buffer queue corresponding to the queue identification.
Wherein the cache is used for temporarily storing data. A data buffer queue is a queue for temporarily storing data. Specifically, the queue server may buffer the received data to be synchronized into the data buffer queue identified by the queue identifier according to the corresponding queue identifier.
In one embodiment, the queue server may determine the acquisition time of the data to be synchronized, and sequentially buffer the data to be synchronized to the tail of the data buffer queue corresponding to the queue identifier according to the time sequence.
S208, the consumption server sends a data synchronization request to the queue server; the data synchronization request carries a queue identification.
Wherein, the consumption server is a server for receiving data to be synchronized. The consumption server may specifically be a data analysis server, an alert server, or a server providing mass messaging, etc.
Specifically, the consumption server may send a data synchronization request carrying the queue identifier to the queue server according to the load status of the consumption server. The consuming server may determine a current load state and may initiate a data synchronization request to the queue server when the consuming server is in a low load state. Alternatively, the consumption server may automatically send the data synchronization request to the queue server at preset time intervals.
In one embodiment, the consumption server comprises a plurality of consumption modules, and each consumption module can read the data to be synchronized in the corresponding data cache queue from the queue server in parallel according to the self load state or timing.
In one embodiment, each consumption module has a unique identification, which may be referred to herein as a target party identification. The consumption server can store an incidence relation table corresponding to the target party identification and the queue identification. For example, if the a' target corresponds to the a queue, the data synchronization request sent by the consumption server carries the queue id of the a queue.
S210, the queue server responds to the data synchronization request and feeds back the data to be synchronized in the data buffer queue corresponding to the queue identification.
Specifically, after receiving a data synchronization request from a consumption server, a queue server feeds back data to be synchronized in a data cache queue corresponding to a queue identifier to the consumption server according to the queue identifier carried in the data synchronization request.
In one embodiment, the consumption server comprises a plurality of consumption modules, and each consumption module can read the data to be synchronized in the corresponding data cache queue from the queue server in parallel. The consumption server also reads the data to be synchronized from the data cache queue of the queue server by calling the API interface provided by the queue server.
In one embodiment, after the consumption server successfully synchronizes the data to be synchronized, the synchronized data may be stored to a local storage medium. The consumption server can receive the data operation instruction from the terminal, and searches corresponding data according to the received data operation instruction and responds to corresponding operation.
For example, when the data to be synchronized includes order related information and the consumption server includes an order query server, the terminal may operate a client corresponding to the consumption server, the user may trigger a query instruction for querying a certain order through the client, the consumption server responds to the query instruction, queries the corresponding order related information and feeds the corresponding order related information back to the terminal, and the terminal displays the queried order related information according to a preset rule.
Or, when the data to be synchronized includes promotion information and the consumption server includes a server providing message group sending, the consumption server may receive an information sending instruction from the terminal, and send the specified promotion information (i.e., the promotion information read by the consumption server from the data cache queue) to the corresponding user account in response to the information sending instruction.
In one embodiment, the data synchronization method further includes a step of updating the state, where the step specifically includes: after the consumption server successfully receives the data to be synchronized fed back by the queue server, feeding back second feedback information indicating that data synchronization is completed to the queue server; and the queue server updates the data state of the fed-back data to be synchronized into a synchronized state according to the second feedback information.
Specifically, after the consumption server successfully synchronizes the data to be synchronized in the data cache queue, the consumption server feeds back second feedback information indicating that data synchronization is completed to the queue server. After receiving the second feedback information, the queue server may update the data state of the data that has been synchronized to the synchronized state, and the subsequent consumption server does not repeat reading when reading.
In one embodiment, the business server comprises an order approval server; the data to be synchronized comprises order related information; the consumption server comprises an order query server.
Specifically, in a specific application scenario, the business server may specifically be an order approval server, and the consumption server may specifically be an order query server providing an order query service. The data to be synchronized may specifically be order related information. When the approval progress of the order is updated, the order approval server can push corresponding order related information to the queue server, the queue server determines a queue identifier corresponding to the order related information, and the order related information is cached in a data cache queue corresponding to the queue identifier. The query server can read order related information from the corresponding data cache queue according to the queue identification, and the order related information is used for providing a query function of the client application.
According to the data synchronization method, the business server pushes the data to be synchronized to the queue server, and the queue server receives the data to be synchronized and then determines the queue identification corresponding to the data to be synchronized. And the queue server caches the data to be synchronized into a data cache queue corresponding to the queue identification. The consumption server sends a data synchronization request carrying a queue identification to the queue server, and the queue server responds to the data synchronization request and feeds back data to be synchronized in a data cache queue corresponding to the queue identification. Therefore, when data synchronization is needed between the service server and the consumption server, the data to be synchronized can be correspondingly cached through the queue server. And when needed, the consumption server can acquire the data to be synchronized from the queue server according to the queue identification. Therefore, when a large amount of data needs to be synchronized, the processing pressure of the service server and the consumption server can be greatly relieved, and the flexibility of data synchronization is improved.
In an embodiment, step S202, that is, the step of the service server pushing the data to be synchronized to the queue server specifically includes: a service server acquires data to be synchronized; the service server determines a source party identifier corresponding to the data to be synchronized; the service server determines the priority level corresponding to the source party identifier; and the service server sequentially pushes the data to be synchronized to the queue server according to the sequence of the corresponding priority level.
The source party identifier is used for uniquely identifying a source party of the data to be synchronized, and specifically may be at least one of letters, numbers, Chinese characters or character strings. The priority level is a level of priority such as high priority, medium priority, low priority, and the like.
Specifically, the service server includes a plurality of data acquisition modules, and each data acquisition module has a unique identifier, which may be referred to as a source identifier in this embodiment. The service server can obtain the data to be synchronized through a plurality of data obtaining modules, wherein each obtaining module can respectively obtain different types of data. For example, the acquisition module a may acquire order related information, the acquisition module B may acquire service promotion information, and the acquisition module C may acquire prompt and early warning information.
In one embodiment, a client corresponding to the service server runs on the terminal, and the user can input corresponding data in the client. Or, the user may open a web interface provided by the service server through the terminal, and the user may input corresponding data in the web interface. Furthermore, the terminal can generate the data to be synchronized according to the data input by the user. The terminal can send the generated data to be synchronized to a preset acquisition module of the service server.
In one embodiment, the service server may provide an API interface, the terminal may communicate with the service server through the API interface provided by the service server, and the staff may transmit the data to be synchronized to the preset obtaining module of the service server through the API interface.
Further, after the service server acquires the data to be synchronized, it may determine which acquisition module the data to be synchronized is specifically acquired by, and further determine the corresponding source identifier. In an embodiment, the service server may preset different priority levels corresponding to different obtaining modules, so as to set priorities corresponding to different types of information.
In one embodiment, after determining the priority level corresponding to the identifier of the source, the service server sequentially pushes the data to be synchronized to the queue server according to the order of the priority levels. For example, if the priority level corresponding to the a obtaining module is a high priority, the data to be synchronized obtained by the a obtaining module is preferentially pushed to the queue server.
In an embodiment, when a large amount of data to be pushed to be synchronized exists in the service server, the service server may perform corresponding pushing according to a sequence of times of generation of the data to be synchronized. And when the time for generating the data to be synchronized is the same, for the data to be synchronized generated at the same time, the service server sequentially pushes the data to be synchronized to the queue server according to the sequence of the priority level of the source party identifier corresponding to each data to be synchronized.
In the above embodiment, the service server sequentially pushes the data to be synchronized to the queue server according to the order of the priority levels corresponding to the source identifiers of the data to be synchronized, so that when a large amount of data to be synchronized exists, important data to be synchronized can be preferentially pushed, limited resources occupied by unimportant data to be synchronized are avoided, and flexible pushing of the data to be synchronized can be realized.
In one embodiment, the data synchronization method further includes a step of repeatedly pushing data to be synchronized, where the step specifically includes: after a business server pushes data to be synchronized to a queue server, the business server detects first feedback information fed back by the queue server; when first feedback information fed back by the queue server is not detected in a preset time period, the service server determines a priority level corresponding to a source party identifier corresponding to the data to be synchronized; the service server determines a repeated pushing mode corresponding to the priority level; and the service server repeatedly pushes the data to be synchronized according to a corresponding repeated pushing mode.
Specifically, after the service server pushes the data to be synchronized to the queue server, and after the queue server successfully receives the data to be synchronized, the queue server feeds back first feedback information indicating successful reception to the service server. And when the service server does not receive the first feedback information fed back by the queue server within a preset time period, indicating that the queue server fails to receive the data. The failure of the queue server to receive the data to be synchronized may be due to a network failure, a failure of the traffic server to send the data, or a failure of the queue server.
Further, when the service server does not receive the first feedback information fed back by the queue server within a preset time period, the service server may determine a priority level corresponding to the source identifier corresponding to the data to be synchronized, and determine a repeat pushing manner corresponding to the priority level. In this embodiment, the service server may preset different priority levels corresponding to different repeated pushing manners.
For example, the service server may include a plurality of data acquisition modules, such as a data acquisition module a, a data acquisition module B, and a data acquisition module C. The data acquisition module A corresponds to a data push level with high priority; the data acquisition module B corresponds to the data push level of the medium priority; the data acquisition module C corresponds to a low-priority data push level.
When the service server does not receive the first feedback information fed back by the queue server within a preset time period, the service server executes a retransmission step in the following way: for the data to be synchronized from the data acquisition module C with low priority, the data is not pushed after the pushing fails; for the data to be synchronized from the data acquisition module B with medium priority, the data to be synchronized is pushed again after the pushing fails until the failure times reach the preset times (for example, three times); and for the data to be synchronized from the data acquisition module A with high priority, re-pushing the data after the pushing fails, and if the pushing failure times reach preset times (for example, three times), storing the data to be synchronized into a database of the service server for subsequent query.
In the above embodiment, after the service server pushes the data to be synchronized to the queue server, when the first feedback information fed back by the queue server is not detected within a preset time period, it may be determined that the current data pushing fails. The service server can repeatedly push the corresponding data according to the priority level corresponding to the source party identification of the data to be synchronized. Therefore, the data which is failed to be pushed is repeatedly pushed, and omission of the data to be synchronized in the synchronization process can be avoided. And according to the priority level corresponding to the source of the data to be synchronized, different repeated pushing modes are adopted to repeatedly push the data to be synchronized, so that the flexibility of data synchronization is greatly enhanced.
In one embodiment, step 208, namely the step of the consumption server sending the data synchronization request to the queue server specifically includes: the consumption server acquires a data synchronization instruction; the consumption server determines a target party identifier corresponding to the data synchronization instruction; the consumption server determines a corresponding queue identifier according to the target party identifier; and the consumption server generates a data synchronization request according to the queue identification and sends the data synchronization request to the queue server.
In one embodiment, the consumption server may receive data synchronization instructions from a terminal trigger. Or the consumption server can trigger the data synchronization instruction at regular time through the timing device and acquire the data synchronization instruction. The consumption server can also monitor the current load state of the consumption server in real time, and when the load state meets the preset load condition, a data synchronization instruction is triggered. The preset load condition may specifically be that the load amount is less than a preset threshold value.
In one embodiment, the consumption server may include a plurality of consumption modules, each having a unique identity, which may be referred to herein as a target party identity. After the consumption server obtains the data synchronization instruction, it can determine which consumption module triggers the data synchronization instruction, that is, determine the corresponding target party identifier.
In one embodiment, the consumption server may store an association table corresponding to the target party identifier and the queue identifier in advance. After determining the queue identifier corresponding to the target party identifier, the consumption server may generate a data synchronization request according to the queue identifier. For example, if the a' target corresponds to the a queue, the data synchronization request sent by the consumption server carries the queue id of the a queue.
In one embodiment, the consumption server may read the data to be synchronized in the corresponding data buffer queue from the queue server in parallel through each consumption module according to its own load state or timing, so as to complete the synchronization of the data.
In the above embodiment, the consumption server reads the to-be-synchronized data cached in the corresponding data cache queue from the queue server through the queue identifier corresponding to the target party identifier corresponding to the data synchronization instruction. Therefore, the queue identification is used for orderly storing, and then orderly reading is carried out, so that the efficiency of data synchronization can be greatly improved.
In one embodiment, the data synchronization method further includes a step of repeatedly receiving, where the step specifically includes: when the consumption server does not receive the data to be synchronized fed back by the queue server, the consumption server determines the priority level corresponding to the target party identifier corresponding to the data synchronization request; the consumption server determines a repeated receiving mode corresponding to the priority level; and the consumption server repeatedly receives the data to be synchronized according to the corresponding repeated receiving mode.
Specifically, when a network fails, a queue server fails or a consumption module of the consumption server fails, an abnormality may occur in the data to be synchronized, which is fed back by the consumption server receiving the queue server. When the consumption server does not receive the data to be synchronized fed back by the queue server, the consumption server can determine the priority level corresponding to the target party identifier corresponding to the data synchronization request and determine the corresponding repeated receiving mode. In this embodiment, the consumption server may preset different priority levels corresponding to different repeated receiving modes.
For example, the consumption server may include a plurality of consumption modules, such as consumption module a ', consumption module B ', and consumption module C '. Wherein, the consumption module A' corresponds to a data reading level with high priority; the consumption module B' corresponds to the data reading level of the middle priority; consumption module C' corresponds to a low priority data read level.
After a consumption module in the consumption server fails to read the data to be synchronized from the queue server, the consumption server executes the step of repeated receiving in the following way: for the consumption module C' with low priority to read the data to be synchronized, the data is not read after the reading fails; for the consumption module B' with the medium priority to read the data to be synchronized, the data to be synchronized can be read again after the reading fails until the failure times reach the preset times (for example, three times); and for the consumption module A' with high priority to read the data to be synchronized, the data to be synchronized is read again after the reading fails, and if the reading fails for a preset number of times (such as three times), the information such as the identifier or the queue identifier of the data to be synchronized, which needs to be read, is stored in the database of the consumption server for subsequent re-reading.
In the above embodiment, when the consumption server does not receive the data to be synchronized fed back by the queue server, it may be determined that the data reading fails. The consumption server can repeatedly read the corresponding data according to the corresponding priority level of the target party identification corresponding to the data synchronization request. Therefore, the data which fails to be read are repeatedly read, and omission of the data to be synchronized in the synchronization process can be avoided. And different repeated receiving modes are adopted to repeatedly read the data to be synchronized according to the priority level corresponding to the target party of the data to be synchronized, so that the flexibility of data synchronization is greatly enhanced.
Further, there may be a plurality of service servers, and correspondingly, there may be a plurality of consumption servers. For this case, the queue server may set a secondary queue identification for classification. For example, the associated business server and consumption server may correspond to a first level tag of the data cache queue; the particular data acquisition module and associated consumption module may then correspond to a second level tag of the data cache queue.
For example, the a service server is associated with the a 'consumption server, that is, the data to be synchronized of the a service server needs to be transmitted to the a' consumption server. All the data to be synchronized transmitted from the a service server to the a' consumption server are cached to the data cache queue cluster with the first-level label a. Further, when the data to be synchronized acquired by the data acquisition module a1 in the a service server is transmitted to the consumption module a1 'in the a' consumption server, the queue server buffers the data to be synchronized into the a1 data buffer queue in the a data buffer queue cluster.
In a specific embodiment, as shown in fig. 3, the data synchronization method specifically includes the following steps:
s302, the service server obtains the data to be synchronized.
S304, the service server determines the source party identification corresponding to the data to be synchronized.
S306, the service server determines the priority level corresponding to the source party identifier.
S308, the service server sequentially pushes the data to be synchronized to the queue server according to the sequence of the corresponding priority level.
S310, after the business server pushes the data to be synchronized to the queue server, the business server detects first feedback information fed back by the queue server.
S312, when the first feedback information fed back by the queue server is not detected within the preset time period, the service server determines the priority level corresponding to the source identifier corresponding to the data to be synchronized.
S314, the service server determines the repeated pushing mode corresponding to the priority level.
And S316, the service server repeatedly pushes the data to be synchronized according to the corresponding repeated pushing mode.
S318, the queue server determines the queue identification corresponding to the data to be synchronized.
S320, the queue server buffers the data to be synchronized into a data buffer queue corresponding to the queue identification.
S322, the consumption server acquires a data synchronization instruction.
S324, the consumption server determines the identification of the target party corresponding to the data synchronization instruction.
S326, the consumption server determines a corresponding queue identifier according to the target party identifier.
And S328, the consumption server generates a data synchronization request according to the queue identification and sends the data synchronization request to the queue server.
S330, the queue server responds to the data synchronization request and feeds back the data to be synchronized in the data buffer queue corresponding to the queue identification.
S332, when the consumption server does not receive the data to be synchronized fed back by the queue server, the consumption server determines the priority level corresponding to the target party identification corresponding to the data synchronization request.
The consuming server determines a repetitive reception pattern corresponding to the priority level S334.
And S336, the consumption server repeatedly receives the data to be synchronized according to the corresponding repeated receiving mode.
And S338, after the consumption server successfully receives the data to be synchronized fed back by the queue server, feeding back second feedback information indicating that data synchronization is completed to the queue server.
And S340, updating the data state of the fed back data to be synchronized into a synchronized state by the queue server according to the second feedback information.
According to the data synchronization method, the business server pushes the data to be synchronized to the queue server, and the queue server receives the data to be synchronized and then determines the queue identification corresponding to the data to be synchronized. And the queue server caches the data to be synchronized into a data cache queue corresponding to the queue identification. The consumption server sends a data synchronization request carrying a queue identification to the queue server, and the queue server responds to the data synchronization request and feeds back data to be synchronized in a data cache queue corresponding to the queue identification. Therefore, when data synchronization is needed between the service server and the consumption server, the data to be synchronized can be correspondingly cached through the queue server. And when needed, the consumption server can acquire the data to be synchronized from the queue server according to the queue identification. Therefore, when a large amount of data needs to be synchronized, the processing pressure of the service server and the consumption server can be greatly relieved, and the flexibility of data synchronization is improved.
It should be understood that although the various steps in the flow charts of fig. 2-3 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 2-3 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternating with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in FIG. 1, a data synchronization system 100 is provided, the system comprising a business server 101, a queue server 102, and a consumption server 103.
The service server 101 is configured to push data to be synchronized to the queue server.
The queue server 102 is configured to determine a queue identifier corresponding to data to be synchronized; and caching the data to be synchronized into a data caching queue corresponding to the queue identification.
The consumption server 103 is used for sending a data synchronization request to the queue server; the data synchronization request carries a queue identification.
The queue server 102 is further configured to feed back data to be synchronized in the data buffer queue corresponding to the queue identifier in response to the data synchronization request.
In an embodiment, the service server 101 is further configured to obtain data to be synchronized, determine a source identifier corresponding to the data to be synchronized, determine a priority level corresponding to the source identifier, and sequentially push the data to be synchronized to the queue server according to an order of the priority levels.
In one embodiment, the service server 101 is further configured to detect first feedback information fed back by the queue server 102 after pushing the data to be synchronized to the queue server 102; when first feedback information fed back by the queue server 102 is not detected within a preset time period, determining a priority level corresponding to a source party identifier corresponding to data to be synchronized; determining a repeated pushing mode corresponding to the priority level; and repeatedly pushing the data to be synchronized according to a corresponding repeated pushing mode.
In one embodiment, the consumption server 103 is further configured to obtain a data synchronization instruction, determine a target party identifier corresponding to the data synchronization instruction, determine a corresponding queue identifier according to the target party identifier, generate a data synchronization request according to the queue identifier, and send the data synchronization request to the queue server.
In one embodiment, the consumption server 103 is further configured to determine a priority level corresponding to the target party identifier corresponding to the data synchronization request when the data to be synchronized fed back by the queue server 102 is not received; determining a repeated receiving mode corresponding to the priority level; and repeatedly receiving the data to be synchronized according to a corresponding repeated receiving mode.
In one embodiment, the consumption server 103 is further configured to, after successfully receiving the data to be synchronized fed back by the queue server 102, feed back second feedback information indicating that data synchronization is completed to the queue server 102. The queue server 102 is further configured to update the data state of the fed back data to be synchronized to a synchronized state according to the second feedback information.
In one embodiment, the business server comprises an order approval server; the data to be synchronized comprises order related information; the consumption server comprises an order query server.
In the data synchronization system, the service server pushes the data to be synchronized to the queue server, and the queue server receives the data to be synchronized and then determines the queue identifier corresponding to the data to be synchronized. And the queue server caches the data to be synchronized into a data cache queue corresponding to the queue identification. The consumption server sends a data synchronization request carrying a queue identification to the queue server, and the queue server responds to the data synchronization request and feeds back data to be synchronized in a data cache queue corresponding to the queue identification. Therefore, when data synchronization is needed between the service server and the consumption server, the data to be synchronized can be correspondingly cached through the queue server. And when needed, the consumption server can acquire the data to be synchronized from the queue server according to the queue identification. Therefore, when a large amount of data needs to be synchronized, the processing pressure of the service server and the consumption server can be greatly relieved, and the flexibility of data synchronization is improved.
For specific limitations of the data synchronization system, reference may be made to the above limitations of the data synchronization method, which are not described herein again. The various modules in the data synchronization system described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided that may be used as a business server, a queue server, or a consumption server, the internal structure of which may be as shown in FIG. 4. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data to be synchronized. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a data synchronization method.
Those skilled in the art will appreciate that the architecture shown in fig. 4 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (14)
1. A method of data synchronization, comprising:
the service server pushes data to be synchronized to the queue server;
the queue server determines a queue identification corresponding to the data to be synchronized based on a source of the data to be synchronized;
the queue server caches the data to be synchronized into a data cache queue corresponding to the queue identification;
each consumption module in the consumption server respectively sends a data synchronization request to the queue server; the data synchronization request carries a queue identification; the target party identification corresponding to each consumption module and the queue identification carried in the data synchronization request sent by the corresponding consumption module have an incidence relation;
the queue server responds to the data synchronization request and feeds back data to be synchronized in a data cache queue corresponding to the queue identification;
and each consumption module in the consumption server reads and stores the data to be synchronized in the corresponding data cache queue in parallel from the queue server, searches corresponding data according to the received data operation instruction when receiving the data operation instruction from the terminal, and responds to the corresponding data operation instruction.
2. The method of claim 1, wherein the business server pushing the data to be synchronized to a queue server comprises:
the service server acquires data to be synchronized;
the service server determines a source party identifier corresponding to the data to be synchronized;
the service server determines the priority level corresponding to the source party identifier;
and the service server sequentially pushes the data to be synchronized to the queue server according to the sequence of the corresponding priority level.
3. The method of claim 2, further comprising:
after the business server pushes data to be synchronized to the queue server, the business server detects first feedback information fed back by the queue server;
when first feedback information fed back by the queue server is not detected in a preset time period, the service server determines a priority level corresponding to a source party identifier corresponding to the data to be synchronized;
the service server determines a repeated pushing mode corresponding to the priority level;
and the service server repeatedly pushes the data to be synchronized according to a corresponding repeated pushing mode.
4. The method of claim 1, wherein the sending of the data synchronization request to the queue server by each consuming module in the consuming server comprises:
the consumption server acquires a data synchronization instruction;
each consumption module in the consumption server respectively determines a target party identifier corresponding to the data synchronization instruction;
each consumption module in the consumption server determines a corresponding queue identifier according to the target party identifier;
and each consumption module in the consumption server generates a data synchronization request according to the queue identification and sends the data synchronization request to the queue server.
5. The method of claim 4, further comprising:
when the consumption server does not receive the data to be synchronized fed back by the queue server, the consumption server determines the priority level corresponding to the target party identifier corresponding to the data synchronization request;
the consumption server determining a duplicate reception manner corresponding to the priority level;
and the consumption server repeatedly receives the data to be synchronized according to a corresponding repeated receiving mode.
6. The method according to any one of claims 1 to 5, further comprising:
after the consumption server successfully receives the data to be synchronized fed back by the queue server, feeding back second feedback information representing that data synchronization is completed to the queue server;
and the queue server updates the data state of the fed back data to be synchronized into a synchronized state according to the second feedback information.
7. The method of claim 6, wherein the business server comprises an order approval server; the data to be synchronized comprises order related information; the consumption server comprises an order query server.
8. A data synchronization system, characterized in that the system comprises a service server, a queue server and a consumption server;
the service server is used for pushing data to be synchronized to the queue server;
the queue server is used for determining a queue identifier corresponding to the data to be synchronized based on a source of the data to be synchronized; caching the data to be synchronized into a data caching queue corresponding to the queue identification;
each consumption module in the consumption server is respectively used for sending a data synchronization request to the queue server; the data synchronization request carries a queue identification; the target party identification corresponding to each consumption module and the queue identification carried in the data synchronization request sent by the corresponding consumption module have an incidence relation;
the queue server is used for responding to the data synchronization request and feeding back data to be synchronized in the data cache queue corresponding to the queue identification;
and each consumption module in the consumption server is used for reading and storing the data to be synchronized in the corresponding data cache queue from the queue server in parallel, searching corresponding order related information according to the received data operation instruction when receiving the data operation instruction from the terminal, and responding to the corresponding data operation instruction.
9. The system according to claim 8, wherein the service server is further configured to obtain data to be synchronized, determine a source identifier corresponding to the data to be synchronized, determine a priority level corresponding to the source identifier, and sequentially push the data to be synchronized to the queue server according to an order of the priority levels.
10. The system of claim 8, wherein the consumption server is further configured to obtain a data synchronization command, determine a destination identifier corresponding to the data synchronization command, determine a corresponding queue identifier according to the destination identifier, generate a data synchronization request according to the queue identifier, and send the data synchronization request to the queue server.
11. The system according to claim 8, wherein the service server is further configured to detect first feedback information fed back by the queue server after pushing data to be synchronized to the queue server;
when the first feedback information fed back by the queue server is not detected in a preset time period, the service server is further configured to determine a priority level corresponding to a source identifier corresponding to the data to be synchronized;
the service server is also used for determining a repeated pushing mode corresponding to the priority level;
and the service server is also used for repeatedly pushing the data to be synchronized according to a corresponding repeated pushing mode.
12. The system according to claim 8, wherein when the consumption server does not receive the data to be synchronized fed back by the queue server, the consumption server is further configured to determine a priority level corresponding to the target party identifier corresponding to the data synchronization request;
the consumption server is further used for determining a repeated receiving mode corresponding to the priority level;
the consumption server is further used for repeatedly receiving the data to be synchronized according to a corresponding repeated receiving mode.
13. The system according to claim 8, wherein after the consumption server successfully receives the data to be synchronized fed back by the queue server, the consumption server is further configured to feed back second feedback information indicating that data synchronization is completed to the queue server;
and the queue server is further configured to update the data state of the fed back data to be synchronized to a synchronized state according to the second feedback information.
14. The system of claim 8, wherein the business server comprises an order approval server; the data to be synchronized comprises order related information; the consumption server comprises an order query server.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910007430.9A CN109788053B (en) | 2019-01-04 | 2019-01-04 | Data synchronization method and system |
| PCT/CN2019/122302 WO2020140661A1 (en) | 2019-01-04 | 2019-12-02 | Data synchronization method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910007430.9A CN109788053B (en) | 2019-01-04 | 2019-01-04 | Data synchronization method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109788053A CN109788053A (en) | 2019-05-21 |
| CN109788053B true CN109788053B (en) | 2022-04-29 |
Family
ID=66500044
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910007430.9A Active CN109788053B (en) | 2019-01-04 | 2019-01-04 | Data synchronization method and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN109788053B (en) |
| WO (1) | WO2020140661A1 (en) |
Families Citing this family (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109788053B (en) * | 2019-01-04 | 2022-04-29 | 深圳壹账通智能科技有限公司 | Data synchronization method and system |
| CN110795505A (en) * | 2019-10-23 | 2020-02-14 | 北京仿真中心 | Cross-domain synchronous distribution system and method for user data |
| CN110781373B (en) * | 2019-10-29 | 2022-09-06 | 北京字节跳动网络技术有限公司 | List updating method and device, readable medium and electronic equipment |
| CN112839067B (en) * | 2019-11-22 | 2022-07-22 | 腾讯科技（深圳）有限公司 | Data synchronization method and device |
| CN112989887B (en) * | 2019-12-16 | 2024-06-11 | 深圳云天励飞技术有限公司 | File merging method and device and electronic equipment |
| CN111371900B (en) * | 2020-03-13 | 2022-07-12 | 北京奇艺世纪科技有限公司 | Method and system for monitoring health state of synchronous link |
| CN111581244B (en) * | 2020-05-14 | 2023-04-25 | 厦门熵基科技有限公司 | Method, system and equipment for orderly synchronizing service transaction data of heterogeneous system |
| CN111651522B (en) * | 2020-05-27 | 2023-05-19 | 泰康保险集团股份有限公司 | Data synchronization method and device |
| CN112035464B (en) * | 2020-07-22 | 2024-03-15 | 武汉达梦数据库股份有限公司 | Data synchronization filtering method and synchronization device based on log analysis |
| CN111897828B (en) * | 2020-07-31 | 2024-07-19 | 广州视源电子科技股份有限公司 | Method, device, equipment and storage medium for realizing data batch processing |
| CN111813868B (en) * | 2020-08-13 | 2023-11-10 | 中国工商银行股份有限公司 | Data synchronization method and device |
| CN112015553A (en) * | 2020-08-27 | 2020-12-01 | 深圳壹账通智能科技有限公司 | Data processing method, device, equipment and medium based on machine learning model |
| CN112052104A (en) * | 2020-09-01 | 2020-12-08 | 掌阅科技股份有限公司 | Message queue management method based on multi-computer-room realization and electronic equipment |
| CN112068972A (en) * | 2020-09-01 | 2020-12-11 | 掌阅科技股份有限公司 | Message queue consumption method based on multi-computer room realization and electronic equipment |
| CN112181680A (en) * | 2020-09-15 | 2021-01-05 | 的卢技术有限公司 | Kafka-based priority queue implementation method |
| CN112506890B (en) * | 2020-09-21 | 2024-08-30 | 北京思特奇信息技术股份有限公司 | Method and device for transferring user fees in batches |
| CN112187916B (en) * | 2020-09-27 | 2023-12-05 | 中国银联股份有限公司 | Cross-system data synchronization method and device |
| CN112818054B (en) * | 2020-10-15 | 2022-05-06 | 广州南天电脑系统有限公司 | Data synchronization method and device, computer equipment and storage medium |
| CN113760980B (en) * | 2020-11-30 | 2024-08-20 | 北京京东乾石科技有限公司 | Data caching method, data providing end and data using end |
| CN112612799B (en) * | 2020-12-08 | 2022-10-18 | 福建天泉教育科技有限公司 | Data synchronization method and terminal |
| CN112416633A (en) * | 2020-12-18 | 2021-02-26 | 世纪恒通科技股份有限公司 | Method and system for pushing data to external system and realizing data synchronization |
| CN112596865B (en) * | 2020-12-22 | 2024-08-16 | 航天信息股份有限公司企业服务分公司 | System for pushing message to be handled based on workflow transaction |
| CN112579704B (en) * | 2020-12-24 | 2024-04-09 | 深圳市科力锐科技有限公司 | Data reverse synchronization method, device, system, mirror server and storage medium |
| CN112650814B (en) * | 2020-12-30 | 2023-09-26 | 平安壹钱包电子商务有限公司 | Data storage method, device, equipment and storage medium based on message middleware |
| CN113064766A (en) * | 2021-05-07 | 2021-07-02 | 数字广东网络建设有限公司 | Data backup method, device, equipment and storage medium |
| CN113448725A (en) * | 2021-05-27 | 2021-09-28 | 深圳震有科技股份有限公司 | Data pushing method, device, terminal and storage medium |
| CN113242313B (en) * | 2021-05-28 | 2023-01-20 | 北京达佳互联信息技术有限公司 | Data synchronization method, system, device, server and storage medium |
| CN113568570B (en) * | 2021-06-22 | 2024-04-12 | 阿里巴巴创新公司 | Data processing method and device |
| CN113434525B (en) * | 2021-06-24 | 2023-06-09 | 青岛海尔科技有限公司 | Cache data updating method and device, storage medium and electronic device |
| CN114051036A (en) * | 2021-09-23 | 2022-02-15 | 通号城市轨道交通技术有限公司 | Data synchronization method, device and equipment for rail transit signal system and storage medium |
| CN114185896B (en) * | 2021-12-14 | 2024-07-09 | 中国平安财产保险股份有限公司 | Data processing method, device, electronic equipment and storage medium |
| CN114745571B (en) * | 2022-04-15 | 2024-01-23 | 网易（杭州）网络有限公司 | Live state information synchronization method and device, electronic equipment and readable storage medium |
| CN114745432A (en) * | 2022-04-18 | 2022-07-12 | 北京京东拓先科技有限公司 | Data transmission method and device |
| CN115080311B (en) * | 2022-07-01 | 2023-01-24 | 深圳美克拉网络技术有限公司 | Informatization remote control method and device for big data |
| CN116155831B (en) * | 2022-12-28 | 2024-05-03 | 河南辉煌科技股份有限公司 | Data transmission method and system for railway production management system |
| CN116340432B (en) * | 2023-05-29 | 2023-08-04 | 武汉华瑞测智能技术有限公司 | Database synchronization method, equipment and medium based on power data |
| CN116521622B (en) * | 2023-06-30 | 2023-09-22 | 中邮消费金融有限公司 | Method and system for automatically managing data based on data snapshot |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105610886A (en) * | 2014-11-25 | 2016-05-25 | 腾讯科技（深圳）有限公司 | Information pushing control method and information pushing platform |
| CN108023908A (en) * | 2016-10-31 | 2018-05-11 | 腾讯科技（深圳）有限公司 | Data-updating method, apparatus and system |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7107314B2 (en) * | 2003-01-21 | 2006-09-12 | Red Hat, Inc. | Mail system synchronization using multiple message identifiers |
| CN106204000A (en) * | 2016-07-05 | 2016-12-07 | 康存乐付保数据科技（上海）有限公司 | A kind of service consumption method for processing payment information and system |
| US10540369B2 (en) * | 2016-12-19 | 2020-01-21 | Salesforce.Com, Inc. | Org sync suspend and resume data sync |
| CN107197017A (en) * | 2017-05-23 | 2017-09-22 | 努比亚技术有限公司 | A kind of consuming method, terminal and computer-readable recording medium based on consumption queue |
| CN108038767B (en) * | 2017-12-26 | 2022-02-11 | 广州供电局有限公司 | E-commerce order asynchronous distribution system and method based on message queue |
| CN109788053B (en) * | 2019-01-04 | 2022-04-29 | 深圳壹账通智能科技有限公司 | Data synchronization method and system |
-
2019
- 2019-01-04 CN CN201910007430.9A patent/CN109788053B/en active Active
- 2019-12-02 WO PCT/CN2019/122302 patent/WO2020140661A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105610886A (en) * | 2014-11-25 | 2016-05-25 | 腾讯科技（深圳）有限公司 | Information pushing control method and information pushing platform |
| CN108023908A (en) * | 2016-10-31 | 2018-05-11 | 腾讯科技（深圳）有限公司 | Data-updating method, apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109788053A (en) | 2019-05-21 |
| WO2020140661A1 (en) | 2020-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109788053B (en) | Data synchronization method and system | |
| CN108449405B (en) | Event reminding method and device, computer equipment and storage medium | |
| CN110719318B (en) | Message processing method and system | |
| CN109743390B (en) | Task scheduling method and device, computer equipment and storage medium | |
| CN108829727B (en) | Data storage method and device, computer equipment and storage medium | |
| CN109766534B (en) | Report generation method and device, computer equipment and readable storage medium | |
| EP2998863B1 (en) | Converting a serial transaction schedule to a parallel transaction schedule | |
| WO2020140663A1 (en) | Microservice grayscale publishing method, device, computer device and storage medium | |
| CN110908778B (en) | Task deployment method, system and storage medium | |
| CN109492019B (en) | Service request response method, device, computer equipment and storage medium | |
| CN109766253B (en) | Performance data sending method and device, computer equipment and storage medium | |
| CN111159233B (en) | Distributed caching method, system, computer equipment and storage medium | |
| WO2020233091A1 (en) | Method and apparatus for service data rollback, computer device and storage medium | |
| CN110781214A (en) | Database reading and writing method and device, computer equipment and storage medium | |
| CN114092252B (en) | Block chain transaction execution method, device, equipment and readable storage medium | |
| CN108376154B (en) | System base table synchronization method and device, computer equipment and storage medium | |
| CN111338834B (en) | Data storage method and device | |
| CN112491659A (en) | Flow playback test method and device, computer equipment and storage medium | |
| CN113111078B (en) | Resource data processing method and device, computer equipment and storage medium | |
| CN108897772B (en) | Data source supplementing method and device, computer equipment and storage medium | |
| CN108389124B (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN114760357A (en) | Request processing method and device, computer equipment and storage medium | |
| CN113010306A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN114238264A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN109325057B (en) | Middleware management method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |