Data processing method and device, electronic equipment and storage medium

Abstract

The invention relates to a data processing method and device, electronic equipment and a storage medium, and relates to the technical field of computers, and the method comprises the following steps: obtaining target language description information constructed for a target distributed transaction; analyzing the target language description information to obtain to-be-executed transaction data corresponding to the target distributed transaction; under the condition that a target transaction processing request corresponding to the target distributed transaction is received, based on a preset transaction execution engine, the target transaction processing request and a node execution sequence corresponding to the to-be-executed transaction data, sequentially reading current node configuration data of a current execution node from the to-be-executed transaction data, and based on the current transaction execution mode and the current execution resource, executing a distributed transaction operation corresponding to the current execution node to obtain a target transaction processing result corresponding to the target distributed transaction. According to the embodiment of the invention, the visual mixed arrangement of various transaction execution modes can be realized, so as to adapt to various different complex business scenes.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a data processing method, device, electronic device, and storage medium. Background Art

[0002] In a distributed system, an operation requires the collaborative completion of multiple services. This type of transaction, completed collaboratively across a network, is called a distributed transaction. Traditionally, long-chain transactions are typically implemented in code, which is not only highly complex but also error-prone. To address this issue, researchers have proposed numerous transaction orchestration methods based on domain-specific languages ​​(DSLs). However, these methods often lack visual interfaces, making it difficult for users to intuitively understand and design transaction processes. Furthermore, existing orchestration methods only support a single mode, making the orchestration results unsuitable for a variety of complex distributed business scenarios. Summary of the Invention

[0003] In view of the above-mentioned technical problems, the present disclosure proposes a data processing method, device, electronic device and storage medium.

[0004] According to one aspect of an embodiment of the present disclosure, a data processing method is provided, the method comprising:

[0005] Obtaining target language description information constructed for a target distributed transaction, the target language description information being generated based on transaction flow chart data corresponding to the target distributed transaction, the transaction flow chart data being obtained by performing mixed-mode arrangement on multiple target nodes corresponding to the target distributed transaction based on transaction execution logic of the target distributed transaction, the multiple target nodes including multiple transaction nodes corresponding to multiple transaction execution modes;

[0006] Parsing the target language description information to obtain pending transaction data corresponding to the target distributed transaction;

[0007] Upon receiving a target transaction processing request corresponding to the target distributed transaction, based on a preset transaction execution engine, the target transaction processing request, and the node execution order corresponding to the to-be-executed transaction data, the current node configuration data corresponding to the current execution node among the multiple target nodes is read in sequence from the to-be-executed transaction data, and based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, the distributed transaction operation corresponding to the current execution node is executed to obtain a target transaction processing result corresponding to the target distributed transaction.

[0008] According to another aspect of an embodiment of the present disclosure, a data processing device is provided, the device comprising:

[0009] a description acquisition module, configured to acquire target language description information constructed for a target distributed transaction, the target language description information being generated based on transaction flow chart data corresponding to the target distributed transaction, the transaction flow chart data being obtained by performing mixed-mode arrangement of multiple target nodes corresponding to the target distributed transaction based on the transaction execution logic of the target distributed transaction, the multiple target nodes including multiple transaction nodes corresponding to multiple transaction execution modes;

[0010] A parsing module, configured to parse the target language description information to obtain pending transaction data corresponding to the target distributed transaction;

[0011] an execution module configured to, upon receiving a target transaction processing request corresponding to the target distributed transaction, sequentially read current node configuration data corresponding to a current execution node among the multiple target nodes from the to-be-executed transaction data based on a preset transaction execution engine, the target transaction processing request, and a node execution order corresponding to the to-be-executed transaction data, and execute the distributed transaction operation corresponding to the current execution node based on a current transaction execution mode corresponding to the current node configuration data and a current execution resource corresponding to the current node configuration data, to obtain a target transaction processing result corresponding to the target distributed transaction.

[0012] Optionally, the execution module includes:

[0013] A first node determination module, configured to determine a current execution node based on a node execution order corresponding to the transaction data to be executed;

[0014] a first execution module, configured to read current node configuration data corresponding to the current execution node from the to-be-executed transaction data, and execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, to obtain a current processing result corresponding to the current execution node; the previous processing result corresponding to the current execution node is a processing result obtained by the previous execution node of the current execution node;

[0015] a first node updating module configured to, when the current processing result indicates that the distributed transaction operation corresponding to the current execution node is successfully executed, determine a next execution node corresponding to the current execution node based on the node execution order corresponding to the to-be-executed transaction data, and update the current execution node based on the next execution node;

[0016] a second execution module, configured to repeat, based on the updated current execution node, the steps of reading the current node configuration data corresponding to the current execution node from the to-be-executed transaction data, executing the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode and the current execution resources corresponding to the current node configuration data, obtaining a current processing result corresponding to the current execution node, and updating the transaction execution step of the current execution node based on the next execution node, until the current execution node becomes the end transaction node;

[0017] The first result generating module is configured to generate the target transaction processing result based on the transaction processing results corresponding to the end transaction node and the plurality of intermediate transaction nodes.

[0018] Optionally, the device further includes:

[0019] A rollback execution module is configured to, when the current processing result indicates that the distributed transaction operation corresponding to the current execution node has been executed abnormally, determine, based on the current transaction execution mode and the current execution resource, a rollback execution resource corresponding to the current execution node, and execute a rollback transaction operation corresponding to the rollback execution resource to obtain a current rollback processing result corresponding to the current execution node;

[0020] A second node determination module is configured to determine a previous execution node corresponding to the current execution node based on a node execution order corresponding to the transaction data to be executed;

[0021] A third execution module is configured to update the current execution node based on the previous execution node, and based on the updated current execution node, repeat the steps of determining the rollback execution resource corresponding to the current execution node based on the current transaction execution mode and the current execution resource, and executing the rollback transaction operation corresponding to the rollback execution resource to obtain the current rollback processing result corresponding to the current execution node, and then perform the abnormal rollback step of updating the current execution node based on the previous execution node until the current execution node is the starting transaction node among the multiple transaction nodes, and generating the target transaction processing result based on the rollback processing results corresponding to the rolled back nodes among the multiple transaction nodes; the rolled back nodes are nodes among the multiple transaction nodes on which the rollback transaction operation has been executed.

[0022] Optionally, the first execution module includes:

[0023] An execution resource determination module, configured to determine a target execution resource from the current execution resources based on the current transaction execution mode;

[0024] A fourth execution module is configured to execute a target transaction operation corresponding to the target execution resource based on the previous processing result to obtain the current processing result.

[0025] Optionally, the device further includes:

[0026] A target language acquisition module, configured to acquire a target execution code language corresponding to the target distributed transaction;

[0027] Accordingly, the execution resource determination module includes:

[0028] an identifier determination module, configured to determine a target interface identifier from the at least one to-be-executed interface identifier based on the current transaction execution mode;

[0029] A target resource determination module is used to determine the target execution resource from multiple preset execution resources corresponding to the target interface identifier based on the target execution code language; each preset execution resource in the multiple preset execution resources corresponds to a preset execution code language.

[0030] Optionally, the execution module includes:

[0031] a fifth execution module, configured to, when the current execution node is a transaction node, execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, to obtain the current transaction processing result corresponding to the current execution node;

[0032] a sixth execution module, configured to, when the current execution node is a non-transactional node, execute the non-transactional operation corresponding to the current execution node based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, and obtain the non-transactional processing result corresponding to the current execution node;

[0033] The second result generating module is configured to generate the target transaction processing result based on the transaction processing results corresponding to the ended non-transaction node, the executed transaction node, and the non-transaction processing results corresponding to the executed non-transaction node.

[0034] Optionally, the sixth execution module includes:

[0035] a seventh execution module, configured to execute the non-transactional operation corresponding to the current execution node based on the current execution resources corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, and obtain the non-transactional processing result corresponding to the current execution node, when the previous execution node of the current execution node is a non-transactional node.

[0036] Optionally, the sixth execution module includes:

[0037] an eighth execution module, configured to, when the previous execution node of the current execution node is a transaction node and the previous processing result indicates that the distributed transaction operation corresponding to the previous execution node is successfully executed, execute the non-transactional operation corresponding to the current execution node based on the current execution resources corresponding to the current node configuration data and the previous processing result, and obtain the non-transactional processing result corresponding to the current execution node.

[0038] Optionally, the sixth execution module includes:

[0039] A branch execution module is used to read the current node configuration data corresponding to the branch node when the current execution node is a branch node, obtain the preset branch condition corresponding to the branch node, and execute the branch processing operation corresponding to the current execution node based on the previous processing result corresponding to the current execution node, the preset branch condition and the node execution order corresponding to the transaction data to be executed, to obtain a branch processing result; the branch processing result is used to indicate the next execution node corresponding to the current execution node.

[0040] Optionally, the execution module includes:

[0041] a ninth execution module configured to, when the current execution node is a transaction node, execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, to obtain the current transaction processing result corresponding to the current execution node;

[0042] a combination execution module configured to, when the current execution node is a combination node, execute the combination transaction operation corresponding to the combination node based on the combination node configuration data corresponding to the combination node in the to-be-executed transaction data, and obtain a combination processing result corresponding to the combination node;

