Transaction data processing system supporting middle station service
By designing a transaction data processing system that supports middle-end services, and using the transaction orchestration module to build external synchronous transactions, the problem of middle-end services requiring manual coding during rollback is solved, and the development efficiency and development difficulty of middle-end access is improved.
Patent Information
- Application Number
- CN202411675166.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-21
- Publication Date
- 2025-03-04
AI Technical Summary
In the prior art, when service data rollback occurs in middle-end services, they need manual coding to compensate atomic services, resulting in high development difficulty and workload.
A transaction data processing system supporting middle-end services is designed, including transaction orchestration module, transaction manager, local middle-end services and external middle-end services. The transaction orchestration module is used to build external synchronization transactions and send them to external middle-end services to realize transaction synchronization branches for external middle-end services, avoiding manual construction of atomic code.
It improves development efficiency, reduces the development difficulty and workload of middle-end access, and realizes the same transaction synchronization branch for external middle-end services.
Smart Images
Figure CN119557363A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of database processing technology, and in particular to a transaction data processing system supporting middle office services. Background Art
[0002] Transaction is a technology to ensure the integrity and consistency of system data. In computer terms, it refers to a program execution unit that accesses and may update various data items in the database. Transactions are usually caused by the execution of user programs written in high-level database manipulation languages or programming languages (such as SQL, C++ or Java), and are defined by statements (or function calls) such as begintransaction and endtransaction. A transaction consists of all operations performed between the beginning of the transaction (begintransaction) and the end of the transaction (endtransaction). With the development of technology, transaction processing has evolved from single-machine transactions that manage single-node data operations in the early days to distributed transactions that manage operations across multiple systems in a distributed system. Distributed transactions ensure data integrity and consistency through the two-phase commit (2PC) standardized protocol or innovative transaction mechanisms such as SAGA / TCC.
[0003] In the prior art, database systems are widely used in various fields, especially in administration, finance and other fields where big data applications are more extensive. Each unit will deploy different database systems locally according to its own needs and rely on the database system for data analysis and production business. At the same time, databases will also be synchronized between units to facilitate other data analysis business. For example, if the upper-level unit needs to analyze the production data of the subordinate unit, the production data in the database of the subordinate unit needs to be synchronized to the database of the upper-level unit before the analysis, and then the analysis work can be carried out.
[0004] In order to achieve better data analysis results, the existing technology usually builds corresponding middle-office services to support front-end business. Middle-office services refer to adding a middle-office service on the basis of the original front-end page-back-end database system. The middle-office service is responsible for the data scheduling and processing in the back-end database, so that the front-end pages of different functions and applications can directly call the data processed by the middle-office service, reducing the workload of front-end development.
[0005] Taking the middle office system built by a government agency as an example, the department needs to collect data from branch business systems in various places, and then use the department's middle office services to calculate and process various direct businesses. Finally, local branches can further design local front-end applications and information systems based on the department's middle office services, and call the data provided by the department's middle office services to perform daily business.
[0006] However, the inventors discovered that when a service data rollback occurs, the middle-office service uses a post-compensation mechanism to implement service rollback, requiring manual coding to compensate for atomic services to implement overall transaction rollback. The manual coding method brings a lot of development difficulty and workload to the middle-office access. Summary of the invention
[0007] In view of the above problems existing in the prior art, a transaction data processing system supporting middle office services is now provided.
[0008] The specific technical solutions are as follows:
[0009] A transaction data processing system supporting middle office services, including a transaction orchestration module, a transaction manager, a local middle office service and an external middle office service;
[0010] The input end of the transaction orchestration module is connected to the transaction manager;
[0011] The output end of the transaction orchestration module is connected to the external middle office service;
[0012] The transaction manager is connected to the local middle office service;
[0013] When the transaction manager submits a data synchronization transaction to the local middle office service, the transaction orchestration module constructs an external synchronization transaction corresponding to the data synchronization transaction to the external middle office service, and sends it to the external middle office service.
[0014] On the other hand, the transaction orchestration module includes an atomic service orchestration module and a branch transaction management module that are interconnected;
[0015] The atomic service management module includes an atomic service calling module;
[0016] The atomic service calling module constructs an atomic service synchronization transaction for each atomic service included in the data synchronization transaction;
[0017] The branch transaction management module includes a branch transaction registration module;
[0018] The branch transaction registration module is connected to the atomic service calling module, and the branch transaction registration module initiates a registration process corresponding to the atomic service synchronization transaction to the transaction manager.
[0019] On the other hand, the data synchronization transaction includes a data submission transaction;
[0020] The transaction orchestration module also includes:
[0021] A branch transaction submission module, wherein the branch transaction submission module obtains the data submission transaction submitted by the transaction manager and creates a branch submission transaction;
[0022] The atomic service management module includes a first submission module;
[0023] The first submission module calls the corresponding atomic service according to the branch submission transaction to generate the external synchronization transaction and sends it to the external middle platform service.
[0024] On the other hand, the data synchronization transaction includes a data rollback transaction;
[0025] The transaction orchestration module also includes:
[0026] A branch transaction rollback module, wherein the branch transaction rollback module obtains the data synchronization transaction submitted by the transaction manager and creates a branch rollback transaction;
[0027] The atomic service management module includes a second submission module;
[0028] The second commit module calls the corresponding atomic service according to the branch rollback transaction to generate the external synchronization transaction and sends it to the external middle platform service.
[0029] On the other hand, the transaction orchestration module further includes:
[0030] A global lock module, the global lock module is connected to the atomic service management module;
[0031] The atomic service management module includes a global lock management module, and the global lock management module is connected to the atomic service calling module;
[0032] When the atomic service calling module parses and obtains the atomic service, the global lock management module generates a global lock query instruction according to the atomic service;
[0033] The global lock management module extracts the corresponding global lock from the global lock module according to the global lock query instruction;
[0034] The global lock is used to control the atomic service.
[0035] On the other hand, the transaction orchestration module further includes:
[0036] A data snapshot module, the data snapshot module is connected to the atomic service management module;
[0037] The atomic service management module includes a snapshot management module, and the snapshot management module is connected to the global lock management module;
[0038] When the global lock management module unlocks the atomic service, the snapshot management module generates snapshot data according to the data synchronization transaction and stores the snapshot data in the data snapshot module.
[0039] On the other hand, when a plurality of the data synchronization transactions call the atomic service in sequence, the global lock management module temporarily stores the data synchronization transactions, and unlocks and locks back the atomic service in sequence.
[0040] On the other hand, the second submission module includes a compensation service calling module;
[0041] The compensation service calling module is connected to the data snapshot module, and when the branch rollback transaction is triggered, the compensation service calling module generates the external synchronization transaction according to the snapshot data.
[0042] On the other hand, the transaction orchestration module further includes:
[0043] A branch transaction log module, wherein the branch transaction log module is connected to the branch transaction management module;
[0044] The branch transaction log module creates a branch transaction log according to the data synchronization transaction.
[0045] The above technical solution has the following advantages or beneficial effects:
[0046] In order to solve the problem in the prior art that the superior middle-office service and the local middle-office service need to edit the corresponding code for the atomic business separately when rolling back, resulting in low development efficiency, this solution introduces a transaction orchestration component. According to the data synchronization transaction of the local middle-office service in the local business system, the data synchronization process for the external middle-office business is initiated synchronously, and the same transaction synchronization branch for the external middle-office service is realized. There is no need to manually build the atomic code, which achieves better development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS
[0047] The embodiments of the present invention will be described more fully with reference to the attached drawings, which are provided for illustration and description only and are not intended to limit the scope of the present invention.
[0048] Figure 1 It is an overall schematic diagram of an embodiment of the present invention;
[0049] Figure 2 A schematic diagram of an atomic service calling module in an embodiment of the present invention;
[0050] Figure 3 is a schematic diagram of a first submission module in an embodiment of the present invention;
[0051] Figure 4 is a schematic diagram of a second submission module in an embodiment of the present invention;
[0052] Figure 5 Schematic diagram of a global lock module in an embodiment of the present invention;
[0053] Figure 6 A schematic diagram of an atomic service calling module in an embodiment of the present invention;
[0054] Figure 7 Schematic diagram of a branch transaction log module in an embodiment of the present invention. DETAILED DESCRIPTION
[0055] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0056] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.
[0057] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, but they are not intended to limit the present invention.
[0058] The present invention comprises:
[0059] A transaction data processing system that supports middle office services, such as Figure 1 As shown, it includes a transaction orchestration module A1, a transaction manager A2, a local middle office service A3 and an external middle office service A4;
[0060] The input end of the transaction orchestration module A1 is connected to the transaction manager A2;
[0061] The output end of the transaction orchestration module A1 is connected to the external middle office service A4;
[0062] Transaction manager A2 connects to local middle office service A3;
[0063] When the transaction manager A2 submits a data synchronization transaction to the local middle office service A3, the transaction orchestration module A1 constructs an external synchronization transaction corresponding to the data synchronization transaction to the external middle office service A4 and sends it to the external middle office service A4.
[0064] Specifically, in order to address the problem in the prior art that the superior middle-office service and the local middle-office service need to edit the corresponding code for the atomic business separately during rollback, resulting in low development efficiency, in this embodiment, a transaction orchestration component A1 is introduced, which initiates the data synchronization process for the external middle-office service A4 based on the data synchronization transaction of the local middle-office service A3 in the local business system, thereby realizing the same transaction synchronization branch for the external middle-office service A4, eliminating the need to manually construct atomic code, and achieving better development efficiency.
[0065] During implementation, the transaction data processing system further includes a local application as a data source and a local business database as a local storage.
[0066] The local application is mainly used as the data source of the local business system. It provides the front-end page to interact with the user, and generates and retrieves the data provided by the local middle-end service A3. During the production process, the local application will generate some production data, which needs to be entered into the local business database for storage through transaction submission.
[0067] Taking the local data storage process as an example, two storage methods can be used, such as sending it directly to the local middle office service A3 through the local application. The local middle office service A3 then pre-processes the data, such as basic normalization and formatting, and also processes it with specific processing algorithms before inputting it into the local business database for storage.
[0068] In another embodiment, in order to achieve a better transaction submission process, the local application first initiates a transaction submission through the transaction manager A2 (TM), and the transaction manager A2 sends a data synchronization transaction to the local middle-office service A3. The local middle-office service A3 then pre-processes the data, such as basic normalization and formatting, and processes it with specific processing algorithms before inputting it into the local business database for storage.
[0069] In the prior art, the process of synchronizing the external middle-office service A4, especially the departmental middle-office service built by a specific government agency described in the background technology, mainly relies on manually written code, which is inefficient.
[0070] To address this issue, in this embodiment, a transaction orchestration module A1 is introduced, which can build corresponding external synchronization transactions based on data synchronization transactions and send them to the external middle-office service A4, thereby realizing a distributed transaction processing mechanism on the transaction manager A2 side that is the same as the local middle-office service A3, reducing the difficulty of docking with the middle-office atomic service.
[0071] In one embodiment, the transaction orchestration module A1 includes an atomic service orchestration module 1 and a branch transaction management module 2 that are connected to each other;
[0072] like Figure 2 As shown, the atomic service management module 1 includes an atomic service calling module 11;
[0073] The atomic service calling module 1 constructs an atomic service synchronization transaction for each atomic service included in the data synchronization transaction;
[0074] The branch transaction management module 2 includes a branch transaction registration module 21;
[0075] The branch transaction registration module 21 is connected to the atomic service calling module 1 , and the branch transaction registration module 21 initiates a registration process corresponding to the atomic service synchronization transaction to the transaction manager A2 .
[0076] Specifically, in order to achieve better maintenance of the transaction submission process, in this embodiment, firstly, an atomic service orchestration module 1 and a branch transaction management module 2 that are interconnected are set in the transaction orchestration module A1.
[0077] The atomic service management module 1 includes an atomic service calling module 11, which is used to construct an atomic service synchronization transaction for each atomic service included in the data synchronization transaction.
[0078] During the implementation process, the atomic service management module 1 is first accessed through the local middle platform service A3 so that the atomic service management module 1 can be informed of the data synchronization transaction that may need to be submitted subsequently.
[0079] According to the data synchronization transaction, the atomic service associated with the transaction submission can be parsed. The atomic service calling module 1 constructs an atomic service synchronization transaction for each atomic service included in the data synchronization transaction, and registers a branch transaction to the branch transaction registration module 21 for subsequent transaction submission to the external middle office service A4.
[0080] If the branch transaction is created for the first time, the branch transaction registration module 21 also initiates a registration process corresponding to the atomic service synchronization transaction to the transaction manager A2, so that when the transaction manager A2 subsequently commits the transaction to the local middle office service A3, it will simultaneously commit the branch transaction to the external middle office service A4.
[0081] In one embodiment, the data synchronization transaction includes a data commit transaction;
[0082] like Figure 3 As shown, the branch transaction management module 2 also includes:
[0083] The branch transaction submission module 22 obtains the data submission transaction submitted by the transaction manager A2 and creates a branch submission transaction;
[0084] The atomic service management module 1 includes a first submission module 12;
[0085] The first submission module 12 generates an external synchronization transaction based on the branch submission transaction call corresponding atomic service and sends it to the external middle platform service.
[0086] Based on the above settings, when the registration of the branch transaction in the branch transaction registration module 21 and the transaction manager A2 is completed, the global transaction submission of the local middle office service A3 and the external middle office service A4 can be realized based on the above settings.
[0087] Specifically, for a single global transaction submission process, transaction manager A2 will create two branch transactions, corresponding to two middle-office services respectively.
[0088] For the branch transaction on the side of the external middle office service A4, the transaction manager A2 first creates a data submission transaction for the data to be synchronized, and carries the transaction context, including global transaction information and current branch transaction information. When the branch transaction registered by the transaction orchestration module 2 is executed, the data submission transaction is submitted to the branch transaction submission module 22. The branch transaction submission module 22 obtains the data submission transaction submitted by the transaction manager A2 and creates a branch submission transaction. Then the first submission module 12 generates an external synchronization transaction based on the branch submission transaction call corresponding atomic service, and sends it to the external middle office service to complete the data submission process.
[0089] In one embodiment, the data synchronization transaction includes a data rollback transaction;
[0090] like Figure 4 As shown, the branch transaction management module 2 also includes:
[0091] The branch transaction rollback module 23 obtains the data rollback transaction submitted by the transaction manager and creates a branch rollback transaction;
[0092] The atomic service management module 1 includes a second submission module 13;
[0093] The second commit module 13 generates an external synchronization transaction based on the branch rollback transaction call corresponding atomic service and sends it to the external middle platform service.
[0094] Specifically, when a transaction is not fully executed successfully, the relevant data submitted by the transaction needs to be rolled back, and the local middle office service A3 applies to the transaction manager A2 for transaction rollback.
[0095] The transaction manager A2 builds a data rollback transaction based on the last data submission transaction that was not successfully executed, and carries the transaction context, including the global transaction information and the current branch transaction information for queuing. When the data rollback transaction is executed, the data rollback transaction is submitted to the branch transaction rollback module 23. The branch transaction rollback module 23 creates a branch rollback transaction based on the data rollback transaction submitted by the transaction manager. Then the second submission module 13 generates an external synchronization transaction based on the branch rollback transaction call corresponding atomic service, and sends it to the external middle office service for synchronous data rollback.
[0096] In one embodiment, Figure 5 As shown, the transaction orchestration module 2 also includes:
[0097] A global lock module 3, the global lock module 3 is connected to the atomic service management module 1;
[0098] The atomic service management module 1 includes a global lock management module 14, and the global lock management module 14 is connected to the atomic service calling module 11;
[0099] When the atomic service calling module 11 parses and obtains the atomic service, the global lock management module 14 generates a global lock query instruction according to the atomic service;
[0100] The global lock management module 14 extracts the corresponding global lock from the global lock module 3 according to the global lock query instruction;
[0101] The global lock is used to control atomic services.
[0102] Specifically, in view of the problem that multiple transactions are submitted concurrently in the actual application process, which may cause data synchronization transaction errors, in this solution, a global lock module 3 is added to the transaction orchestration module 2, and the global lock module 3 is used to control the atomic service. That is, when the data synchronization transaction is not triggered, the atomic service is locked by the global lock. When the data synchronization transaction is triggered, the atomic service is first unlocked, and then the corresponding data synchronization transaction is executed, and then the atomic service is locked back.
[0103] When multiple data synchronization transactions call atomic services in sequence, the global lock management module 3 temporarily stores the data synchronization transactions and unlocks and relocks the atomic services in sequence.
[0104] Through the above settings, data isolation can be controlled when multiple transactions are executed concurrently, ensuring that each transaction can read and write access to database data, avoiding dirty reading and writing of data, and ensuring data accuracy and consistency.
[0105] There are two businesses executing concurrently. Business 1 starts executing the atomic service at time t1, and the data state is d1. The atomic service is completed at time t3, and the data state after execution is d2. Business 1 transaction ends at time t5. Business 2 starts executing the atomic service at time t2, and the data state is d1. The atomic service is completed at time t4, and the data state after execution is d3. Business 2 transaction ends at time t6.
[0106] Assuming that the atomic services executed by two businesses are the same and the objects of the atomic services operations are the same, in the absence of global locks to control data isolation, the expected data status of the middle platform may not match the actual status. For example, when the transaction of business 1 is rolled back and the transaction of business 2 is committed, the expected data status should be d3 at the end of the transaction of business 2. In fact, due to the rollback of business 1, the data status returns to d1, resulting in data inconsistency.
[0107] In order to solve this problem, a global lock module 3 is added to the transaction orchestration module 2. Before executing the data synchronization transaction, a global lock is acquired for the operation object. After that, the transaction that has acquired the lock can continue to execute, and the other transactions need to wait to ensure that the transaction concurrency result is correct; the global lock is released at the end of the branch submission transaction to ensure that other transactions can reacquire the global lock.
[0108] To achieve the above operations, the global lock is composed of a service and a service parameter (equivalent to the row lock granularity of the database). The lock name of the global lock is a combination of the service number and the unique identifier of the service parameter as the lock object; if the unique identifier of the parameter consists of multiple fields, they are spliced together in order of field names; if the service parameter is a collection (or array), each element of the collection is locked separately.
[0109] When executing the actual data synchronization transaction, when the atomic service calling module 11 parses and obtains the atomic service, the global lock management module 14 acquires the lock based on the input parameter and service number of the currently pointed atomic service as the lock name, and extracts the field information (which can be composed of multiple fields) that can represent the unique identifier of the input parameter and the atomic service name to form the lock name. If the input parameter is a collection (array), the lock is acquired for each element in the collection, so as to find the corresponding global lock and unlock it, and then perform lock control according to the above process.
[0110] In one embodiment, Figure 6 As shown, the transaction orchestration module 2 also includes:
[0111] The data snapshot module 4 is connected to the atomic service management module 1;
[0112] The atomic service management module 1 includes a snapshot management module 15, and the snapshot management module 15 is connected to the global lock management module 14;
[0113] When the global lock management module 14 unlocks the atomic service, the snapshot management module 15 generates snapshot data according to the data synchronization transaction and stores it in the data snapshot module.
[0114] Specifically, in order to support data rollback transactions, a data snapshot module 4 and a snapshot management module 15 are also constructed in this embodiment. Data snapshot refers to retaining a copy of the data before the atomic service changes the data in the business middle station, which is used when the atomic service rolls back the transaction as an input parameter of the compensation service. The data snapshot is determined according to the operation type of the atomic service. If the atomic service is to add data, the input parameter of the atomic service is used as the data snapshot. If it is another type, it is obtained through the query service query of the external middle station service A4. This operation needs to be completed before calling the atomic service through the middle station.
[0115] In one embodiment, the atomic service management module 1 includes a compensation service calling module 16, and the second submission module 12 is connected to the compensation service calling module 16;
[0116] The compensation service calling module 16 is connected to the data snapshot module 4. When triggering a branch rollback transaction, the compensation service calling module 16 generates an external synchronization transaction according to the snapshot data.
[0117] Specifically, in order to achieve a better transaction rollback effect, in this embodiment, the atomic service management module 1 includes a compensation service calling module 16. When the second commit module 12 triggers a branch rollback transaction, the compensation service calling module 16 retrieves the corresponding data snapshot according to the branch rollback transaction and generates an external synchronization transaction according to the snapshot data.
[0118] In one embodiment, Figure 7 As shown, the transaction orchestration module A1 also includes:
[0119] A branch transaction log module 5, the branch transaction log module 5 is connected to the branch transaction management module 2;
[0120] The branch transaction log module 5 creates a branch transaction log according to the data synchronization transaction.
[0121] Specifically, in order to achieve better transaction management, the present embodiment also introduces a branch transaction log module 5 to create a branch transaction log according to the data synchronization transaction.
[0122] Specifically, the branch transaction log is a log record managed by the branch transaction log, which is used to track the execution status and execution order of multiple transaction operations in the branch transaction. In the first phase of the transaction, it is used to record and track the execution status of transaction operations. Each transaction operation generates a record, and after the execution is completed, the status value is updated in time. In the second phase of the transaction rollback, the branch transaction is compensated according to the records of the branch transaction log, and service compensation is performed for each successfully executed transaction operation.
[0123] The above are only preferred embodiments of the present invention, and are not intended to limit the implementation methods and protection scope of the present invention. Those skilled in the art should be aware that all solutions obtained by equivalent substitutions and obvious changes made using the description and illustrations of the present invention should be included in the protection scope of the present invention.
Claims
1. A transaction data processing system supporting middle office services, characterized in that: Includes transaction orchestration module, transaction manager, local middle office service and external middle office service; The input end of the transaction orchestration module is connected to the transaction manager; The output end of the transaction orchestration module is connected to the external middle office service; The transaction manager is connected to the local middle office service; When the transaction manager submits a data synchronization transaction to the local middle office service, the transaction orchestration module constructs an external synchronization transaction corresponding to the data synchronization transaction to the external middle office service, and sends it to the external middle office service.
2. The transaction data processing system according to claim 1, characterized in that: The transaction orchestration module includes an atomic service orchestration module and a branch transaction management module that are interconnected; The atomic service management module includes an atomic service calling module; The atomic service calling module constructs an atomic service synchronization transaction for each atomic service included in the data synchronization transaction; The branch transaction management module includes a branch transaction registration module; The branch transaction registration module is connected to the atomic service calling module, and the branch transaction registration module initiates a registration process corresponding to the atomic service synchronization transaction to the transaction manager.
3. The transaction data processing system according to claim 2, characterized in that: The data synchronization transaction includes a data submission transaction; The branch transaction management module also includes: A branch transaction submission module, wherein the branch transaction submission module obtains the data submission transaction submitted by the transaction manager and creates a branch submission transaction; The atomic service management module includes a first submission module; The first submission module calls the corresponding atomic service according to the branch submission transaction to generate the external synchronization transaction and sends it to the external middle platform service.
4. The transaction data processing system according to claim 2, characterized in that: The data synchronization transaction includes a data rollback transaction; The branch transaction management module also includes: A branch transaction rollback module, wherein the branch transaction rollback module obtains the data rollback transaction submitted by the transaction manager and creates a branch rollback transaction; The atomic service management module includes a second submission module; The second commit module calls the corresponding atomic service according to the branch rollback transaction to generate the external synchronization transaction and sends it to the external middle platform service.
5. The transaction data processing system according to claim 4, characterized in that: The transaction orchestration module also includes: A global lock module, the global lock module is connected to the atomic service management module; The atomic service management module includes a global lock management module, and the global lock management module is connected to the atomic service calling module; When the atomic service calling module parses and obtains the atomic service, the global lock management module generates a global lock query instruction according to the atomic service; The global lock management module extracts the corresponding global lock from the global lock module according to the global lock query instruction; The global lock is used to control the atomic service.
6. The transaction data processing system according to claim 5, characterized in that: The transaction orchestration module also includes: A data snapshot module, the data snapshot module is connected to the atomic service management module; The atomic service management module includes a snapshot management module, and the snapshot management module is connected to the global lock management module; When the global lock management module unlocks the atomic service, the snapshot management module generates snapshot data according to the data synchronization transaction and stores the snapshot data in the data snapshot module.
7. The transaction data processing system according to claim 2, characterized in that: When a plurality of the data synchronization transactions call the atomic service in sequence, the global lock management module temporarily stores the data synchronization transactions, and unlocks and relocks the atomic service in sequence.
8. The transaction data processing system according to claim 6, characterized in that: The atomic service management module includes the compensation service calling module, and the second submission module is connected to the compensation service calling module; The compensation service calling module is connected to the data snapshot module, and when the branch rollback transaction is triggered, the compensation service calling module generates the external synchronization transaction according to the snapshot data.
9. The transaction data processing system according to claim 2, characterized in that: The transaction orchestration module also includes: A branch transaction log module, wherein the branch transaction log module is connected to the branch transaction management module; The branch transaction log module creates a branch transaction log according to the data synchronization transaction.