CN117579229A - Distributed transaction processing method and system - Google Patents
Distributed transaction processing method and system Download PDFInfo
- Publication number
- CN117579229A CN117579229A CN202211681505.XA CN202211681505A CN117579229A CN 117579229 A CN117579229 A CN 117579229A CN 202211681505 A CN202211681505 A CN 202211681505A CN 117579229 A CN117579229 A CN 117579229A
- Authority
- CN
- China
- Prior art keywords
- message
- data
- service
- message data
- processing
- 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
- 238000003672 processing method Methods 0.000 title claims abstract description 17
- 238000012545 processing Methods 0.000 claims abstract description 119
- 238000000034 method Methods 0.000 claims abstract description 21
- 238000012790 confirmation Methods 0.000 claims abstract description 19
- 238000012544 monitoring process Methods 0.000 claims description 12
- 230000005540 biological transmission Effects 0.000 description 5
- 238000005192 partition Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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/547—Messaging middleware
-
- 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
Abstract
The invention discloses a distributed transaction processing method and a system, which relate to the technical field of computers, wherein the method comprises the following steps: the generating end service system generates service data and processes the service data and corresponding message data; storing the business data and the message data into a database; setting the state of the message data to be transmitted; after the business data processing is completed, the message data is sent to the message middleware; after receiving the message data, the message middleware actively replies and confirms the receipt; the generating end service system sets the state of the message data to be sent; after subscribing the message data of the message middleware, the consumption end service system judges whether the message data is consumed or not, if so, the message is abandoned; otherwise, carrying out service processing according to the message data, and sending confirmation completion to the message middleware; the message middleware deletes the message data, and the technical scheme provided by the invention does not require that the data of all services at the same time are completely consistent, but only the final data are consistent.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a distributed transaction processing method and system.
Background
Distributed transactions are those in which the participants of the transaction, the servers supporting the transaction, the resource servers, and the transaction manager are located on different nodes of different distributed systems, respectively. According to the distributed system CAP theory, consistency (C), availability (a), partition fault tolerance (Partition Tolerance, P) are not all available. In the prior art, most of distributed transaction service systems only can ensure the data consistency of the service systems and cannot ensure the final consistency of the data of the associated systems; when a plurality of systems are involved, once an abnormality occurs in a certain system, abnormal data cannot be found or processed in time, so that the data are finally inconsistent; and the technical problems that when the concurrency is too large, the time-out is easy, related services cannot be processed and the like exist.
Disclosure of Invention
The distributed transaction processing method and system provided by the invention solve the technical problems.
The invention provides a distributed transaction processing method, which comprises the following steps:
the method comprises the steps that A1, a generating end service system generates service data, and the service data and message data corresponding to the service data are processed in one transaction; storing the business data and the message data corresponding to the business data into a database; setting the state of message data corresponding to the service data as to-be-sent;
a2, after the business data processing is completed, sending the message data corresponding to the business data to a message middleware;
step A3: after receiving the message data, the message middleware replies acknowledgement to the generating end service system;
step A4: the generating end service system sets the state of message data corresponding to the service data as sent;
after the consumer side service system subscribes to the message data of the message middleware, executing step S1;
step S1, judging whether the message data is consumed or not, if so, discarding the message data; otherwise, carrying out service processing according to the message data, and executing step S2;
step S2, sending confirmation completion to the message middleware;
and step S3, deleting the message data corresponding to the service data by the message middleware.
Optionally, the method further comprises:
the message service compensation monitoring system inquires the state of message data corresponding to the service data in a database; and if the state of the message data corresponding to the service data is the state to be sent, sending the message data corresponding to the service data to the message middleware.
Optionally, the step S1 specifically includes: searching message ID of message data in REDIS and database; if so, discarding the message data; otherwise, carrying out service processing according to the message data, and executing step S2;
the service processing according to the message data further comprises the following steps: the message ID of the message data is stored in the REDIS and database.
Optionally, the step s1 specifically includes: the consumer terminal service system inquires the message processing state of the message data according to the own rule, and if the message processing state is processed, the message data is abandoned; if not, carrying out service processing according to the message data, and executing step S2;
the service processing according to the message data further comprises the following steps: the message processing state of the message data is set to processed.
Optionally, in the step s1, the performing service processing according to the message data specifically includes: the consumer terminal service system performs service processing according to the message data, and if the processing is successful, the step S2 is executed; if the processing fails, continuing to process the service according to the message data, and after the failure exceeds the preset times, sending the message data to a dead message queue to wait for manual processing.
The invention also provides a distributed transaction processing system, which comprises: generating an end service system, a message middleware and a consumption end service system;
the generating end service system comprises: the device comprises a generating module, a first processing module, a first storage module, a setting module, a first sending module and a first receiving module;
the message middleware includes: the device comprises a second receiving module, a second sending module, a third receiving module and a deleting module;
the consumer-side business system comprises: the device comprises a judging module, a second processing module and a third sending module;
the generating module is used for generating service data;
the first processing module is used for processing service data and message data corresponding to the service data in one transaction;
the first storage module is used for storing the business data and the message data corresponding to the business data into a database;
the first sending module is used for sending the message data corresponding to the service data to the message middleware;
the first receiving module is used for receiving the confirmation received message data from the message middleware;
the setting module is used for setting the state of the message data corresponding to the service data to be transmitted after the message data are stored in the database; the first receiving module is further used for setting the state of the message data corresponding to the service data to be sent after receiving the confirmation received message data from the message middleware;
the second receiving module is used for receiving message data from the generating end service system;
the second sending module is used for sending the message data confirmed to be received to the consumer-side service system;
the third receiving module is configured to receive the confirmation completion from the consumer-side service system;
the deleting module is used for deleting the message data corresponding to the service data after the third receiving module receives the confirmation from the consumer-side service system;
the judging module is used for subscribing the message data of the message middleware by the consumer service system. Judging whether the message data is consumed or not, if so, discarding the message data;
the second processing module is used for carrying out service processing according to the message data after the judging module judges that the message data is not the same;
and the third sending module is used for sending confirmation completion to the message middleware after the second processing module finishes processing.
Optionally, the method further comprises: a message service compensation monitoring system;
the message service compensation monitoring system is used for inquiring the state of message data corresponding to the service data in the database; and if the state of the message data corresponding to the service data is the state to be sent, sending the message data corresponding to the service data to the message middleware.
Optionally, the judging module is specifically configured to search the REDIS and the database for the message ID of the message data; if so, discarding the message data;
the consumer-side business system also comprises a second storage module;
the second saving module is configured to store the message ID of the message data in the REDIS and the database after the second processing module performs service processing according to the message data.
Optionally, the judging module is specifically configured to query a message processing state of the message data according to a rule of the consumer-side service system, and if the message processing state is processed, discard the message data;
the consumer-side business system also comprises a third storage module;
the third saving module is configured to set a message processing state of the message data to processed after the second processing module performs service processing according to the message data.
Optionally, the second processing module is specifically configured to perform service processing according to the message data; if the processing fails, continuing to process the service according to the message data, and after the failure exceeds the preset times, sending the message data to a dead message queue to wait for manual processing.
The invention has the beneficial effects that: the invention provides a distributed transaction processing method and a distributed transaction processing system, which can be used for completely consistent data of all services at the same time according to the characteristics of the data and service scenes. Namely, the AP model is realized, and the data only needs to be consistent finally.
Drawings
Fig. 1 is an operation flow chart of a generating end service system in a distributed transaction processing method according to an embodiment of the present invention;
fig. 2 is a flowchart of operations performed when a plurality of consumer service systems subscribe to message data of a message middleware according to an embodiment of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made more apparent and fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments of the invention are shown. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Examples
The present invention provides a distributed transaction processing method, as shown in fig. 1 and fig. 2, including:
the method comprises the steps that A1, a generating end service system generates service data, and the service data and message data corresponding to the service data are processed in one transaction; storing the business data and the message data corresponding to the business data into a database; setting the state of message data corresponding to the service data as to-be-sent;
a2, after the business data processing is completed, sending the message data corresponding to the business data to a message middleware;
step A3: after receiving the message data, the message middleware replies acknowledgement to the generating end service system;
step A4: the generating-side service system sets the state of message data corresponding to the service data to be transmitted.
The distributed transaction processing method provided in this embodiment further includes:
the message service compensation monitoring system inquires the state of message data corresponding to the service data in a database; and if the state of the message data corresponding to the service data is the state to be sent, sending the message data corresponding to the service data to the message middleware.
After the consumer side service system subscribes to the message data of the message middleware, executing step S1;
step S1, a consumption end service system judges whether message data are consumed or not, if so, the message data are abandoned; otherwise, carrying out service processing according to the message data, and executing step S2;
carrying out service processing according to the message data, and executing step S2 if the processing is successful; if the processing fails, continuing to process the service according to the message data, and after the failure exceeds the preset times, sending the message data to a dead message queue to wait for manual processing.
Step S2, sending confirmation completion to the message middleware;
and step S3, deleting the message data corresponding to the service data by the message middleware.
The step S1 specifically comprises the following steps: searching message ID of message data in REDIS and database; if so, discarding the message data; otherwise, carrying out service processing according to the message data, and executing step S2;
the service processing according to the message data further comprises the following steps: the message ID of the message data is stored in the REDIS and database.
Or the step S1 specifically comprises: the consumer terminal service system inquires the message processing state of the message data according to the own rule, and if the message processing state is processed, the message data is abandoned; if not, carrying out service processing according to the message data, and executing step S2;
the service processing according to the message data further comprises the following steps: the message processing state of the message data is set to processed.
More specifically, the distributed transaction processing method provided in this embodiment specifically includes: the generating end service system generates service data, namely a producer of the message, and the service data needs to be consumed by the consuming end service system;
the generating end service system issues message data corresponding to the service data to a message queue; the consumption end service system subscribes to the message data in the consumption message queue and processes the service;
in this embodiment, different customer service systems may subscribe to the message data in the message queue corresponding to themselves.
And finally, the generating end service system and the consuming end service system achieve service data consistency.
If the consumption end service system still can not process the message data after reaching the maximum retry times in the process of processing the message, the message data is sent to a dead message queue to wait for manual processing.
The distributed transaction processing method provided by the embodiment mainly solves the following two problems by adopting a data final consistency scheme based on a message to realize the data final consistency scheme.
1. Reliable messaging services design business data synchronization between different services.
The reliable message service architecture comprises the following specific processes:
since the message middleware cannot realize transaction processing with the business data, reliable message service needs to be ensured.
Step 1: the generating end service system firstly processes service data and information to be transmitted in a transaction, and stores the service data and the information to be transmitted in a database, wherein the transmission state of the information data is to be transmitted;
step 2: when the business data and the message data are processed in one transaction, the generating end business system can call the message sending module, and when the message data are sent, the sending state of the message data can be modified to be sent after the message middleware replies with an ACK;
step 3: when the transmission of message data or the change of the transmission state of message data fails, a message service compensation monitoring process follows.
Step 4: when the message service compensation monitoring finds that the message data is in a state to be sent, a message sending function is started to send the message data. If the maximum retry number of the message data is not successful, the message data is sent to a dead message queue to wait for manual processing;
the problem of repeated message transmission may exist in the message transmission of the generating end service system or the message monitoring and transmitting of the message service compensation. The message repetition problem is solved by a message consumer service system, namely the message idempotency problem is solved.
2. Consumer service system solves message idempotent problem
The message middleware is used for ensuring that the message is not lost and must be arrived, allowing the repeated message to be sent, and ensuring that the repeated message is consistent with the effect of one execution and has no relation with time when being consumed. The scheme is as follows:
the choice of scheme is determined by the own business requirements of the consumer business system:
scheme one:
1) When the consumption end service system needs to consume the message data, firstly, inquiring whether the message is consumed in REDIS by the message ID value, if not, judging whether the message is consumed in the inquiry database, ensuring that the message is not consumed, if not, normally processing the message data, and updating the database. If the REDIS or the database has the message ID, the processing of the message is abandoned;
the generating end service system must have a unique ID value for each message data sent to the message queue when generating the data, and the repeated message ID values are the same.
2) When the consumption end service system consumes the message data, the service items are processed first, after the processing is completed, the program actively transmits the ACK to the message middleware, and after the message middleware receives the ACK, the consumed message data is deleted;
message middleware services are not allowed to be set to automatic ACK responses, with the message middleware proactively sending ACK acknowledgements
3) After processing the message, the message ID is updated to the REDIS and database to quickly verify whether the message has been consumed.
Scheme II:
1) When the consumer terminal service system needs to consume the message data, the consumer terminal service system inquires the message processing state of the service information according to the own rule, if the message data is processed, the message data is ignored, if the message data is unprocessed, the message is processed, and the message processing state is modified to be processed;
2) If the processing fails in the processing process, retrying is carried out, if the maximum retry number is reached, the retry number is sent to a dead mail queue, and the manual processing is waited.
The embodiment also provides a distributed transaction processing system, which comprises: generating an end service system, a message middleware and a consumption end service system;
generating a terminal service system, comprising: the device comprises a generating module, a first processing module, a first storage module, a setting module, a first sending module and a first receiving module;
the message middleware comprises: the device comprises a second receiving module, a second sending module, a third receiving module and a deleting module;
the consumer-side business system comprises: the device comprises a judging module, a second processing module and a third sending module;
the generating module is used for generating service data;
the first processing module is used for processing service data and message data corresponding to the service data in one transaction;
the first storage module is used for storing the business data and the message data corresponding to the business data into a database;
the first sending module is used for sending the message data corresponding to the service data to the message middleware;
the first receiving module is used for receiving the confirmation received message data from the message middleware;
the setting module is used for setting the state of the message data corresponding to the service data to be transmitted after the message data are stored in the database; the first receiving module is further used for setting the state of the message data corresponding to the service data to be sent after receiving the confirmation received message data from the message middleware;
the second receiving module is used for receiving message data from the generating end service system;
the second sending module is used for sending the message data confirmed to be received to the consumer business system;
the third receiving module is used for receiving the confirmation completion from the consumer business system;
the deleting module is used for deleting the message data corresponding to the service data after the third receiving module receives the confirmation from the consumer-side service system;
and the judging module is used for subscribing the message data of the message middleware by the consumer-side service system. Judging whether the message data is consumed or not, if so, discarding the message data;
the second processing module is used for carrying out service processing according to the message data after the judging module judges that the message data is not the same;
and the third sending module is used for sending confirmation completion to the message middleware after the second processing module finishes processing.
Optionally, the method further comprises: a message service compensation monitoring system;
the message service compensation monitoring system is used for inquiring the state of message data corresponding to the service data in the database; and if the state of the message data corresponding to the service data is the state to be sent, sending the message data corresponding to the service data to the message middleware.
Optionally, the judging module is specifically configured to search the REDIS and the database for the message ID of the message data; if so, discarding the message data;
the consumer-side business system also comprises a second storage module;
and the second storage module is used for storing the message ID of the message data in REDIS and the database after the second processing module performs service processing according to the message data.
Optionally, the judging module is specifically configured to query the message processing state of the message data according to the rule of the consumer-side service system, and if the message processing state is processed, discard the message data;
the consumer-side business system also comprises a third storage module;
and the third storage module is used for setting the message processing state of the message data to be processed after the second processing module performs service processing according to the message data.
Optionally, the second processing module is specifically configured to perform service processing according to the message data; if the processing fails, continuing to process the service according to the message data, and after the failure exceeds the preset times, sending the message data to a dead message queue to wait for manual processing.
The distributed transaction processing method and system provided by the embodiment of the invention can be used for ensuring that the data of all services at the same time are not required to be completely consistent according to the characteristics of the data and the service scene, but only the final data are consistent. Namely, the AP model is realized, and the data only needs to be consistent finally.
The foregoing is merely illustrative embodiments of the present invention, and the present invention is not limited thereto, and any changes or substitutions that may be easily contemplated by those skilled in the art within the scope of the present invention should be included in the scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.
Claims (10)
1. A method of distributed transaction processing, comprising:
the method comprises the steps that A1, a generating end service system generates service data, and the service data and message data corresponding to the service data are processed in one transaction; storing the business data and the message data corresponding to the business data into a database; setting the state of message data corresponding to the service data as to-be-sent;
a2, after the business data processing is completed, sending the message data corresponding to the business data to a message middleware;
step A3: after receiving the message data, the message middleware replies acknowledgement to the generating end service system;
step A4: the generating end service system sets the state of message data corresponding to the service data as sent;
after the consumer side service system subscribes to the message data of the message middleware, executing step S1;
step S1, judging whether the message data is consumed or not, if so, discarding the message data; otherwise, carrying out service processing according to the message data, and executing step S2;
step S2, sending confirmation completion to the message middleware;
and step S3, deleting the message data corresponding to the service data by the message middleware.
2. The distributed transaction processing method of claim 1, further comprising:
the message service compensation monitoring system inquires the state of message data corresponding to the service data in a database; and if the state of the message data corresponding to the service data is the state to be sent, sending the message data corresponding to the service data to the message middleware.
3. The distributed transaction processing method according to claim 1, wherein the step S1 is specifically: searching message ID of message data in REDIS and database; if so, discarding the message data; otherwise, carrying out service processing according to the message data, and executing step S2;
the service processing according to the message data further comprises the following steps: the message ID of the message data is stored in the REDIS and database.
4. The distributed transaction processing method according to claim 1, wherein the step s1 is specifically: the consumer terminal service system inquires the message processing state of the message data according to the own rule, and if the message processing state is processed, the message data is abandoned; if not, carrying out service processing according to the message data, and executing step S2;
the service processing according to the message data further comprises the following steps: the message processing state of the message data is set to processed.
5. The distributed transaction processing method according to claim 1, wherein the performing service processing according to the message data in step s1 specifically includes: the consumer terminal service system performs service processing according to the message data, and if the processing is successful, the step S2 is executed; if the processing fails, continuing to process the service according to the message data, and after the failure exceeds the preset times, sending the message data to a dead message queue to wait for manual processing.
6. A distributed transaction processing system, comprising: generating an end service system, a message middleware and a consumption end service system;
the generating end service system comprises: the device comprises a generating module, a first processing module, a first storage module, a setting module, a first sending module and a first receiving module;
the message middleware includes: the device comprises a second receiving module, a second sending module, a third receiving module and a deleting module;
the consumer-side business system comprises: the device comprises a judging module, a second processing module and a third sending module;
the generating module is used for generating service data;
the first processing module is used for processing service data and message data corresponding to the service data in one transaction;
the first storage module is used for storing the business data and the message data corresponding to the business data into a database;
the first sending module is used for sending the message data corresponding to the service data to the message middleware;
the first receiving module is used for receiving the confirmation received message data from the message middleware;
the setting module is used for setting the state of the message data corresponding to the service data to be transmitted after the message data are stored in the database; the first receiving module is further used for setting the state of the message data corresponding to the service data to be sent after receiving the confirmation received message data from the message middleware;
the second receiving module is used for receiving message data from the generating end service system;
the second sending module is used for sending the message data confirmed to be received to the consumer-side service system;
the third receiving module is configured to receive the confirmation completion from the consumer-side service system;
the deleting module is used for deleting the message data corresponding to the service data after the third receiving module receives the confirmation from the consumer-side service system;
the judging module is used for subscribing the message data of the message middleware by the consumer service system. Judging whether the message data is consumed or not, if so, discarding the message data;
the second processing module is used for carrying out service processing according to the message data after the judging module judges that the message data is not the same;
and the third sending module is used for sending confirmation completion to the message middleware after the second processing module finishes processing.
7. The distributed transaction processing system of claim 6, further comprising: a message service compensation monitoring system;
the message service compensation monitoring system is used for inquiring the state of message data corresponding to the service data in the database; and if the state of the message data corresponding to the service data is the state to be sent, sending the message data corresponding to the service data to the message middleware.
8. The distributed transaction system according to claim 6, wherein the determination module is configured to find a message ID of the message data in the REDIS and database; if so, discarding the message data;
the consumer-side business system also comprises a second storage module;
the second saving module is configured to store the message ID of the message data in the REDIS and the database after the second processing module performs service processing according to the message data.
9. The distributed transaction system according to claim 6, wherein the judging module is specifically configured to query the message processing state of the message data according to the own rule by the consumer-side service system, and discard the message data if the message processing state is processed;
the consumer-side business system also comprises a third storage module;
the third saving module is configured to set a message processing state of the message data to processed after the second processing module performs service processing according to the message data.
10. The distributed transaction system of claim 6, wherein the second processing module is configured to perform business processing based on message data; if the processing fails, continuing to process the service according to the message data, and after the failure exceeds the preset times, sending the message data to a dead message queue to wait for manual processing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211681505.XA CN117579229A (en) | 2022-12-27 | 2022-12-27 | Distributed transaction processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211681505.XA CN117579229A (en) | 2022-12-27 | 2022-12-27 | Distributed transaction processing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117579229A true CN117579229A (en) | 2024-02-20 |
Family
ID=89888668
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211681505.XA Pending CN117579229A (en) | 2022-12-27 | 2022-12-27 | Distributed transaction processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117579229A (en) |
-
2022
- 2022-12-27 CN CN202211681505.XA patent/CN117579229A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8539107B2 (en) | Personal information management data synchronization | |
| JP5128111B2 (en) | System for preserving the sequence associated with a message, and method and computer program thereof | |
| US20110173495A1 (en) | Method and System for Reliable Intersystem Message Notification | |
| CN106844014B (en) | Method and device for realizing suspension prevention of distributed transactions | |
| US20070162560A1 (en) | System and method for asynchronous request response | |
| CN107277083B (en) | Data interaction processing method, device and system | |
| US8484281B2 (en) | System and method for callbacks based on web service addressing | |
| CN112788074A (en) | Data transmitting method, processing method, receiving method and equipment and storage medium | |
| EP2597818A1 (en) | Cluster management system and method | |
| CN113391979A (en) | Processing method, equipment and system for monitoring data display and storage medium | |
| CN109144748B (en) | Server, distributed server cluster and state driving method thereof | |
| CN111416823A (en) | Data transmission method and device | |
| CN111124717A (en) | Message delivery method, system and computer storage medium | |
| CN112632093A (en) | Work order processing method, device, system, storage medium and program product | |
| CN117579229A (en) | Distributed transaction processing method and system | |
| CN115964133A (en) | Message management method, device, equipment and storage medium | |
| CN114356596A (en) | Message processing method and device for distributed system | |
| CN109254853B (en) | Data sharing method, data sharing system and computer readable storage medium | |
| CN114598662A (en) | Message queue cluster federal management system and method | |
| CN112468386A (en) | Method and terminal for processing repeated messages | |
| CN112769824B (en) | Information transmission state updating method, terminal, device and storage medium | |
| CN112351072B (en) | Message pushing method and terminal | |
| CN112068997B (en) | Data backup method, device, equipment and storage medium | |
| CN112783612A (en) | Distributed transaction processing system of sharing platform | |
| CN112636950A (en) | Hot standby method, system, device and storage medium of aggregation server |
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 |