[0043] The third result generating module is configured to generate the target transaction processing result based on the transaction processing results corresponding to the ended non-transaction node and the executed transaction node and the combined processing result.

[0044] Optionally, the device further includes:

[0045] A display module, configured to display a transaction orchestration page, wherein the transaction orchestration page includes a node orchestration control;

[0046] A description processing module is used to, when the transaction flow chart data is acquired based on the node orchestration control and a description processing instruction corresponding to the target distributed transaction is detected, perform description processing on the transaction flow chart data to obtain the target language description information.

[0047] According to another aspect of an embodiment of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the above-mentioned data processing method.

[0048] According to another aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform the above-mentioned data processing method.

[0049] According to another aspect of an embodiment of the present disclosure, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the above data processing method.

[0050] The technical solutions provided by the embodiments of the present disclosure bring at least the following beneficial effects:

[0051] By obtaining the target language description information constructed for the target distributed transaction, the target language description information is generated based on the transaction flow chart data corresponding to the target distributed transaction. The transaction flow chart data is obtained by performing mixed mode orchestration on multiple target nodes corresponding to the target distributed transaction based on the transaction execution logic of the target distributed transaction. The multiple target nodes include multiple transaction nodes, and the multiple transaction nodes correspond to multiple transaction execution modes. Visual mixed orchestration of multiple transaction execution modes can be achieved, and the readability and maintainability of transaction orchestration can be improved through the target language description information, thereby reducing the programming complexity in the mixed transaction orchestration process and improving development efficiency to adapt to various complex business scenarios. The target language description information is then parsed and processed to obtain the to-be-executed transaction data corresponding to the target distributed transaction. It can realize the loading and parsing of target language description information, and then, when receiving the target transaction processing request corresponding to the target distributed transaction, based on the preset transaction execution engine, the target transaction processing request and the node execution order corresponding to the transaction data to be executed, the current node configuration data corresponding to the current execution node in multiple target nodes are read from the transaction data to be executed in turn, and based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, the distributed transaction operation corresponding to the current execution node is executed to obtain the target transaction processing result corresponding to the target distributed transaction. This can realize hybrid orchestration of distributed transaction processing, and thus make it easier to realize distributed services for various complex distributed business scenarios, support complex transaction processes, and improve development efficiency.

[0052] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The accompanying drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute an improper limitation of the present disclosure.

[0054] Figure 1 is a schematic diagram of an application system according to an exemplary embodiment;

[0055] Figure 2 is a flow chart showing a data processing method according to an exemplary embodiment;

[0056] Figure 3 This is a schematic diagram showing a page display of a hybrid arrangement of a distributed transaction mode according to an exemplary embodiment;

[0057] Figure 4 This is a schematic diagram showing a page display of mixed transactional and non-transactional arrangement according to an exemplary embodiment;

[0058] Figure 5 is a schematic diagram showing node configuration in a hybrid orchestration process according to an exemplary embodiment;

[0059] Figure 6 is a schematic diagram of execution logic of a hybrid orchestration according to an exemplary embodiment;

[0060] Figure 7 is a block diagram of a data processing device according to an exemplary embodiment;

[0061] Figure 8 is a block diagram of an electronic device for processing a target distributed transaction according to an exemplary embodiment;

[0062] Figure 9 It is a block diagram of another electronic device for processing a target distributed transaction according to an exemplary embodiment. DETAILED DESCRIPTION

[0063] Various exemplary embodiments, features, and aspects of the present application will be described in detail below with reference to the accompanying drawings. The same reference numerals in the accompanying drawings represent elements with the same or similar functions. Although various aspects of the embodiments are shown in the accompanying drawings, the drawings are not necessarily drawn to scale unless otherwise indicated.

[0064] The word “exemplary” is used exclusively herein to mean “serving as an example, example, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.

[0065] In addition, numerous specific details are provided in the detailed description below to better illustrate the present application. Those skilled in the art will appreciate that the present application can be practiced without certain specific details. In some instances, methods, means, components, and circuits well known to those skilled in the art are not described in detail in order to highlight the main purpose of the present application.

[0066] The system involved in the embodiment of the present invention can be a distributed system formed by connecting a client and multiple system nodes (any form of computing device in the access network, such as a server, a user terminal) through network communication. A distributed system can refer to a loosely coupled system consisting of multiple processors interconnected by communication lines. With the rapid development of the Internet, distributed systems have been widely used in various fields. For example, the above-mentioned distributed system can be composed of multiple servers, which can be distributed in different geographical locations; this architecture can provide better performance and scalability, and provide better fault tolerance and user experience.

[0067] Cloud computing refers to the delivery and usage model of IT infrastructure, enabling on-demand, scalable access to required resources over the internet. Broadly speaking, cloud computing refers to the delivery and usage model of services, enabling on-demand, scalable access to required services over the internet. These services can be IT-related, software-related, internet-related, or other services. Cloud computing is the product of the convergence of traditional computer and network technologies, including grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, and load balancing.

[0068] Cloud computing has rapidly grown, driven by the internet, real-time data streams, the diversification of connected devices, and the growing demand for search services, social networks, mobile commerce, and open collaboration. Unlike previous parallel and distributed computing approaches, the emergence of cloud computing will fundamentally revolutionize the entire internet and enterprise management model.

[0069] See also Figure 1 , Figure 11 is a schematic diagram of an application system according to an exemplary embodiment. The application system can be used in the data processing method of the present application. The application system may include at least a server 01 and a terminal 02.

[0070] In the embodiment of the present application, server 01 can be used to process target distributed transactions. Specifically, server 01 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0071] In the embodiment of the present application, terminal 02 can be used to generate target language description information. Terminal 02 can include physical devices such as smartphones, desktop computers, tablet computers, laptops, smart speakers, in-vehicle terminals, digital assistants, augmented reality (AR) / virtual reality (VR) devices, and smart wearable devices. It can also include software running on the physical devices, such as applications. Operating systems running on terminal 02 in the embodiment of the present application can include, but are not limited to, Android, GNU / Linux, and Windows.

[0072] In the embodiments of this specification, the terminal 02 and the server 01 may be connected directly or indirectly via wired or wireless communication, which is not limited in this application.

[0073] It should be noted that the following diagrams illustrate a possible sequence of steps and are not intended to be strictly followed. Some steps can be performed in parallel without relying on each other.

[0074] Specifically, Figure 2 FIG. 1 is a flow chart showing a data processing method according to an exemplary embodiment. Figure 2 As shown, the data processing method can be used in electronic devices such as servers, and can specifically include the following steps:

[0075] S201: Obtain target language description information constructed for a target distributed transaction.

[0076] In a specific embodiment, the target distributed transaction may refer to a distributed transaction currently to be processed. Specifically, the target distributed transaction may include a distributed transaction in a virtual resource interaction scenario.

[0077] In a specific embodiment, the target language description information can be used to describe transaction flow chart data based on the target domain language. The target language description information can be generated based on the transaction flow chart data corresponding to the target distributed transaction. Specifically, the target language description information can include node configuration description information corresponding to each of multiple target nodes. Optionally, the target domain language can include JavaScript Object Notation or Extensible Markup Language, etc.

[0078] In a specific embodiment, multiple target nodes may refer to the to-be-executed nodes included in the target distributed transaction. Any target node may correspond to a business operation to be executed. Specifically, the multiple target nodes may include multiple transaction nodes. Furthermore, the multiple transaction nodes may correspond to multiple transaction execution modes. Among them, the transaction execution mode of any transaction node may be used to characterize the transaction execution logic of any of the above-mentioned transaction nodes. Specifically, the transaction execution mode may include AT (Automatic Transaction) mode, TCC (Try-Confirm-Cancel) mode, compensation transaction mode, or best effort notification mode, etc.

[0079] In a specific embodiment, the node configuration description information corresponding to any target node can be used to describe the node configuration corresponding to any of the above-mentioned target nodes. The node configuration description information corresponding to any target node can include node type description information, execution resource description information and next node description information. Furthermore, in the case where the target node is a transaction node, the node configuration description information corresponding to the target node can also include execution mode description information. Among them, the node type description information corresponding to any target node can be used to indicate the node type of any of the above-mentioned target nodes. The execution resource description information corresponding to any of the above-mentioned target nodes can be used to indicate the execution resources adopted by any of the above-mentioned target nodes. The next node description information corresponding to any of the target nodes can be used to indicate the next node path corresponding to any of the above-mentioned target nodes. The execution mode description information corresponding to any of the target nodes can be used to indicate the transaction execution mode adopted by any of the above-mentioned target nodes.

[0080] In a specific embodiment, the target language description information can be obtained by:

[0081] Display the transaction arrangement page;

[0082] When the transaction flow chart data is acquired based on the node orchestration control and a description processing instruction corresponding to the target distributed transaction is detected, description processing is performed on the transaction flow chart data to obtain target language description information.

[0083] In a specific embodiment, a transaction orchestration page can be used to perform mixed orchestration of multiple target nodes corresponding to a target distributed transaction. The transaction orchestration page can include a node orchestration control. The node orchestration control can be used to orchestrate paths between the multiple target nodes and configure each target node. The node orchestration control can include a node selection control. The node selection control can be used to select a node and add the selected node to the orchestration area on the transaction orchestration page.

