Transaction service arrangement system
Through the transaction service orchestration system, the asynchronous transaction processing process is optimized, the priority of transaction interfaces and query interfaces is configured, and the parallel execution queue and asynchronous task queue are used, combined with batch running services, the complexity and timeliness of asynchronous transaction processing are solved, and the problem of asynchronous transaction processing is realized. Transaction processing efficiency improves and reduces risks.
Patent Information
- Application Number
- CN202410978212.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-22
- Publication Date
- 2024-11-12
AI Technical Summary
In the field of financial technology, the asynchronous transaction processing logic is complex, which makes the processing logic difficult, there is a risk of transaction failure or data inconsistency, and the timeliness is difficult to guarantee, making it easy to fall into a deadlock or wait for a long time.
Provide a trading service orchestration system, which configures modules, type marking modules and interface orchestration modules through the trading service interface, optimizes the asynchronous transaction processing process, configures the priority of the transaction interface and query interface, and uses parallel execution queues and asynchronous task queues for task orchestration. , combined with batch service, realize series call of transaction results, reduce professional requirements and improve transaction processing efficiency.
It achieves the efficiency of transaction processing, reduces the risk of transaction failure, ensures the timeliness and consistency of transactions, simplifies transaction processes, and facilitates fault processing and data management.
Smart Images