[0084] In a specific embodiment, the transaction orchestration page can be displayed through the orchestration terminal corresponding to the transaction orchestration demander. The transaction orchestration demander can be a user who needs to perform hybrid transaction orchestration. The orchestration terminal corresponding to the transaction orchestration demander can be a terminal used by the transaction orchestration demander during the transaction orchestration process.

[0085] In a specific embodiment, transaction flow graph data can be used to represent the transaction execution logic of a target distributed transaction. The transaction flow graph data can be obtained by performing a mixed-mode orchestration of multiple target nodes corresponding to the target distributed transaction based on the transaction execution logic of the target distributed transaction. The transaction flow graph data may include target flow graph data and target node attribute data corresponding to the multiple target nodes. The target flow graph data can be used to represent the logical relationship between the multiple target nodes; the target node attribute data corresponding to any target node can represent the node attributes of any of the aforementioned target nodes.

[0086] In a specific embodiment, the description processing instruction may be used to instruct to perform description processing on the transaction flow chart data. The description processing instruction may include data identification information corresponding to the transaction flow chart data.

[0087] In a specific embodiment, Figure 3 This is a schematic diagram showing a page display of a hybrid arrangement of a distributed transaction mode according to an exemplary embodiment; Figure 4 This is a schematic diagram of a page display of a mixed arrangement of transactions and non-transactions according to an exemplary embodiment. Specifically, Figure 3-Figure 4 As shown, the transaction orchestration demander can perform a node selection operation on the node selection control in the transaction orchestration page to add multiple target nodes to the orchestration area in the transaction orchestration page. Furthermore, the node selection control can display multiple different types of nodes to be selected, wherein the nodes to be selected can include the starting non-transaction node (such as Figure 3 Node "Start" in the Figure 3 Node "End") in the middle non-transaction node (such as Figure 3 Node "Task" in Figure 3Node "Choice" in the Figure 3 Node "Fail") in Figure 4 Node "Succeed") in the waiting node (such as Figure 4 Node "Wait" in the Figure 4 Node "Pass" in the Figure 3 Node "XABegin") in the transaction), end transaction node (such as Figure 3 Node "XAEnd") and intermediate transaction nodes (such as Figure 3 Node "XATask" in the node selection control); accordingly, any node to be selected in the node selection control can be dragged and dropped to add the above-mentioned node to the arrangement area.

[0088] In a specific embodiment, the transaction orchestration demander can perform a path marking operation on any two target nodes based on the transaction execution logic to implement the orchestration of the logic execution path between multiple target nodes and obtain the target flow chart data in the transaction flow chart data. For example, taking the interactive business scenario as an example, Figure 3 As shown, multiple transaction nodes may include a starting non-transaction node "Start", a starting transaction node "XABegin", an intermediate transaction node "Order", an intermediate transaction node "inventory", an ending transaction node "XAEnd" and an ending non-transaction node "End"; wherein the intermediate transaction node "Order" may be used to execute a transaction operation corresponding to an ordering service in an interactive business scenario; and the intermediate transaction node "inventory" may be used to execute a transaction operation corresponding to a shipping service in an interactive business scenario. In another example, as Figure 4 As shown, the non-transaction node "SecurityCheck" can be used to implement security detection; the non-transaction node "ReportLog" can be used to implement log reporting; the non-transaction node "SentEvent" can be used to implement event notification sending; the non-transaction node "PAStart" can be a parallel start node; the non-transaction node "PAEnd" can be a parallel end node; in addition, the transaction range line (such as Figure 4 The "XA" part in the dotted box) frames a single distributed transaction; Figure 4The distributed transaction "XA" in the example may include the starting transaction node "XABegin", the intermediate transaction node "CreateBill", the intermediate transaction node "Pay", the intermediate transaction node "Reduce" and the ending transaction node "XAEnd", wherein the intermediate transaction node "CreateBill" may be used to implement the creation of interactive credentials; the intermediate transaction node "Pay" may be used to perform virtual resource interactive operations; the intermediate transaction node "Reduce" may be used to perform the update operation of the number of interactive items; and the non-transaction node "QueryCountInfo" may be used to perform data query operations.

[0089] In a specific embodiment, Figure 5 FIG. 1 is a schematic diagram showing a node configuration in a hybrid orchestration process according to an exemplary embodiment. Specifically, Figure 5 As shown, the transaction orchestration demander can perform attribute configuration operations on each target node to obtain target node attribute data corresponding to each target node. Then, when the orchestration terminal corresponding to the transaction orchestration demander detects the data save instruction, it can generate transaction flow chart data based on the current target flow chart data and the target node attribute data corresponding to the above multiple target nodes. Further, the transaction orchestration demander can perform attribute configuration operations on each target node (such as Figure 5 The transaction orchestration requester can edit the node name to input the node identification information of the node to be configured; and the transaction orchestration requester can select a function in the function selection control to configure the execution resources of the node to be configured.

[0090] In a specific embodiment, when transaction flow graph data is acquired based on a node orchestration control and a description processing instruction corresponding to a target distributed transaction is detected, the transaction flow graph data can be described and processed based on the orchestration terminal corresponding to the transaction orchestration requester to obtain description information in the target language. Specifically, description processing can be performed on each target node based on the transaction flow graph data to obtain node configuration description information corresponding to each target node.

[0091] In the above embodiment, by displaying the transaction orchestration page, when the transaction flowchart data is obtained based on the node orchestration control and the description processing instruction corresponding to the target distributed transaction is detected, the transaction flowchart data is described and processed to obtain the target language description information, which can realize the visual hybrid orchestration of multiple transaction execution modes, and improve the readability and maintainability of the transaction orchestration through the target language description information, thereby reducing the programming complexity in the hybrid transaction orchestration process and improving the development efficiency to adapt to various different complex business scenarios.

[0092] S203: Parse the target language description information to obtain to-be-executed transaction data corresponding to the target distributed transaction.

[0093] In a specific embodiment, the pending transaction data can be used by a preset transaction execution engine to read and execute corresponding operations. The pending transaction data can include target node configuration data corresponding to each of multiple target nodes. Specifically, the pending transaction data can be DAG (Directed Acyclic Graph) structure data or state machine structure data.

[0094] In a specific embodiment, a parser can be loaded based on a preset description to parse the node configuration description information corresponding to each target node in the target language description information to obtain the target node configuration data corresponding to each target node; accordingly, the pending transaction data corresponding to the target distributed transaction can be obtained. The preset description loading parser can be used to parse the target language description information into pending transaction data.

[0095] In a specific embodiment, when the orchestration terminal corresponding to the transaction orchestration demander generates target language description information, the target language description information can be sent to the server; when the server receives the above target language description information, it can parse and process the target language description information to obtain pending transaction data corresponding to the target distributed transaction, and store the pending transaction data in the memory space, so that when the server receives the target transaction processing request corresponding to the target distributed transaction, the server can execute the operation corresponding to the above target distributed transaction based on the received target transaction processing request.

[0096] S205: When a target transaction processing request corresponding to a target distributed transaction is received, based on the preset transaction execution engine, the target transaction processing request and the node execution order corresponding to the transaction data to be executed, the current node configuration data corresponding to the current execution node among multiple target nodes are read in sequence from the transaction data to be executed, and based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, the distributed transaction operation corresponding to the current execution node is executed to obtain the target transaction processing result corresponding to the target distributed transaction.

[0097] In a specific embodiment, the target transaction processing request can be used to request execution of a business operation corresponding to the target distributed transaction. The target transaction processing request can be triggered by the target object through the target user terminal and sent to the server. The target transaction processing request can include the business data to be processed.

[0098] In a specific embodiment, the preset transaction execution engine can be used to execute corresponding business operations based on the pending transaction data. For example, taking the pending transaction data as DAG structure data as an example, the preset transaction execution engine can be a DAG executor.

[0099] In a specific embodiment, the node execution order corresponding to the pending transaction data can be used to indicate the executable logical path corresponding to the target distributed transaction. For example, the node execution order can be "node 1 → node 2 → node 3".

[0100] In a specific embodiment, the current execution node may refer to a node that currently needs to execute a corresponding business operation. Specifically, the current execution node may be a transaction node or a non-transaction node.

[0101] In a specific embodiment, the current node configuration data may refer to the target node configuration data corresponding to the current execution node in the to-be-executed transaction data.

[0102] In a specific embodiment, the current transaction execution mode corresponding to the current node configuration data may refer to the transaction execution mode of the current execution node indicated by the current node configuration data.

[0103] In a specific embodiment, the current execution resource corresponding to the current node configuration data may refer to the execution resource used by the current execution node indicated by the current node configuration data. Specifically, the current execution resource may include code to be executed, an interface to be executed, or a function to be executed.

[0104] In a specific embodiment, the target transaction processing result may refer to a processing result obtained by performing processing corresponding to the target distributed transaction on the target transaction processing request.

[0105] In a specific embodiment, when multiple transaction nodes correspond to a distributed transaction, the multiple transaction nodes may include multiple intermediate transaction nodes and an end transaction node. The end transaction node may refer to a transaction node that belongs to the distributed transaction and is located last among the multiple transaction nodes. The end transaction node may be used to generate a transaction processing result for the distributed transaction. The intermediate transaction node may refer to a node before the end transaction node among the multiple transaction nodes.

[0106] In a specific embodiment, the above step S205 may include:

[0107] Determine the current execution node based on the node execution order corresponding to the transaction data to be executed;

[0108] Read the current node configuration data corresponding to the current execution node from the transaction data to be executed, and execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resource corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, to obtain the current processing result corresponding to the current execution node;

[0109] If the current processing result indicates that the distributed transaction operation corresponding to the current execution node is successfully executed, the next execution node corresponding to the current execution node is determined based on the node execution order corresponding to the transaction data to be executed, and the current execution node is updated based on the next execution node;

[0110] Based on the updated current execution node, the current node configuration data corresponding to the current execution node is repeatedly read from the pending transaction data, and based on the current transaction execution mode and the current execution resource corresponding to the current node configuration data, the distributed transaction operation corresponding to the current execution node is executed to obtain the current processing result corresponding to the current execution node. Then, based on the next execution node, the transaction execution steps of the current execution node are updated until the current execution node becomes the end transaction node.

[0111] A target transaction processing result is generated based on the transaction processing results corresponding to the end transaction node and the multiple intermediate transaction nodes.

[0112] In a specific embodiment, the previous processing result corresponding to the current execution node may be a processing result obtained by processing the previous execution node of the current execution node.

[0113] In a specific embodiment, when the previous execution node is empty (i.e., the current execution node is determined for the first time), the first target node indicated by the node execution order can be used as the current execution node. Correspondingly, when the previous execution node is not empty, the next target node corresponding to the previous execution node indicated by the node execution order can be used as the current execution node. Specifically, the previous execution node can be the node among multiple target nodes that most recently executed a business operation before the current moment.

[0114] In a specific embodiment, when the current execution node is a transaction node, the preset transaction execution engine can read the current node configuration data corresponding to the current execution node from the transaction data to be executed, and based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, execute the distributed transaction operation corresponding to the current execution node to obtain the current processing result.

[0115] In a specific embodiment, based on the current transaction execution mode corresponding to the current node configuration data, the current execution resource corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, executing the distributed transaction operation corresponding to the current execution node to obtain the current processing result corresponding to the current execution node may include:

[0116] Based on the current transaction execution mode, determine the target execution resource from the current execution resources;

[0117] Based on the previous processing result, the target transaction operation corresponding to the target execution resource is executed to obtain the current processing result.

[0118] In a specific embodiment, the current execution resource may refer to an execution resource to be executed corresponding to the current execution node. The current execution resource may include at least one to-be-executed interface identifier.

[0119] In a specific embodiment, when the current transaction execution mode is AT mode, the current execution resource can be parsed and processed to obtain the anti-execution resource corresponding to the above-mentioned current execution resource; the current execution state corresponding to the current transaction execution mode can be determined; when the current execution state indicates that it is currently in the first stage, the above-mentioned current execution resource can be used as the target execution resource, and accordingly, based on the previous processing result, the business operation corresponding to the above-mentioned target execution resource can be executed to obtain the current execution result, and the anti-execution resource corresponding to the above-mentioned current execution resource can be stored. When the current execution state indicates that it is currently in the second stage, and the above-mentioned current execution result indicates that the business operation corresponding to the above-mentioned target execution resource is successfully executed, the above-mentioned current execution result can be used as the above-mentioned current processing result, and the anti-execution resource corresponding to the above-mentioned current execution resource can be deleted. Among them, the current execution state can be used to characterize the current execution situation corresponding to the current execution node.

[0120] In a specific embodiment, when the current transaction execution mode is the TCC mode, the current execution resources may include attempt execution resources, confirmation execution resources and cancellation execution resources; the current execution status corresponding to the current transaction execution mode can be determined; when the current execution status indicates that it is currently in the first stage, the attempt execution resources in the above-mentioned current execution resources can be used as the target execution resources, and accordingly, based on the previous processing result, the business operation corresponding to the above-mentioned target execution resource can be executed to obtain the current execution result; when the above-mentioned current execution result indicates that the business operation corresponding to the above-mentioned attempt execution resource is successfully executed, the business operation corresponding to the above-mentioned confirmation execution resource can be executed based on the above-mentioned current execution result to obtain the current processing result.

[0121] In a specific embodiment, when the current transaction execution mode is a compensation transaction mode, the current execution resources may include resources to be executed and compensation execution resources corresponding to the above-mentioned resources to be executed; the current execution status corresponding to the current transaction execution mode can be determined; when the current execution status indicates that it is currently in the first stage, the business operation corresponding to the above-mentioned resources to be executed can be executed based on the previous processing result to obtain the current processing result.

[0122] In a specific embodiment, when the current transaction execution mode is the best-effort notification mode, the current execution resource can be used as the target execution resource, and based on the previous processing result, the target transaction operation corresponding to the target execution resource is executed to obtain the current processing result.

[0123] In a specific embodiment, the above method may further include:

[0124] Get the target execution code language corresponding to the target distributed transaction;

[0125] Accordingly, the above-mentioned determination of the target execution resource from the current execution resources based on the current transaction execution mode may include:

[0126] Determine a target interface identifier from at least one to-be-executed interface identifier based on the current transaction execution mode;

[0127] Based on the target execution code language, a target execution resource is determined from a plurality of preset execution resources corresponding to the target interface identifier.

[0128] In a specific embodiment, the target execution code language can be used to represent the system operating environment currently executing the target distributed transaction. The target execution code language can include Java or Go.

[0129] In a specific embodiment, each of the plurality of preset execution resources may correspond to a preset execution code language.

[0130] In a specific embodiment, a target interface identifier can be determined from at least one to-be-executed interface identifier based on the current transaction execution mode and the current execution state. Specifically, when the current transaction execution mode is AT mode, the at least one to-be-executed interface identifier corresponding to the current transaction execution mode can be a to-be-executed interface identifier, and accordingly, the one to-be-executed interface identifier can be used as the target interface identifier. When the current transaction execution mode is TCC mode, the at least one to-be-executed interface identifier corresponding to the current transaction execution mode can include an attempted execution interface identifier, a confirmed execution interface identifier, and a canceled execution interface identifier, and accordingly, the attempted execution interface identifier can be used as the target interface identifier. When the current transaction execution mode is compensation transaction mode, the at least one to-be-executed interface identifier corresponding to the current transaction execution mode can include a to-be-executed interface identifier and a compensation execution interface identifier corresponding to the to-be-executed interface identifier, and accordingly, the to-be-executed interface identifier can be used as the target interface identifier. When the current transaction execution mode is best-effort notification mode, the at least one to-be-executed interface identifier corresponding to the current transaction execution mode can be a to-be-executed interface identifier, and accordingly, the one to-be-executed interface identifier can be used as the target interface identifier.

[0131] In a specific embodiment, a preset execution resource corresponding to the target execution code language may be selected from a plurality of preset execution resources corresponding to the target interface identifier as the target execution resource.

[0132] In the above embodiment, by determining the target interface identifier from at least one to-be-executed interface identifier based on the current transaction execution mode, and determining the target execution resource from multiple preset execution resources corresponding to the target interface identifier based on the target execution code language, the system can be adapted to a variety of different languages ​​and platforms, thereby improving the versatility and portability of hybrid transaction orchestration in different systems and environments.

[0133] In a specific embodiment, the preset transaction execution engine can repeatedly read the current node configuration data corresponding to the current execution node from the to-be-executed transaction data based on the updated current execution node, and execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode and current execution resources corresponding to the current node configuration data, thereby obtaining the current processing result corresponding to the current execution node, and then update the transaction execution steps of the current execution node based on the next execution node until the current execution node becomes the end transaction node. Accordingly, when the current execution node is the end transaction node, the transaction processing results corresponding to each of the above-mentioned multiple intermediate transaction nodes can be analyzed and processed based on the end transaction node to obtain the target transaction processing result corresponding to the above-mentioned distributed transaction.

[0134] In the above embodiment, the current execution node is determined based on the node execution order corresponding to the pending transaction data, the current node configuration data corresponding to the current execution node is read from the pending transaction data, and based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, the distributed transaction operation corresponding to the current execution node is executed to obtain the current processing result corresponding to the current execution node. If the current processing result indicates that the distributed transaction operation corresponding to the current execution node is successfully executed, the next execution node corresponding to the current execution node is determined based on the node execution order corresponding to the pending transaction data, and the current execution node is updated based on the next execution node. Based on the updated current execution node, the current node configuration data corresponding to the current execution node is repeatedly read from the transaction data to be executed, and based on the current transaction execution mode corresponding to the current node configuration data and the current execution resources corresponding to the current node configuration data, the distributed transaction operation corresponding to the current execution node is executed to obtain the current processing result corresponding to the current execution node. Based on the next execution node, the transaction execution steps of the current execution node are updated until the current execution node is the end transaction node. Based on the transaction processing results corresponding to the end transaction node and multiple intermediate transaction nodes, the target transaction processing result is generated. This can achieve accurate execution of distributed transactions in a hybrid mode and data consistency of distributed transaction processing results in a hybrid mode.

[0135] In a specific embodiment, the above method may further include:

[0136] When the current processing result indicates that the distributed transaction operation corresponding to the current execution node is executed abnormally, based on the current transaction execution mode and the current execution resource, the rollback execution resource corresponding to the current execution node is determined, and the rollback transaction operation corresponding to the rollback execution resource is executed to obtain the current rollback processing result corresponding to the current execution node;

[0137] Determine the previous execution node corresponding to the current execution node based on the node execution order corresponding to the transaction data to be executed;

[0138] Based on the previous execution node, the current execution node is updated, and based on the updated current execution node, the rollback execution resource corresponding to the current execution node is repeatedly determined based on the current transaction execution mode and the current execution resource, and the rollback transaction operation corresponding to the rollback execution resource is executed to obtain the current rollback processing result corresponding to the current execution node, and then based on the previous execution node, the abnormal rollback step of the current execution node is updated, until the current execution node is the starting transaction node among multiple transaction nodes, and the target transaction processing result is generated based on the rollback processing results corresponding to the rolled back nodes among the multiple transaction nodes.

[0139] In a specific embodiment, the fallback execution resource may refer to a resource that needs to be executed when an exception occurs during the execution of an operation by the current execution node.

[0140] In a specific embodiment, the current rollback processing result may refer to the processing result obtained by the current execution node executing the rollback transaction operation.

[0141] In a specific embodiment, when the current processing result indicates that the distributed transaction operation corresponding to the current execution node is executed abnormally and the current transaction execution mode is AT mode, the reverse execution resource corresponding to the above-mentioned current execution resource can be read as the rollback execution resource corresponding to the above-mentioned current execution node; based on the current processing result, the rollback transaction operation corresponding to the above-mentioned reverse execution resource can be executed to obtain the current rollback processing result corresponding to the current execution node.

[0142] In a specific embodiment, when the current processing result indicates that the distributed transaction operation corresponding to the current execution node is executed abnormally and the current transaction execution mode is the TCC mode, the rollback transaction operation corresponding to the cancel execution resource in the current execution resource can be executed based on the current processing result to obtain the current rollback processing result corresponding to the current execution node. Specifically, when the above-mentioned current execution result indicates that the business operation corresponding to the above-mentioned attempted execution resource has failed to execute, the rollback transaction operation corresponding to the cancel execution resource in the current execution resource can be executed based on the above-mentioned current execution result to obtain the current rollback processing result corresponding to the current execution node.

[0143] In a specific embodiment, when the current processing result indicates that the distributed transaction operation corresponding to the current execution node is executed abnormally and the current transaction execution mode is the compensation transaction mode, the rollback transaction operation corresponding to the compensation execution resource in the current execution resource can be executed based on the current processing result to obtain the current rollback processing result corresponding to the current execution node.

[0144] In a specific embodiment, the rolled-back node may refer to a transaction node that has executed a rollback transaction operation among multiple transaction nodes. The rolled-back node may include at least one transaction node among the multiple transaction nodes.

[0145] Exemplarily, taking multiple transaction nodes including transaction node 1, transaction node 2, transaction node 3, transaction node 4 and transaction node 5 as an example, assuming that the execution order of the above multiple transaction nodes is "transaction node 1 → transaction node 2 → transaction node 3 → transaction node 4 → transaction node 5", and when the current execution node is transaction node 3, the current processing result indicates that the distributed transaction operation corresponding to the current execution node is executed abnormally, the fallback execution resource of transaction node 3 can be determined based on the transaction execution mode and corresponding execution resources of transaction node 3, and based on the processing result of transaction node 3, the fallback transaction operation corresponding to the fallback execution resource of transaction node 3 is executed to obtain the fallback processing result corresponding to transaction node 3; based on the above node execution order, it can be determined that the previous execution node "transaction node 2" is the current execution node, and then based on the transaction execution mode and corresponding execution resources of transaction node 2, it can be determined that the current execution node The rollback execution resource of transaction node 2 is determined, and based on the processing result of transaction node 3, the rollback transaction operation corresponding to the rollback execution resource of transaction node 2 is executed to obtain the rollback processing result corresponding to transaction node 2; then, based on the above-mentioned node execution order, the previous execution node "transaction node 1" can be determined as the current execution node, and based on the transaction execution mode and corresponding execution resources of transaction node 1, the rollback execution resource of transaction node 1 is determined, and based on the processing result of transaction node 2, the rollback transaction operation corresponding to the rollback execution resource of transaction node 1 is executed to obtain the rollback processing result corresponding to transaction node 1; then, when the current execution node "transaction node 1" is the starting transaction node among multiple transaction nodes, the target transaction processing result is generated based on the rollback processing results corresponding to the rolled back nodes (i.e., "transaction node 1", "transaction node 2" and "transaction node 3") among the multiple transaction nodes.

[0146] In a specific embodiment, the multiple target nodes may further include multiple non-transactional nodes. The multiple non-transactional nodes may include intermediate non-transactional nodes and end non-transactional nodes. The end non-transactional node may refer to the last node in the node execution order among the multiple target nodes. The end non-transactional node may be used to generate a target transaction processing result. The intermediate non-transactional node may refer to a node among the multiple non-transactional nodes other than the end non-transactional node.

[0147] In the above embodiment, when the current processing result indicates that the distributed transaction operation corresponding to the current execution node has been executed abnormally, the rollback execution resource corresponding to the current execution node is determined based on the current transaction execution mode and the current execution resource, and the rollback transaction operation corresponding to the rollback execution resource is executed to obtain the current rollback processing result corresponding to the current execution node; the previous execution node corresponding to the current execution node is determined based on the node execution order corresponding to the transaction data to be executed; the current execution node is updated based on the previous execution node; and based on the updated current execution node, the steps of determining the rollback execution resource corresponding to the current execution node based on the current transaction execution mode and the current execution resource, and executing the rollback transaction operation corresponding to the rollback execution resource are repeated to obtain the current rollback processing result corresponding to the current execution node, and then updating the abnormal rollback step of the current execution node based on the previous execution node, until the current execution node is the starting transaction node among multiple transaction nodes, and the target transaction processing result is generated based on the rollback processing results corresponding to the rolled back nodes among the multiple transaction nodes. This can achieve accurate rollback of distributed transactions in a hybrid mode, and ensure correct execution of the transaction process and data consistency.

[0148] In a specific embodiment, based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, executing the distributed transaction operation corresponding to the current execution node to obtain the target transaction processing result corresponding to the target distributed transaction may include:

[0149] When the current execution node is a transaction node, based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, the distributed transaction operation corresponding to the current execution node is executed to obtain the current transaction processing result corresponding to the current execution node;

[0150] If the current execution node is a non-transactional node, based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, the non-transactional operation corresponding to the current execution node is executed to obtain the non-transactional processing result corresponding to the current execution node;

[0151] A target transaction processing result is generated based on the transaction processing results corresponding to the ended non-transaction nodes, the executed transaction nodes, and the non-transaction processing results corresponding to the executed non-transaction nodes.

[0152] In a specific embodiment, the current transaction processing result may refer to a processing result obtained by the current execution node executing the corresponding transaction operation when the current execution node is a transaction node.

[0153] In a specific embodiment, when the current execution node is a transaction node, the execution process of the distributed transaction operation of the current execution node can refer to the specific execution process of the above-mentioned step S205 when multiple transaction nodes correspond to one distributed transaction, which will not be repeated in this disclosure.

[0154] In a specific embodiment, the non-transactional processing result corresponding to the current execution node may refer to a processing result obtained by executing a corresponding non-transactional operation when the current execution node is a non-transactional node.

[0155] In a specific embodiment, based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, executing the non-transactional operation corresponding to the current execution node to obtain the non-transactional processing result corresponding to the current execution node may include:

[0156] When the previous execution node of the current execution node is a non-transactional node, based on the current execution resources corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, the non-transactional operation corresponding to the current execution node is executed to obtain the non-transactional processing result corresponding to the current execution node.

[0157] In a specific embodiment, when the previous execution node of the current execution node is a non-transactional node, the non-transactional operation corresponding to the current execution resource can be executed based on the previous processing result corresponding to the current execution node to obtain the non-transactional processing result corresponding to the current execution node.

[0158] In a specific embodiment, based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, executing the non-transactional operation corresponding to the current execution node to obtain the non-transactional processing result corresponding to the current execution node may include:

[0159] When the previous execution node of the current execution node is a transaction node and the previous processing result indicates that the distributed transaction operation corresponding to the previous execution node is successfully executed, the non-transactional operation corresponding to the current execution node is executed based on the current execution resources and the previous processing result corresponding to the current node configuration data to obtain the non-transactional processing result corresponding to the current execution node.

[0160] In a specific embodiment, when the previous execution node of the current execution node is a transaction node and the previous processing result indicates that the distributed transaction operation corresponding to the previous execution node was successfully executed, the non-transactional operation corresponding to the current execution resource can be executed based on the previous processing result corresponding to the current execution node to obtain the non-transactional processing result corresponding to the current execution node. It is understandable that when the previous execution node of the current execution node is a transaction node and the previous processing result indicates that the distributed transaction operation corresponding to the previous execution node was executed abnormally, the previous execution node can execute the corresponding rollback transaction operation, and the process may not reach the above-mentioned current execution node, that is, the above-mentioned current execution node does not execute the operation.

[0161] In a specific embodiment, the plurality of non-transaction nodes may further include a branch node. Accordingly, the non-transaction processing result may include a branch processing result. The branch node may be used to implement jump selections for multiple paths.

[0162] In a specific embodiment, when the current execution node is a non-transactional node, executing the non-transactional operation corresponding to the current execution node based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node to obtain the non-transactional processing result corresponding to the current execution node may include:

[0163] When the current execution node is a branch node, the current node configuration data corresponding to the branch node is read to obtain the preset branch condition corresponding to the branch node, and based on the previous processing result corresponding to the current execution node, the preset branch condition and the node execution order corresponding to the transaction data to be executed, the branch processing operation corresponding to the current execution node is executed to obtain the branch processing result.

[0164] In a specific embodiment, the branch processing result may be used to indicate the next execution node corresponding to the current execution node.

[0165] In a specific embodiment, the preset branch condition may include multiple preset comparison conditions and preset branch paths corresponding to each preset comparison condition. Among them, the preset branch path corresponding to the preset comparison condition may refer to a branch path selected when the above-mentioned preset comparison condition is met. Specifically, when the current execution node is a branch node, the current node configuration data corresponding to the branch node is read to obtain the preset branch condition corresponding to the branch node; accordingly, the previous processing result and the preset comparison condition can be compared to obtain a branch comparison result; when the above-mentioned branch comparison result indicates that the above-mentioned previous processing result meets any preset comparison condition, the branch processing result can be generated based on the preset branch path corresponding to any preset comparison condition met. Exemplarily, assuming that multiple preset comparison conditions include a first comparison condition and a second comparison condition, and multiple preset branch paths include a first branch path corresponding to the first comparison condition and a second branch path corresponding to the second comparison condition, when the previous processing result meets the first comparison condition, the branch processing result can be generated based on the first branch path; when the previous processing result meets the second comparison condition, the branch processing result can be generated based on the second branch path.

[0166] In a specific embodiment, the executed transaction node may refer to a node where multiple transaction nodes have executed corresponding distributed transaction operations. The executed transaction node may include at least one transaction node.

[0167] In a specific embodiment, an executed non-transaction node may refer to a node among multiple non-transaction nodes that has executed a corresponding non-transaction operation. The executed non-transaction node may include at least one non-transaction node.

[0168] In a specific embodiment, when the current execution node is a terminating non-transactional node, the terminating non-transactional node may generate a target transaction processing result based on the transaction processing results generated by the terminating transactional node and the non-transactional results generated by the executed non-transactional nodes. Specifically, the terminating non-transactional node may analyze the transaction processing results generated by the terminating transactional node and the non-transactional results generated by the executed non-transactional nodes to obtain the target transaction processing result.

[0169] In a specific embodiment, the multiple target nodes may further include a combination node and an end non-transaction node. The combination node may include at least one of a transaction subnode and a non-transaction subnode. Specifically, the transaction orchestration requester may first perform a node selection operation on the node selection control on the transaction orchestration page to add multiple nodes to be combined to the orchestration area on the transaction orchestration page; then, the transaction orchestration requester may perform an attribute configuration operation on each node to be combined to obtain node attribute data corresponding to each node to be combined; and then, the transaction orchestration requester may perform a node combination operation on the multiple nodes to be combined to obtain the attribute data of the combined node and the target node corresponding to the combined node.

[0170] In a specific embodiment, based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, executing the distributed transaction operation corresponding to the current execution node to obtain the target transaction processing result corresponding to the target distributed transaction may include:

[0171] When the current execution node is a transaction node, based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, the distributed transaction operation corresponding to the current execution node is executed to obtain the current transaction processing result corresponding to the current execution node;

[0172] In the case where the current execution node is a combination node, based on the combination node configuration data corresponding to the combination node in the transaction data to be executed, the combination transaction operation corresponding to the combination node is executed to obtain the combination processing result corresponding to the combination node;

[0173] Generate a target transaction processing result based on the transaction processing results corresponding to the ended non-transaction nodes, the executed transaction nodes, and the combined processing results.

[0174] In a specific embodiment, when the current execution node is a transaction node, the execution process of the distributed transaction operation of the current execution node can refer to the specific execution process of the above-mentioned step S205 when multiple transaction nodes correspond to one distributed transaction, which will not be repeated in this disclosure.

[0175] In a specific embodiment, the combined processing result corresponding to the combined node may refer to a result obtained by processing the previous processing result based on the combined node.

[0176] In a specific embodiment, when the current execution node is a combination node, the combination node configuration data corresponding to the above combination node can be read from the transaction data to be executed; then, based on the above combination node configuration data, the combination node is expanded and processed to obtain the sub-node execution order of multiple combination sub-nodes corresponding to the above combination node and the sub-node configuration data corresponding to each combination sub-node; then, based on the sub-node execution order of multiple combination sub-nodes, the current execution sub-node can be determined, the sub-node configuration data corresponding to the above current execution sub-node can be read, and based on the execution resources corresponding to the sub-node configuration data of the above current execution sub-node and the previous processing result of the above current execution sub-node, the sub-node operation corresponding to the current combination sub-node is executed to obtain the current sub-node processing result; then, based on the above sub-node execution order, the current execution sub-node can be updated, and based on the updated current execution sub-node, the process returns to the above step of reading the sub-node configuration data corresponding to the above current execution sub-node, until the current combination sub-node is the end sub-node in the above combination sub-node, and accordingly, the current sub-node processing result corresponding to the end sub-node can be used as the combination processing result corresponding to the combination node.

[0177] In the above embodiment, when the current execution node is a combination node, based on the combination node configuration data corresponding to the combination node in the transaction data to be executed, the combination transaction operation corresponding to the combination node is executed to obtain the combination processing result corresponding to the combination node. Based on the transaction processing results corresponding to the end non-transaction node and the executed transaction node and the combination processing result, the target transaction processing result is generated. Complex logic can be simplified through the combination node, and development efficiency can be improved through the reuse of the combination node.

[0178] In a specific embodiment, Figure 6 FIG. 1 is a schematic diagram of a hybrid orchestration execution logic according to an exemplary embodiment. Specifically, Figure 6 As shown, the above-mentioned multiple target nodes may include a combination node (such as Figure 6 A plurality of transaction nodes and a plurality of non-transaction nodes; wherein the plurality of non-transaction nodes may include a plurality of intermediate non-transaction nodes (such as Figure 6 Node "A", node "B", node "C", node "D", node "E", node "F" and node "G") in ), parallel starting nodes (such as Figure 6 middle node "parallel begin"), parallel end node (such as Figure 6 Middle node "parallelend"), starting non-transaction node (such as Figure 6 Node "begin" in the Figure 6 middle node "end") and branch nodes (such as Figure 6Node "if" in ); multiple transaction nodes may include a starting transaction node (such as Figure 6 Middle node "tx_begin"), intermediate transaction node (such as Figure 6 Middle node "M") and end transaction node (such as Figure 6 The start transaction node can be used to register the corresponding pending transaction; the parallel start node can be used to register the parallel path to be executed.

[0179] In a specific embodiment, Figure 6 As shown, taking node "B" as an example, when the current execution node is node "B", the parameter processing process related to the operation corresponding to the execution resource can be advanced, that is, the parameters are pre-processed first (such as Figure 6 "node_pre" in the input parameter conversion), and then bind the pre-processing result with the to-be-executed parameter in the execution resource. Then, the operation corresponding to the current execution resource can be executed. After obtaining the processing result, the above processing result is processed and the result after the parameter processing is used as the current processing result, that is, the result extraction post-processing required by the subsequent branch (such as Figure 6 This allows for separation of the changing and unchanging parts. The unchanging part is the functional logic, allowing nodes to be reused in different graphs or locations without any path awareness. It should be noted that any of the multiple target nodes can be reused through the aforementioned parameter pre- and post-processing methods.

[0180] In the above embodiment, by obtaining the target language description information constructed for the target distributed transaction, the target language description information is generated based on the transaction flow chart data corresponding to the target distributed transaction, and the transaction flow chart data is obtained by performing mode mixed arrangement of multiple target nodes corresponding to the target distributed transaction based on the transaction execution logic of the target distributed transaction. The multiple target nodes include multiple transaction nodes, and the multiple transaction nodes correspond to multiple transaction execution modes. Visual mixed arrangement of multiple transaction execution modes can be achieved, and the readability and maintainability of the transaction arrangement are improved through the target language description information, thereby reducing the programming complexity in the mixed transaction arrangement process and improving the development efficiency to adapt to various different complex business scenarios. The target language description information is then parsed and processed to obtain the to-be-executed transaction corresponding to the target distributed transaction. Then, when receiving the target transaction processing request corresponding to the target distributed transaction, based on the preset transaction execution engine, the target transaction processing request and the node execution order corresponding to the transaction data to be executed, the current node configuration data corresponding to the current execution node in multiple target nodes are read from the transaction data to be executed in turn, and based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, the distributed transaction operation corresponding to the current execution node is executed to obtain the target transaction processing result corresponding to the target distributed transaction, which can realize hybrid orchestration of distributed transaction processing, thereby making it easier to realize distributed services for various complex distributed business scenarios, support complex transaction processes, and improve development efficiency.

[0181] Figure 7 FIG. 1 is a block diagram of a data processing device according to an exemplary embodiment. Specifically, Figure 7 As shown, the device may include:

[0182] Description acquisition module 710 may be used to acquire target language description information constructed for a target distributed transaction. The target language description information is generated based on transaction flow chart data corresponding to the target distributed transaction. The transaction flow chart data is obtained by performing mixed mode arrangement on multiple target nodes corresponding to the target distributed transaction based on the transaction execution logic of the target distributed transaction. The multiple target nodes include multiple transaction nodes, and the multiple transaction nodes correspond to multiple transaction execution modes.

[0183] The parsing module 720 can be used to parse the target language description information to obtain the pending transaction data corresponding to the target distributed transaction;

[0184] The execution module 730 can be used to, upon receiving a target transaction processing request corresponding to a target distributed transaction, sequentially read the current node configuration data corresponding to the current execution node among multiple target nodes from the to-be-executed transaction data based on a preset transaction execution engine, the target transaction processing request, and the node execution order corresponding to the to-be-executed transaction data, and execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, to obtain the target transaction processing result corresponding to the target distributed transaction.

[0185] In a specific embodiment, the execution module 730 may include:

[0186] The first node determination module may be used to determine the current execution node based on the node execution order corresponding to the transaction data to be executed;

[0187] The first execution module may be configured to read the current node configuration data corresponding to the current execution node from the transaction data to be executed, and execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, to obtain the current processing result corresponding to the current execution node; the previous processing result corresponding to the current execution node is the processing result obtained by the previous execution node of the current execution node;

[0188] The first node update module may be configured to determine the next execution node corresponding to the current execution node based on the node execution order corresponding to the to-be-executed transaction data when the current processing result indicates that the distributed transaction operation corresponding to the current execution node is successfully executed, and update the current execution node based on the next execution node;

[0189] The second execution module may be configured to repeatedly read the current node configuration data corresponding to the current execution node from the to-be-executed transaction data based on the updated current execution node, and execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode and the current execution resource corresponding to the current node configuration data, obtain the current processing result corresponding to the current execution node, and update the transaction execution step of the current execution node based on the next execution node until the current execution node becomes the end transaction node;

[0190] The first result generating module may be configured to generate a target transaction processing result based on the transaction processing results corresponding to the end transaction node and the plurality of intermediate transaction nodes.

[0191] In a specific embodiment, the above device may further include:

[0192] The rollback execution module can be used to determine the rollback execution resource corresponding to the current execution node based on the current transaction execution mode and the current execution resource when the current processing result indicates that the distributed transaction operation corresponding to the current execution node has been executed abnormally, and execute the rollback transaction operation corresponding to the rollback execution resource to obtain the current rollback processing result corresponding to the current execution node;

[0193] The second node determination module may be used to determine the previous execution node corresponding to the current execution node based on the node execution order corresponding to the transaction data to be executed;

[0194] The third execution module can be used to update the current execution node based on the previous execution node, and based on the updated current execution node, repeatedly determine the rollback execution resource corresponding to the current execution node based on the current transaction execution mode and the current execution resource, and execute the rollback transaction operation corresponding to the rollback execution resource to obtain the current rollback processing result corresponding to the current execution node, and update the abnormal rollback step of the current execution node based on the previous execution node, until the current execution node is the starting transaction node among multiple transaction nodes, and the target transaction processing result is generated based on the rollback processing result corresponding to the rolled back nodes among the multiple transaction nodes; the rolled back nodes are nodes among the multiple transaction nodes on which the rollback transaction operation has been executed.

[0195] In a specific embodiment, the first execution module may include:

[0196] An execution resource determination module may be used to determine a target execution resource from current execution resources based on the current transaction execution mode;

[0197] The fourth execution module can be used to execute the target transaction operation corresponding to the target execution resource based on the previous processing result to obtain the current processing result.

[0198] In a specific embodiment, the above device may further include:

[0199] The target language acquisition module can be used to obtain the target execution code language corresponding to the target distributed transaction;

[0200] Accordingly, the execution resource determination module may include:

[0201] The identifier determination module may be configured to determine a target interface identifier from at least one to-be-executed interface identifier based on a current transaction execution mode;

[0202] The target resource determination module can be used to determine the target execution resource from multiple preset execution resources corresponding to the target interface identifier based on the target execution code language; each preset execution resource in the multiple preset execution resources corresponds to a preset execution code language.

[0203] In a specific embodiment, the execution module 730 may include:

[0204] A fifth execution module may be configured to, when the current execution node is a transaction node, execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, and obtain the current transaction processing result corresponding to the current execution node;

[0205] a sixth execution module, configured to, when the current execution node is a non-transactional node, execute the non-transactional operation corresponding to the current execution node based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, and obtain the non-transactional processing result corresponding to the current execution node;

[0206] The second result generation module can be used to generate a target transaction processing result based on the transaction processing results corresponding to the ended non-transaction node, the executed transaction node, and the non-transaction processing results corresponding to the executed non-transaction node.

[0207] In a specific embodiment, the sixth execution module may include:

[0208] The seventh execution module can be used to execute the non-transactional operation corresponding to the current execution node based on the current execution resources corresponding to the current node configuration data and the previous processing result corresponding to the current execution node when the previous execution node of the current execution node is a non-transactional node, and obtain the non-transactional processing result corresponding to the current execution node.

[0209] In a specific embodiment, the sixth execution module may include:

[0210] The eighth execution module can be used to execute the non-transactional operation corresponding to the current execution node based on the current execution resources corresponding to the current node configuration data and the previous processing result, when the previous execution node of the current execution node is a transaction node and the previous processing result indicates that the distributed transaction operation corresponding to the previous execution node is successfully executed, to obtain the non-transactional processing result corresponding to the current execution node.

[0211] In a specific embodiment, the sixth execution module may include:

[0212] The branch execution module can be used to read the current node configuration data corresponding to the branch node when the current execution node is a branch node, obtain the preset branch condition corresponding to the branch node, and execute the branch processing operation corresponding to the current execution node based on the previous processing result corresponding to the current execution node, the preset branch condition and the node execution order corresponding to the transaction data to be executed, to obtain the branch processing result; the branch processing result is used to indicate the next execution node corresponding to the current execution node.

[0213] In a specific embodiment, the execution module 730 may include:

[0214] A ninth execution module may be configured to, when the current execution node is a transaction node, execute the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, and obtain the current transaction processing result corresponding to the current execution node;

[0215] The combination execution module can be used to execute the combination transaction operation corresponding to the combination node based on the combination node configuration data corresponding to the combination node in the transaction data to be executed when the current execution node is a combination node, and obtain the combination processing result corresponding to the combination node;

[0216] The third result generation module can be used to generate a target transaction processing result based on the transaction processing results corresponding to the ended non-transaction node and the executed transaction node and the combined processing result.

[0217] In a specific embodiment, the above device may further include:

[0218] The display module can be used to display the transaction orchestration page, which includes the node orchestration control;

[0219] The description processing module can be used to obtain transaction flow chart data based on the node orchestration control and detect the description processing instruction corresponding to the target distributed transaction, and then perform description processing on the transaction flow chart data to obtain description information in the target language.

[0220] Regarding the apparatus in the above embodiment, the specific manner in which each module and unit performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0221] Figure 8 This is a block diagram of an electronic device for processing a target distributed transaction according to an exemplary embodiment. The electronic device may be a server, and its internal structure diagram may be as shown in FIG. Figure 8As shown. The electronic device includes a processor, a memory, and a network interface connected via a system bus. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a data processing method is implemented.

[0222] Figure 9 is a block diagram of another electronic device for processing target distributed transactions according to an exemplary embodiment. The electronic device may be a terminal, and its internal structure diagram may be as shown in FIG. Figure 9 As shown. The electronic device includes a processor, a memory, a network interface, a display screen and an input device connected via a system bus. The processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a data processing method is implemented. The display screen of the electronic device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic device can be a touch layer covering the display screen, or a button, trackball or touchpad provided on the housing of the electronic device, or an external keyboard, touchpad or mouse, etc.

[0223] Those skilled in the art will understand that Figure 8 or Figure 9 The structure shown in the figure is only a block diagram of a part of the structure related to the scheme of the present disclosure, and does not constitute a limitation on the electronic device to which the scheme of the present disclosure is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0224] In an exemplary embodiment, an electronic device is further provided, including: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the data processing method in the embodiment of the present disclosure.

[0225] In an exemplary embodiment, a computer-readable storage medium is further provided. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the data processing method in the embodiment of the present disclosure.

[0226] In an exemplary embodiment, a computer program product containing instructions is also provided. When the computer program product is run on a computer, the computer is caused to execute the data processing method in the embodiment of the present disclosure.

[0227] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, which can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0228] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0229] It is understandable that in the specific implementation of this application, related data such as user information is involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0230] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0231] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A data processing method, characterized in that: The method comprises: Obtaining target language description information constructed for a target distributed transaction, the target language description information being generated based on transaction flow chart data corresponding to the target distributed transaction, the transaction flow chart data being obtained by performing mixed-mode arrangement on multiple target nodes corresponding to the target distributed transaction based on transaction execution logic of the target distributed transaction, the multiple target nodes including multiple transaction nodes corresponding to multiple transaction execution modes; Parsing the target language description information to obtain to-be-executed transaction data corresponding to the target distributed transaction; Upon receiving a target transaction processing request corresponding to the target distributed transaction, based on a preset transaction execution engine, the target transaction processing request, and the node execution order corresponding to the to-be-executed transaction data, the current node configuration data corresponding to the current execution node among the multiple target nodes is read in sequence from the to-be-executed transaction data, and based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, the distributed transaction operation corresponding to the current execution node is executed to obtain a target transaction processing result corresponding to the target distributed transaction.