Figure CN118941233A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a transaction service orchestration system. Background Art
[0002] In the field of financial technology, transaction scenarios involve the query, merging and calculation of large amounts of data, which are usually very time-consuming. Therefore, traditional transaction interfaces usually use asynchronous processing, which is particularly important when the core transaction interface depends on multiple other transaction interfaces. Asynchronous operation processing usually includes two remote calls: one is the transaction processing interface, and the other is the transaction result query interface.
[0003] In specific application scenarios, for example, when configuring a public transfer transaction, the pre-operation depends on transaction verification. First, you need to configure a series of atomic interfaces, such as transaction query, transaction verification, public transfer and transfer result query, and configure the priority: transaction query has the highest priority, followed by transaction verification, public transfer and transfer query. All these interfaces are connected in sequence according to priority to ensure the smooth progress of the transaction process. In order to realize the entire transaction closed loop, batch groups are usually set up: one group is responsible for transaction initiation tasks, and the other group is responsible for asynchronous result query tasks. The batch mechanism is used to self-drive the business process to achieve the final completion of the transaction.
[0004] Although this complex asynchronous transaction processing method can achieve eventual consistency of transactions, if each core transaction depends on the success of other transactions, it is necessary to ensure that all dependent transactions are successful before proceeding to the next step. If the final transaction fails, the previous transaction needs to be rolled back. If one of the dependent transactions succeeds and the other fails, the successful transaction also needs to be rolled back.
[0005] As the number of asynchronous transactions increases, the processing logic becomes extremely complex, and managing these asynchronous operations becomes more difficult. Coordination is required between multiple asynchronous operations to ensure that they are executed in the expected order. This requires the system to have strong concurrent processing capabilities and precise state management functions to avoid transaction failures or data inconsistencies due to improper processing.
[0006] In transaction scenarios, it is necessary not only to ensure the final consistency of transactions, but also to ensure the timeliness of processing. However, the existing asynchronous processing logic has the risk of causing transaction processing to deadlock or wait for a long time. Summary of the invention
[0007] The embodiment of the present application provides a transaction service orchestration system to optimize the asynchronous transaction processing flow, improve processing efficiency, and reduce the risk of transaction failure.
[0008] In order to achieve the above objectives, the present application embodiment provides a transaction service orchestration system, including:
[0009] A transaction service interface configuration module, configured to include: a transaction interface and a query interface, wherein the transaction interface is used to perform transaction operations, including but not limited to: transaction flow query, fund occupation, recharge, and transfer, and the query interface is used to obtain transaction operation results of the transaction interface;
[0010] A type marking module is used to mark the transaction interface and query interface as synchronous interface or asynchronous interface, wherein the asynchronous interface allows configuration of dependent interfaces, the asynchronous interface executes tasks in a parallel asynchronous task queue, and the synchronous interface executes tasks in a parallel execution queue. The synchronous interface is used to call required data according to a transaction request and immediately return a call result, and the asynchronous interface is used to process data in the background according to a transaction call request and notify the caller after completion;
[0011] The interface orchestration module configures the priority of the transaction interface and / or the priority of the query interface, arranges the calling sequence between the transaction interface and the query interface based on the business logic of the transaction service, triggers the call to the parallel execution queue through the batch service based on the priority and the arranged calling sequence, and mounts multiple transaction interfaces and query interfaces under the transaction batch service, wherein the tasks in the parallel execution queue and the tasks in the asynchronous task queue are called in series according to the arranged calling sequence.
[0012] In some embodiments, the interface arrangement module further includes:
[0013] The priority configuration unit configures the priority order of the transaction interface and / or query interface based on the business logic of the transaction service, so as to implement sequential execution of the interfaces according to the priority order.
[0014] In some embodiments, the interface arrangement module further includes:
[0015] The parallel execution configuration unit configures and binds the transaction interfaces and / or query interfaces that can be executed in parallel in the business logic according to the interface path, interface input parameters, and interface output parameters, and marks the interfaces with the same priority, thereby realizing batch parallel execution of transaction interfaces with the same priority and that can be executed in parallel.
[0016] In some embodiments, the interface arrangement module further includes:
[0017] When multiple dependent interfaces are set under the asynchronous interface, operations are performed according to the priority and execution type of the dependent interfaces. The execution type includes synchronous execution and parallel execution. The synchronous execution means serial execution between business requests, and the parallel execution means that the interfaces marked by the parallel execution configuration unit are executed simultaneously to shorten the transaction time.
[0018] In some embodiments, the interface arrangement module further includes:
[0019] The interface group editing unit divides the query interface into a parameter preparation query interface group and an asynchronous result query interface group according to the execution requirement stage. The query interface in the parameter preparation query interface group is used to obtain or verify the required parameter information before the batch task is executed; the query interface in the asynchronous result query interface group is used to query the execution status or result of the task after the batch task is executed.
[0020] In some of the embodiments, the interface orchestration module provides a batch configuration interface, which is connected to a technical platform for configuring batch services, thereby allowing querying and setting batch times.
[0021] In some of the embodiments, the batch running time is configured in the form of a time period combined with time, such as hourly, daily, weekly, and time such as 8:00, 12:20, etc. Compared with the prior art configured according to cron expressions, this form reduces professional requirements to facilitate configuration by business personnel.
[0022] In some embodiments, the transaction operation result includes: success, failure, or processing.
[0023] In some embodiments, the transaction interface further includes:
[0024] The transaction cancellation interface is used to perform a failed cancellation operation when the query interface fails to obtain the transaction operation result of the transaction interface;
[0025] The transaction cancellation query interface is used to query the cancellation operation results of the transaction cancellation interface.
[0026] In some embodiments, the transaction cancellation interface is marked as an asynchronous interface, and the transaction cancellation query interface is marked as a synchronous interface.
[0027] Compared with the related art, the transaction service orchestration system provided in the embodiment of the present application, by combining the transaction interface logic orchestration, the transaction query interface logic orchestration and the batch running time orchestration, finally outputs the entire core transaction result, and standardizes and configures transaction operations through abstract configuration, thereby reducing the research and development time; through dual-pipeline batch running services and open time, the serial and parallel trigger times can be flexibly set according to the asynchronous time efficiency of their own transaction interfaces, thereby greatly shortening the entire transaction time; the upper and lower configurations of the transaction interface are connected and the priority and parallel sequence are set, so that the execution order is clear and easy to debug; as a whole, the hard-coded business logic is packaged through standardized service orchestration to package the core transactions of the scene, so that the output is standardized and the connection is convenient.
[0028] Details of one or more embodiments of the present application are set forth in the following drawings and description to make other features, objects, and advantages of the present application more readily apparent. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0030] Figure 1 is a structural block diagram of a transaction service orchestration system according to an embodiment of the present application;
[0031] Figure 2 is a block diagram of a subunit structure of a transaction service orchestration system according to an embodiment of the present application;
[0032] Figure 3 It is a timing diagram of the working principle of the transaction service encoding system according to the preferred embodiment of the present application.
[0033] In the figure: 1. Transaction service interface configuration module; 2. Type marking module; 3. Interface orchestration module; 301. Priority configuration unit; 302. Parallel execution configuration unit; 303. Interface group editing unit. DETAILED DESCRIPTION
[0034] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is described and illustrated below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not intended to limit the present application. Based on the embodiments provided in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.
[0035] Obviously, the drawings described below are only some examples or embodiments of the present application. For ordinary technicians in this field, the present application can also be applied to other similar scenarios based on these drawings without creative work. In addition, it can also be understood that although the efforts made in this development process may be complicated and lengthy, for ordinary technicians in this field related to the content disclosed in this application, some changes in design, manufacturing or production based on the technical content disclosed in this application are just conventional technical means, and should not be understood as insufficient content disclosed in this application.
[0036] Reference to "embodiment" in this application means that a particular feature, structure, or characteristic described in conjunction with the embodiment may be included in at least one embodiment of the present application. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments.
[0037] The words "one", "a", "a kind of", "the" and the like involved in this application do not indicate a quantity limitation, and may indicate the singular or plural. The terms "include", "comprise", "have" and any of their variations involved in this application are intended to cover non-exclusive inclusions; for example, a process, method, system, product or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units that are not listed, or may also include other steps or units inherent to these processes, methods, products or devices. The words "connect", "connected", "coupled" and the like involved in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "multiple" involved in this application refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships, for example, "A and / or B" may indicate: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0038] In digital currency exchanges, transaction rollback usually means that when a transaction process fails or seriously deviates from the original intention of the transaction, the transaction system will cancel all completed transaction operations in the transaction database and restore them to a certain state before the transaction.
[0039] This embodiment provides a transaction service orchestration system. Figure 1 is a structural block diagram of a transaction service orchestration system according to an embodiment of the present application. Figure 1 As shown, the transaction service arrangement system includes: transaction service interface configuration module 1, type marking module 2, interface arrangement module 3 and other components. Those skilled in the art can understand that Figure 1The transaction service orchestration system structure shown in the figure does not constitute a limitation on the transaction service orchestration system, and may include more or less components than shown in the figure, or combine certain components, or arrange the components differently.
[0040] Combine the following Figure 1 The following is a detailed introduction to the various components of the transaction service orchestration system:
[0041] The transaction service interface configuration module 1 is used to configure the transaction service interface to include: a transaction interface and a query interface. The transaction interface is used to perform transaction operations, including but not limited to: transaction flow query, fund occupation, recharge, and transfer, which are not listed here one by one. The query interface is used to obtain the transaction operation results of the transaction interface, and the transaction operation results include: success, failure, or processing;
[0042] The type marking module 2 is used to mark the transaction interface and the query interface as a synchronous interface or an asynchronous interface, wherein the asynchronous interface allows the configuration of dependent interfaces, the asynchronous interface executes tasks in a parallel asynchronous task queue, and the synchronous interface executes tasks in a parallel execution queue. The synchronous interface allows the configuration of the next-level synchronous interface or asynchronous interface. When an asynchronous interface is configured under a synchronous interface, it actually belongs to an asynchronous interface, and the updateable interface is marked as an asynchronous interface. When the lower-level interfaces configured under the synchronous interface are all synchronous interfaces, they are maintained as synchronous interfaces. The synchronous interface is used to call the required data according to the transaction request and immediately return the call result. The asynchronous interface is used to process data in the background according to the transaction call request and notify the caller after completion.
[0043] It should be noted that when multiple dependent interfaces are set under an asynchronous interface, operations are performed according to the priority and execution type of the dependent interfaces. The execution types include synchronous execution and parallel execution. Synchronous execution means serial execution between business requests, and parallel execution means that the interfaces marked by the parallel execution configuration unit are executed simultaneously to shorten the transaction time.
[0044] The interface orchestration module 3 is used to configure the priority of the transaction interface and / or the priority of the query interface, arrange the calling sequence between the transaction interface and the query interface based on the business logic of the transaction service, trigger the call to the parallel execution queue through the batch service based on the priority and the arranged calling sequence, and mount multiple transaction interfaces and query interfaces under the transaction batch service, wherein the tasks in the parallel execution queue and the tasks in the asynchronous task queue are called in series according to the arranged calling sequence.
[0045] The interface arrangement module 3 further includes: a priority configuration unit 301 , a parallel execution configuration unit 302 and an interface group editing unit 303 .
[0046] The priority configuration unit 301 is used to configure the priority order of the transaction interface and / or query interface based on the business logic of the transaction service, and is used to implement the sequential execution of the interface according to the priority order. The business logic of the transaction service here can be obtained by parsing the specified transaction service process, including obtaining the process nodes of the transaction service and identifying the entities related to the transaction service, determining the conditions, processing logic or rules of the transaction operation according to the business rules, and identifying the key nodes in the process as the logical basis for the transaction interface configuration and subsequent call sequence in this application.
[0047] The parallel execution configuration unit 302 is used to configure and bind the transaction interfaces and / or query interfaces that can be executed in parallel in the business logic according to the interface path, interface input parameters, and interface output parameters, and mark the interfaces with the same priority, so as to achieve batch parallel execution of transaction interfaces with the same priority and that can be executed in parallel. For example, when there are multiple asynchronous transactions operating at the same time, we can compile the asynchronous result query into the same task group by marking, initiate parallel execution, and then execute the next step according to their respective results.
[0048] The interface group editing unit 303 is used to divide the query interface into a parameter preparation query interface group and an asynchronous result query interface group according to the execution requirement stage. The query interface in the parameter preparation query interface group is used to obtain or verify the required parameter information before running the batch task; the query interface in the asynchronous result query interface group is used to query the execution status or result of the task after running the batch task.
[0049] In some of the embodiments, the interface arrangement module provides a batch configuration interface, which is connected to the technical platform for configuring the batch service, so as to allow querying and setting the batch time. Optionally, the technical platform can be Apache Airflow, Spring Cloud Task, AWS Batch or Azure Batch, etc. Based on this, business personnel can flexibly set the serial and parallel trigger time according to the asynchronous time of their own transaction interface, so that the whole transaction time is greatly shortened. In the embodiment of the present application, the batch time is configured in the form of a time cycle combined with time. The time cycle is such as hourly, daily, and weekly, and the time is such as 8:00, 12:20, etc. Compared with the prior art configuration according to the cron expression, this form reduces the professional requirements to facilitate the configuration of business personnel.
[0050] In order to handle transaction failures, the transaction interface also includes: a transaction cancellation interface and a transaction cancellation query interface, wherein the transaction cancellation interface is used to perform a failed cancellation operation when the query interface fails to obtain the transaction operation result of the transaction interface; the transaction cancellation query interface is used to query the cancellation operation result of the transaction cancellation interface. In the type marking module 2, the transaction cancellation interface is marked as an asynchronous interface, and the transaction cancellation query interface is marked as a synchronous interface.
[0051] Based on the above configuration, the transaction service orchestration system of the present application is based on the logical orchestration of the interface and the batch time orchestration, executes the transaction service request, outputs the transaction result, and uses asynchronous and parallel dual pipelines to greatly shorten the logic processing time. The batch time is orchestrated by exposing the batch time parameters of the batch service, and the interface serial and parallel trigger time can be flexibly set; the transaction interface makes the execution order of the orchestration clear according to the conditions and constraints such as the dependent interface or the upper and lower interface connection, interface priority, and parallel interface configured by the transaction interface, and realizes the hard-coded business logic through the orchestration and packaging of the core transactions of the scenario, so that the transaction service output is standardized and convenient for docking.
[0052] The transaction service orchestration system of the present application is applicable to various types of financial transactions, such as merchant transactions, supply chain financial transactions, third-party payments or wallet services, etc. The following takes merchant transactions as an example to describe and illustrate the embodiments of the present application through preferred embodiments.
[0053] Figure 3 This is a timing diagram of the working principle of the transaction service orchestration system according to the preferred embodiment of the present application. Figure 3 As shown, the current transaction in the example includes the interaction between service A, service B, and service C: (1) pre-transaction flow query, (2) calculation of merchant interest subsidy occupancy, (3) recharge, and (4) transfer. Based on this business logic, the working process of the transaction service orchestration system of this application includes the following steps:
[0054] First, configure the transaction service interface for these four service interaction processes, including the transaction interface and the query interface.
[0055] The transaction interfaces include: transaction flow query transaction interface, capital occupation transaction interface, recharge transaction interface, and transfer transaction interface; each transaction interface is configured with the following query interfaces: transaction flow query result query interface, capital occupation query interface, recharge query interface, and transfer query interface to obtain the corresponding transaction results.
[0056] Secondly, mark the transaction interface for transaction flow query, fund occupation, recharge and transfer as asynchronous interfaces, and the results of their transaction operations are: success, failure or processing;
[0057] Mark the transaction query result query interface, fund usage query interface, recharge query interface, and transfer query interface as synchronous interfaces, and configure the transaction query result query interface to have a higher priority than other query interfaces;
[0058] If the transaction operation result queried by the transfer transaction interface is a failure, it is necessary to perform a failed cancellation operation on the interest subsidy occupation transaction and the recharge transaction. The failed cancellation operation can be implemented by configuring the transaction cancellation interface and the transaction cancellation query interface in the transaction service interface. The transaction cancellation interface is used to perform a failed cancellation operation, the occupation failure cancellation interface, and the recharge failure cancellation interface. The transaction cancellation query interface is used to query the cancellation operation results, such as the interest subsidy occupation cancellation result query interface and the recharge cancellation result query interface. The cancellation operation results are: success, failure or in progress. The transaction cancellation interface can be multiple transaction cancellation interfaces adapted to the transaction interface. The transaction cancellation interface is marked as an asynchronous interface, and the transaction cancellation query interface is marked as a synchronous interface.
[0059] Subsequently, taking into account the strong dependency order between the various services of this transaction, the priorities of the transaction interfaces are configured from high to low as follows: transaction flow query transaction interface, fund occupation transaction interface, recharge transaction interface, and transfer transaction interface. It can be understood that: the transaction flow query transaction interface, fund occupation transaction interface, and recharge transaction interface are dependent interfaces under the transfer transaction interface, and the transaction flow query transaction interface is a dependent interface of the fund occupation transaction interface.
[0060] Then, multiple transaction cancellation query interfaces and multiple query interfaces are configured to be executable in parallel and put into a parallel execution queue for parallel execution;
[0061] The above interfaces marked as asynchronous interfaces are put into the asynchronous task queue and are processed in descending order of priority;
[0062] Then, the transaction interface and the query interface are arranged, specifically, the arrangement is as follows: when the transaction operation result is queried by the transaction result query interface, the fund occupation transaction interface with a priority level below the transaction query transaction interface in the asynchronous task queue is called; similarly, when the transaction operation result is queried by the fund occupation query interface, the recharge transaction interface with a priority level below the fund occupation transaction interface in the asynchronous task queue is called. Following this logic, each query interface will serially call the next transaction operation in the asynchronous task queue when the return result is successful; the transaction interfaces in this example are executed in series, but it does not rule out the possibility of parallel execution in other transaction services;
[0063] It should be noted that if the query interface finds that the transaction operation has failed, the corresponding transaction cancellation interface will be called to perform the transaction cancellation operation;
[0064] After the orchestration is completed, the parallel execution queue can be triggered and called through the batch running service. Specifically, the query interfaces in the parallel execution queue except the transaction query result query interface are executed at the same time, which can make more efficient use of system resources and avoid unnecessary waiting and idle time. When the query result is that the transaction operation is successful, the tasks in the asynchronous execution queue are called based on the orchestration order, which improves the overall transaction processing efficiency.
[0065] The above-mentioned embodiment implements the logical orchestration of the interaction between parallel execution queues and asynchronous execution docking based on the transaction service orchestration system of the present application, and completes the entire transaction by asynchronous breakpoint resumption through the batch running service. There is no need to wait during the query process, and the transaction operation results of the transaction interface can be queried at any time to execute the next asynchronous call without waiting for a long time at the original node. Even if an operation fails, the entire system can quickly identify and process it without blocking subsequent processes. The orchestration scheme of the present application can be easily expanded by adjusting the configuration of the interface, parallel execution queue and asynchronous task queue.
[0066] It should be noted that the steps shown in the above process can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.
[0067] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.
Claims
1. A transaction service orchestration system, characterized in that: include: A transaction service interface configuration module, configured to include: a transaction interface and a query interface, wherein the transaction interface is used to perform transaction operations, and the query interface is used to obtain transaction operation results of the transaction interface; A type marking module marks the transaction interface and the query interface as a synchronous interface or an asynchronous interface, wherein the asynchronous interface allows configuration of dependent interfaces, the asynchronous interface executes tasks in a parallel execution queue, and the synchronous interface executes tasks in a parallel execution queue; The interface orchestration module configures the priority of the transaction interface and / or the priority of the query interface, arranges the calling sequence between the transaction interface and the query interface based on the business logic of the transaction service, triggers the call to the parallel execution queue through the batch service based on the priority and the arranged calling sequence, and mounts multiple transaction interfaces and query interfaces under the transaction batch service, wherein the tasks in the parallel execution queue and the tasks in the asynchronous task queue are called in series according to the arranged calling sequence.
2. The transaction service orchestration system according to claim 1, characterized in that: The interface arrangement module further includes: The priority configuration unit configures the priority order of the transaction interface and / or query interface based on the business logic of the transaction service, so as to implement sequential execution of the interfaces according to the priority order.
3. The transaction service orchestration system according to claim 2, characterized in that: The interface arrangement module further includes: The parallel execution configuration unit configures and binds the transaction interfaces and / or query interfaces that can be executed in parallel in the business logic according to the interface path, interface input parameters, and interface output parameters, and marks the interfaces with the same priority.
4. The transaction service orchestration system according to claim 3, characterized in that: The interface arrangement module further includes: When multiple dependent interfaces are set under the asynchronous interface, operations are performed according to the priority and execution type of the dependent interfaces. The execution type includes synchronous execution and parallel execution. The synchronous execution means serial execution between business requests, and the parallel execution means simultaneous execution of the interfaces marked by the parallel execution configuration unit.
5. The transaction service orchestration system according to claim 1, characterized in that: The interface arrangement module further includes: The interface group editing unit divides the query interface into a parameter preparation query interface group and an asynchronous result query interface group according to the execution requirement stage. The query interface in the parameter preparation query interface group is used to obtain or verify the required parameter information before the batch task is executed, and the query interface in the asynchronous result query interface group is used to query the execution status or result of the task after the batch task is executed.
6. The transaction service orchestration system according to claim 1, characterized in that: The interface arrangement module provides a batch configuration interface, which is connected to a technical platform for configuring batch services, thereby allowing querying and setting batch times.
7. The transaction service orchestration system according to claim 6, characterized in that: The batch running time is configured in the form of a time period combined with time.
8. The transaction service orchestration system according to claim 1, characterized in that: The transaction operation results include: success, failure or processing.
9. The transaction service orchestration system according to claim 8, characterized in that: The transaction interface also includes: The transaction cancellation interface is used to perform a failed cancellation operation when the query interface fails to obtain the transaction operation result of the transaction interface; The transaction cancellation query interface is used to query the cancellation operation results of the transaction cancellation interface.
10. The transaction service orchestration system according to claim 9, characterized in that: The transaction cancellation interface is marked as an asynchronous interface, and the transaction cancellation query interface is marked as a synchronous interface.