2. The method according to claim 1, characterized in that In a case where the multiple transaction nodes correspond to one distributed transaction, the multiple transaction nodes include multiple intermediate transaction nodes and an end transaction node. Based on a preset transaction execution engine, the target transaction processing request, and the node execution order corresponding to the to-be-executed transaction data, the current node configuration data corresponding to the current execution node among the multiple target nodes is sequentially read from the to-be-executed transaction data, and based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data, the distributed transaction operation corresponding to the current execution node is executed to obtain a target transaction processing result corresponding to the target distributed transaction, including: Determining a current execution node based on a node execution order corresponding to the transaction data to be executed; Reading current node configuration data corresponding to the current execution node from the to-be-executed transaction data, and executing the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, to obtain a current processing result corresponding to the current execution node; the previous processing result corresponding to the current execution node is a processing result obtained by the previous execution node of the current execution node; If the current processing result indicates that the distributed transaction operation corresponding to the current execution node is successfully executed, determining the next execution node corresponding to the current execution node based on the node execution order corresponding to the to-be-executed transaction data, and updating the current execution node based on the next execution node; Based on the updated current execution node, repeating the steps of reading the current node configuration data corresponding to the current execution node from the to-be-executed transaction data, and executing the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode and the current execution resource corresponding to the current node configuration data, obtaining the current processing result corresponding to the current execution node, and then updating the transaction execution step of the current execution node based on the next execution node, until the current execution node becomes the end transaction node; The target transaction processing result is generated based on the transaction processing results corresponding to the end transaction node and the multiple intermediate transaction nodes.

3. The method according to claim 2, characterized in that The method further comprises: If the current processing result indicates that the distributed transaction operation corresponding to the current execution node is executed abnormally, determining a rollback execution resource corresponding to the current execution node based on the current transaction execution mode and the current execution resource, and executing a rollback transaction operation corresponding to the rollback execution resource to obtain a current rollback processing result corresponding to the current execution node; Determining a previous execution node corresponding to the current execution node based on a node execution order corresponding to the to-be-executed transaction data; Based on the previous execution node, the current execution node is updated, and based on the updated current execution node, the steps of determining the rollback execution resource corresponding to the current execution node based on the current transaction execution mode and the current execution resource, and executing the rollback transaction operation corresponding to the rollback execution resource are repeated to obtain the current rollback processing result corresponding to the current execution node, and then the abnormal rollback step of updating the current execution node based on the previous execution node is performed until the current execution node is the starting transaction node among the multiple transaction nodes, and the target transaction processing result is generated based on the rollback processing result corresponding to the rolled back nodes among the multiple transaction nodes; the rolled back nodes are nodes among the multiple transaction nodes on which the rollback transaction operation has been executed.

4. The method according to claim 2, characterized in that The step of executing the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data, the current execution resource corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node to obtain the current processing result corresponding to the current execution node includes: Determining a target execution resource from the current execution resources based on the current transaction execution mode; Based on the previous processing result, the target transaction operation corresponding to the target execution resource is executed to obtain the current processing result.

5. The method according to claim 4, characterized in that The currently executed resource includes at least one to-be-executed interface identifier, and the method further includes: Obtaining a target execution code language corresponding to the target distributed transaction; The determining the target execution resource from the current execution resources based on the current transaction execution mode includes: Based on the current transaction execution mode, determining a target interface identifier from the at least one to-be-executed interface identifier; Based on the target execution code language, the target execution resource is determined from a plurality of preset execution resources corresponding to the target interface identifier; each preset execution resource in the plurality of preset execution resources corresponds to a preset execution code language.

6. The method according to claim 1, characterized in that The multiple target nodes further include multiple non-transaction nodes, and the multiple non-transaction nodes include intermediate non-transaction nodes and end non-transaction nodes; executing the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data to obtain the target transaction processing result corresponding to the target distributed transaction includes: If the current execution node is a transaction node, based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, the distributed transaction operation corresponding to the current execution node is executed to obtain the current transaction processing result corresponding to the current execution node; If the current execution node is a non-transactional node, based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, execute the non-transactional operation corresponding to the current execution node to obtain the non-transactional processing result corresponding to the current execution node; The target transaction processing result is generated based on the ended non-transaction node, the transaction processing results corresponding to the executed transaction nodes, and the non-transaction processing results corresponding to the executed non-transaction nodes.

7. The method according to claim 6, characterized in that The performing, based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, a non-transactional operation corresponding to the current execution node to obtain the non-transactional processing result corresponding to the current execution node includes: In a case where the previous execution node of the current execution node is a non-transactional node, based on the current execution resources corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, the non-transactional operation corresponding to the current execution node is executed to obtain the non-transactional processing result corresponding to the current execution node.

8. The method according to claim 6, characterized in that The performing, based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, a non-transactional operation corresponding to the current execution node to obtain the non-transactional processing result corresponding to the current execution node includes: If the previous execution node of the current execution node is a transaction node and the previous processing result indicates that the distributed transaction operation corresponding to the previous execution node is successfully executed, based on the current execution resources corresponding to the current node configuration data and the previous processing result, the non-transactional operation corresponding to the current execution node is executed to obtain the non-transactional processing result corresponding to the current execution node.

9. The method according to claim 6, characterized in that The multiple non-transactional nodes further include branch nodes, and the non-transactional processing result includes a branch processing result; when the current execution node is a non-transactional node, executing the non-transactional operation corresponding to the current execution node based on the current execution resource corresponding to the current node configuration data and the previous processing result corresponding to the current execution node, to obtain the non-transactional processing result corresponding to the current execution node, including: In the case where the current execution node is a branch node, the current node configuration data corresponding to the branch node is read to obtain the preset branch condition corresponding to the branch node, and based on the previous processing result corresponding to the current execution node, the preset branch condition and the node execution order corresponding to the transaction data to be executed, the branch processing operation corresponding to the current execution node is executed to obtain a branch processing result; the branch processing result is used to indicate the next execution node corresponding to the current execution node.

10. The method according to claim 1, characterized in that The multiple target nodes further include a combination node and an end non-transaction node, the combination node including at least one of a transaction sub-node and a non-transaction sub-node; the executing the distributed transaction operation corresponding to the current execution node based on the current transaction execution mode corresponding to the current node configuration data and the current execution resource corresponding to the current node configuration data to obtain a target transaction processing result corresponding to the target distributed transaction includes: If the current execution node is a transaction node, based on the current transaction execution mode corresponding to the current node configuration data, the current execution resources corresponding to the current node configuration data, and the previous processing result corresponding to the current execution node, the distributed transaction operation corresponding to the current execution node is executed to obtain the current transaction processing result corresponding to the current execution node; In a case where the current execution node is a combination node, based on the combination node configuration data corresponding to the combination node in the to-be-executed transaction data, executing the combination transaction operation corresponding to the combination node to obtain the combination processing result corresponding to the combination node; The target transaction processing result is generated based on the transaction processing results corresponding to the ended non-transaction node, the executed transaction node, and the combined processing result.

11. The method according to any one of claims 1 to 10, characterized in that: The target language description information is obtained in the following manner: Displaying a transaction orchestration page, wherein the transaction orchestration page includes a node orchestration control; When the transaction flow chart data is acquired based on the node orchestration control and a description processing instruction corresponding to the target distributed transaction is detected, description processing is performed on the transaction flow chart data to obtain the target language description information.

12. A data processing device, characterized in that: The device comprises: a description acquisition module, configured to acquire target language description information constructed for a target distributed transaction, the target language description information being generated based on transaction flow chart data corresponding to the target distributed transaction, the transaction flow chart data being obtained by performing mixed-mode arrangement of multiple target nodes corresponding to the target distributed transaction based on the transaction execution logic of the target distributed transaction, the multiple target nodes including multiple transaction nodes corresponding to multiple transaction execution modes; A parsing module, configured to parse the target language description information to obtain pending transaction data corresponding to the target distributed transaction; an execution module configured to, upon receiving a target transaction processing request corresponding to the target distributed transaction, sequentially read current node configuration data corresponding to a current execution node among the multiple target nodes from the to-be-executed transaction data based on a preset transaction execution engine, the target transaction processing request, and a node execution order corresponding to the to-be-executed transaction data, and execute the distributed transaction operation corresponding to the current execution node based on a current transaction execution mode corresponding to the current node configuration data and a current execution resource corresponding to the current node configuration data, to obtain a target transaction processing result corresponding to the target distributed transaction.

13. An electronic device, characterized in that: include: processor; a memory for storing processor-executable instructions; The processor is configured to execute the executable instructions to implement the data processing method according to any one of claims 1 to 11.

14. A non-volatile computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the data processing method according to any one of claims 1 to 11 is implemented.

15. A computer program product comprising a computer program, characterized in that When the computer program is executed by an electronic device, the data processing method according to any one of claims 1 to 11 is implemented.

Images