WO2021169243A1

WO2021169243A1 - Method, apparatus and system for processing distributed transaction

Info

Publication number: WO2021169243A1
Application number: PCT/CN2020/114407
Authority: WO
Inventors: 姜宇; 张伟
Original assignee: 华为技术有限公司
Priority date: 2020-02-29
Filing date: 2020-09-10
Publication date: 2021-09-02
Also published as: CN113326272A

Abstract

A method, apparatus and system for processing a distributed transaction, which belong to the technical field of distribution. A database operation instruction sent by a service client to a service database may carry the context of a distributed transaction, such that a network agent node can create and process transaction branches on the basis of the context of the distributed transaction and a database operation statement. Since transaction branches can be created and processed by means of a network agent node, a service client does not need to deploy an interface used for creating and processing the transaction branches, thereby effectively reducing the development cost of the application of the service client to a distributed transaction processing system.

Description

Distributed transaction processing method, device and system

This application claims the priority of the Chinese patent application filed on February 29, 2020 with the application number 202010132037.5 and the invention title of "a transaction processing system", and the application number filed on June 15, 2020 as 202010544092.5 , The priority of the Chinese patent application with the title of "Distributed Transaction Processing Method, Device and System", the entire content of which is incorporated into this application by reference.

Technical field

This application relates to the field of distributed technology, and in particular to a method, device and system for processing distributed transactions.

Background technique

Transaction refers to a sequence of operations composed of one or more resource management operations. Distributed transaction refers to a transaction involving multiple databases (DB) in an operation sequence. Since distributed transactions involve operations on multiple databases, it is necessary to ensure the consistency of operations on each database.

In related technologies, try-confirm-cancel (TCC) technology is usually used to process distributed transactions. The business clients in the resource server (also called business server) that adopt the TCC technology are deployed with try and confirm. And cancel three interfaces. The processing process of the TCC technology includes the following two stages: In the first stage (also called the try stage), the main business client that initiates the distributed transaction calls the try interfaces of the other slave business clients involved in the distributed transaction. To request the reservation of business resources from the business client. In the second stage (also known as the confirm/cancel stage), if the main business client determines that the business resources of each slave business client are successfully reserved, it can send a commit instruction to the transaction server, and the transaction server can then call The confirm interface of each slave business client instructs each slave business client to perform an operation on the reserved business resources, that is, to perform a submit operation. If the master business client determines that the reservation of the business resources of any slave business client fails, it can send a rollback instruction to the transaction server, and the transaction server can then call the cancel interface of each slave business client to instruct each slave business The client cancels the operation on the reserved business resources, that is, performs a rollback operation to release the reserved business resources.

However, because the TCC technology needs to deploy try, confirm, and cancel three interfaces for each business client participating in a distributed transaction, the development cost of the business client is high.

Summary of the invention

This application provides a method, device, and system for processing distributed transactions, which can solve the technical problem of high development cost when implementing distributed transactions by business clients in related technologies.

On the one hand, a distributed transaction processing method is provided. The method is applied to a distributed transaction processing system. The distributed transaction processing system includes a plurality of business servers, a transaction server, and a business database, and each business server includes a network agent node. And a business client, and the method is executed by the network agent node; the method includes: obtaining one or more database operation instructions sent by the business client, each database operation instruction includes: a database operation statement and the context of a distributed transaction , Wherein the database operation instructions included in the one or more database operation instructions are used to implement the transaction branch of the distributed transaction, and the context of the distributed transaction includes the identification of the distributed transaction; each database is executed in the business database The operation instruction includes a database operation statement, and a transaction branch creation request is sent to the transaction server, and the transaction branch creation request includes the identifier of the distributed transaction.

In the distributed transaction processing method provided by this application, the database operation instruction sent by the business client carries the context of the distributed transaction, so that the network agent node can create and process transaction branches based on the database operation instruction. Since there is no need for the business client to create and process transaction branches, the impact on the original business logic of the business client is small, thereby effectively reducing the development cost of the business client applied to the distributed transaction processing system.

Optionally, the method further includes: acquiring lock information of a data set that is targeted by a database operation statement included in the one or more database operation instructions, and the lock information of the data set is used in the business database Identify the data set; correspondingly, the transaction branch creation request also includes the lock information of the data set.

Carrying the lock information of the data set in the transaction branch creation request can facilitate whether the data set is locked by the transaction server, and then determine whether the transaction branch can be created.

Optionally, the network agent node confirms that the automatic submission function of the service database is in the on state, and the network agent node may, after receiving the first creation response sent by the transaction server to indicate that the transaction branch is successfully created, then perform the service The database operation statement included in each database operation instruction is executed in the database. In addition, the network agent node may also send a first commit instruction for the transaction branch of the distributed transaction to the service database in response to the first creation response, where the first commit instruction is used to instruct the service database to submit the transaction branch.

After the network agent node determines that the transaction branch is created successfully, it executes the database operation statement, which can avoid the problem that the previously executed database operation statement is invalid if it determines that the transaction branch creation fails after executing the database operation statement. That is, in the scenario where the creation of the transaction branch fails, the database operation statement is no longer executed, which can avoid wasting the computing resources of the business server.

Optionally, the network agent node may also receive a second creation response sent by the transaction server to indicate that the creation of the transaction branch fails; and, in response to the second creation response, send to the service database the transaction branch of the distributed transaction The first rollback instruction is used to instruct the business database to roll back the transaction branch.

Optionally, the network agent node confirms that the automatic submission function of the business database is in the off state, and may send the execution result of the database operation statement to the business client after each execution of a database operation statement in a database operation instruction; In addition, the network agent node may obtain the lock information of the data set after obtaining the second commit instruction for the transaction branch of the distributed transaction sent by the business client; wherein, if the data set is used to implement the distributed transaction The number of database operation statements of the transaction branch is greater than 1, then the automatic submission function of the business database is set to the off state by the business client; the second commit instruction is the execution result sent by the business client according to the network agent node It is determined that the database operation statements included in each database operation instruction used to implement the transaction branch of the distributed transaction are sent after the execution is successful.

Since the network agent node detects that the automatic submission function of the business database is in the off state, it can determine that the database operation instructions used to implement the transaction branch include multiple, so the network agent node can perform the second submission instruction after receiving the second submission instruction. Obtain the lock information of the data set, and then send a transaction branch creation request.

Optionally, after the network agent node sends the execution result of the database operation statement included in each database operation instruction to the business client, if it obtains the second transaction branch for the distributed transaction sent by the business client Rollback instruction, you can also delete the lock information of the data set, and send the second rollback instruction to the business database; wherein, the second rollback instruction is the task of the business client when determining to implement the transaction branch. Sent after the execution of a database operation sentence included in a database operation instruction fails.

If the network agent node receives the second rollback instruction, it can determine that the transaction branch has failed to execute, and therefore can delete the lock information of the stored data set to avoid the lock information of the data set from occupying too much storage space.

Optionally, the network agent node may obtain the first setting instruction sent by the business client, and may record the automatic submission function of the business database as the on state according to the first setting instruction. Alternatively, the network agent node may obtain the second setting instruction sent by the business client, and may record the automatic submission function of the business database as closed according to the second setting instruction; wherein, the first setting instruction is the business client Sent when it is determined that the number of database operation statements used to implement the transaction branch is equal to 1; the second setting instruction is when the business client determines that the number of database operation statements used to implement the transaction branch is greater than 1 Sent when.

The network agent node records the status of the automatic submission function of the business database according to the acquired first setting instruction or the second setting instruction, which can ensure that when a transaction branch is created, the automatic submission of the business database can be accurately determined according to the recorded status Whether the function is turned on.

Optionally, the first creation response may carry an identifier assigned by the transaction server to the transaction branch; the network agent node receives the first creation sent by the transaction server to indicate that the transaction branch of the distributed transaction is successfully created. After the response, the identifier of the transaction branch and the corresponding relationship of the data set can also be stored in the transaction log of the distributed transaction; afterwards, the network proxy node can receive the third commit instruction for the transaction branch sent by the transaction server, And clean up the transaction branch identifier and the data set recorded in the transaction log; or, the network agent node may receive the third rollback instruction for the transaction branch sent by the transaction server, and then obtain the transaction branch from the transaction according to the transaction branch identifier. Obtain the data set from the log, and roll back the transaction branch according to the data set.

Wherein, the third commit instruction is sent by the transaction server after receiving the commit instruction for the distributed transaction sent by the business client, and the third rollback instruction is sent by the transaction server after the transaction server receives the commit instruction for the distributed transaction. Sent after the rollback instruction of the distributed transaction.

Optionally, after the network agent node sends the first commit instruction for the transaction branch of the distributed transaction to the service database, it can also delete the lock information of the data set; and, if the network agent node determines that the transaction branch is submitted successfully, Then, it can send a commit result indicating that the transaction branch of the distributed transaction is successfully submitted to the business client; if the network agent node determines that the transaction branch of the distributed transaction has failed, it can send an instruction to the business client If the transaction branch of the distributed transaction fails to submit the commit result, the fourth rollback instruction for the transaction branch of the distributed transaction is sent to the business database, and the transaction branch carrying the identifier of the distributed transaction is sent to the transaction server The notification message is used to instruct the transaction server to delete the lock information of the data set corresponding to the transaction branch of the distributed transaction.

After the network agent node sends the first commit instruction for the transaction branch, it feeds back the commit result of the transaction branch to the business client, which can facilitate the business client to determine to commit or roll back the distributed transaction according to the commit result.

Optionally, the network proxy node can intercept the data packet sent by the business client, and if it is detected that the recipient of the data packet sent by the business client is the business database, the network proxy node can obtain and parse the data packet; if If it is detected that the receiver of the data packet sent by the service client is not the service database, the network proxy node may directly forward the data packet to the receiver.

In the solution provided in this application, since the network proxy node only needs to parse the data packets sent by the business client to the business database, and the business clients interact with the business database based on the database protocol, the network proxy node only needs to support the database protocol It can be adapted to business clients developed in different programming languages. That is, the solution provided in this application can be applied to a cross-programming language distributed transaction processing system.

On the other hand, a distributed transaction processing method is provided, which is applied to a distributed transaction processing system. The distributed transaction processing system includes multiple business servers, transaction servers, and business databases. Each business server includes a network agent node and Business client, and the method may be executed by a first business client; the method may include: generating a transaction branch for realizing the distributed transaction according to the transaction branch to be executed by the first business client in the distributed transaction One or more database operation statements; one or more database operation instructions are generated according to the one or more database operation statements, each database operation instruction includes at least one database operation statement and the context of a distributed transaction, and the context of the distributed transaction Including the identification of the distributed transaction; sending the one or more database operation instructions to the first service database, where the first network agent node and the first service client are deployed on the same service server.

Since the database operation instruction sent by the business client carries the context of the distributed transaction, the network agent node that has obtained the database operation instruction can create and process the transaction branch based on the database operation statement and the context of the distributed transaction. Since there is no need for the business client to create and process transaction branches, the impact on the original business logic of the business client is small, thereby effectively reducing the development cost of the business client applied to the distributed transaction processing system.

Optionally, the first business client may be the main business client that initiates the distributed transaction. Correspondingly, the first business client may also send the creation request of the distributed transaction to the transaction server in response to the service request. ; Receive the identifier of the distributed transaction sent by the transaction server; and send a service invocation request to the second business client participating in the distributed transaction, the service invocation request carries the identifier of the distributed transaction; and, the first A business client can determine the transaction branch to be executed by the first business client in the distributed transaction according to the business request.

Optionally, the first business client as the main business client may also perform the following operations: receive the commit result of the transaction branch sent by the first network proxy node; and receive the second business client's response to the service invocation The service invocation response requested to be sent; then, according to the commit result and the service invocation response, a commit instruction or a rollback instruction for the distributed transaction is sent to the transaction server; wherein, the commit instruction for the distributed transaction is used to indicate Submit each transaction branch included in the distributed transaction, and a commit instruction for the distributed transaction is used to instruct to roll back each transaction branch included in the distributed transaction.

In the solution provided by this application, the first business client as the main business client only needs to send the creation request of the distributed transaction, generate the database operation instruction, and send the commit instruction or reply of the distributed transaction in the process of realizing the distributed transaction. Roll instructions. The above operations have little impact on the original business logic of the main business client, that is, the business of the main business client is less intrusive, so it can effectively reduce the adaptation of the main business client to the distributed transaction processing architecture to achieve business Cost of distributed transformation.

Optionally, the first business client can also be a slave business client participating in a distributed transaction. Correspondingly, the first business client can also receive a service call sent by a second business client (ie, the main business client) Request, the service invocation request carries the context of the distributed transaction; according to the service invocation request, the transaction branch to be executed by the first business client in the distributed transaction is determined.

In the process of realizing distributed transactions, the first business client as the slave business client only needs to generate database operation instructions, which can effectively reduce the adaptation of the distributed transaction processing architecture from the business client to realize the distributed business. The cost of retrofitting.

Optionally, the method may further include: the first business client determines that the number of database operation statements used to implement the transaction branch of the distributed transaction is equal to 1, and sends to the first business database an instruction to automatically submit a function The first setting instruction set to the on state; or, the first business client determines that the number of database operation statements used to implement the transaction branch of the distributed transaction is greater than 1, and sends to the first business database an instruction to automatically Submit the second setting instruction in which the function is set to the off state.

The above-mentioned first setting instruction and second setting instruction can be intercepted by the first network agent node, and the first network agent node can accurately determine the state of the automatic submission function of the first service database based on the first setting instruction or the second setting instruction, That is, it can be accurately determined whether the number of database operation statements used to implement the transaction branch of the distributed transaction is greater than one.

Optionally, after sending a second setting instruction for instructing the automatic submission function to be turned off to the first service database, the first service client may also receive each database operation sent by the first network proxy node The execution result of the database operation statement included in the instruction; if it is determined according to the execution result that the database operation statement included in each database operation instruction used to implement the transaction branch of the distributed transaction is executed successfully, the first business client can send the The first service database sends a second commit instruction for the transaction branch of the distributed transaction; if it is determined according to the execution result that any database operation instruction used to implement the transaction branch of the distributed transaction includes a database operation statement that fails to execute, then The first service client may send a second rollback instruction for the transaction branch of the distributed transaction to the first service database.

The aforementioned second commit instruction and second rollback instruction may be intercepted by the first network agent node, and the first network agent node may create a transaction branch based on the second commit instruction, or may roll back the transaction branch based on the second rollback instruction.

In another aspect, a network agent node is provided, which is applied to a distributed transaction processing system. The distributed transaction processing system includes multiple business servers, transaction servers, and business databases. Each business server includes a network agent node and a business client. , The network agent node includes:

The parsing module is used to obtain one or more database operation instructions sent by the business client. Each database operation instruction includes: a database operation statement and the context of the distributed transaction, and the one or more database operation instructions include database operations The statement is used to implement the transaction branch of the distributed transaction, and the context of the distributed transaction includes the identifier of the distributed transaction;

The transaction branch processing module is used to execute database operation statements included in each database operation instruction in the business database, and send a transaction branch creation request to the transaction server, and the transaction branch creation request includes the identifier of the distributed transaction.

Optionally, the transaction branch processing module is further used to obtain lock information of a data set, the data set being targeted by a database operation statement included in the one or more database operation instructions, and the lock information of the data set used in The data set is identified in the business database; the transaction branch creation request also includes lock information of the data set.

Optionally, the transaction branch processing module is configured to: confirm that the automatic submission function of the business database is in the on state; after receiving the first creation response sent by the transaction server indicating that the transaction branch is successfully created, in the The business database executes database operation statements included in each database operation instruction; the transaction branch processing module is further configured to: in response to the first creation response, send a first commit instruction for the transaction branch to the business database.

Optionally, the transaction branch processing module is further configured to: receive a second creation response sent by the transaction server for indicating that the transaction branch creation fails; in response to the second creation response, send to the business database a response to the transaction The first rollback instruction of the branch.

Optionally, the transaction branch processing module is further used to: confirm that the automatic submission function of the business database is in the off state; send the execution result of the database operation statement included in each database operation instruction to the business client; After the second commit instruction for the transaction branch sent by the business client, the lock information of the data set is acquired; where the second commit instruction is the business client determining the database included in each database operation instruction according to the execution result Sent after the operation statements are executed successfully.

Optionally, the transaction branch processing module is further configured to: after sending the execution result of the database operation statement included in each database operation instruction to the business client, obtain the second transaction branch sent by the business client. Rollback instruction, delete the lock information of the data set; send the second rollback instruction to the business database; wherein, the second rollback instruction is executed by the business client in determining the database operation statement included in any database operation instruction Sent after failure.

Optionally, the transaction branch processing module is further configured to: obtain the first setting instruction sent by the business client; according to the first setting instruction, record that the automatic submission function of the business database is turned on; wherein, the first setting The instruction is sent when the business client determines that the number of database operation statements used to implement the transaction branch is equal to 1.

Optionally, the transaction branch processing module is further configured to: obtain a second setting instruction sent by the business client; according to the second setting instruction, record that the automatic submission function of the business database is off; wherein, the second setting The instruction is sent when the business client determines that the number of database operation statements used to implement the transaction branch is greater than one.

Optionally, the first creation response carries an identifier assigned by the transaction server to the transaction branch; the transaction branch processing module is further configured to: upon receiving a message sent by the transaction server indicating that the transaction branch is successfully created After the first response is created, the identifier of the transaction branch and the corresponding relationship of the data set are stored in the transaction log of the distributed transaction; the third commit instruction for the transaction branch sent by the transaction server is received, and the transaction log is cleaned The recorded identifier of the transaction branch and the data set; wherein, the third commit instruction is sent by the transaction server after receiving the commit instruction for the distributed transaction sent by the business client.

Optionally, the first creation response carries an identifier assigned by the transaction server to the transaction branch; the transaction branch processing module is further configured to: upon receiving a message sent by the transaction server indicating that the transaction branch is successfully created After the first response is created, the identifier of the transaction branch and the corresponding relationship of the data set are stored in the transaction log of the distributed transaction; the third rollback instruction for the transaction branch sent by the transaction server is received, according to the transaction branch The identifier of obtains the data set from the transaction log, and rolls back the transaction branch according to the data set; wherein, the third rollback instruction is that the transaction server receives the distributed transaction sent by the business client Sent after the rollback instruction.

In another aspect, a business client is provided, which is applied to a distributed transaction processing system. The distributed transaction processing system includes a plurality of business servers, a transaction server, and a business database. Each business server includes a network agent node and a business client. , The business client includes:

The processing module is used to generate one or more database operation statements for implementing the transaction branch according to the transaction branch to be executed by the business client in the distributed transaction;

The application program interface module is used to generate one or more database operation instructions according to the one or more database operation statements, and each database operation instruction includes: at least one database operation statement and the context of the distributed transaction, and the distributed transaction The context of includes the identity of the distributed transaction;

The database driver is used to send the one or more database operation instructions to the first network agent node, where the first network agent node and the service client are deployed on the same service server.

Optionally, the application program interface module is further configured to: in response to a service request, send a creation request of the distributed transaction to the transaction server; receive an identifier of the distributed transaction sent by the transaction server;

The business client further includes: a service invocation module for sending a service invocation request to a second business client participating in the distributed transaction, and the service invocation request carries the identifier of the distributed transaction; the processing module also uses Based on the business request, determine the transaction branch to be executed by the business client in the distributed transaction.

Optionally, the processing module is further configured to: receive the commit result of the transaction branch sent by the first network agent node; receive the service invocation response sent by the second business client in response to the service invocation request; and according to the commit Result and the service call response, send a commit instruction or rollback instruction for the distributed transaction to the transaction server; wherein, the commit instruction for the distributed transaction is used to instruct to submit each transaction branch included in the distributed transaction, and for The commit instruction of the distributed transaction is used to instruct to roll back each transaction branch included in the distributed transaction.

Optionally, the processing module is further configured to: receive a service invocation request sent by a second business client, the service invocation request carries the context of the distributed transaction; according to the service invocation request, determine that the distributed transaction is The branch of the transaction to be executed by the business client.

Optionally, the processing module is further configured to: determine that the number of database operation statements is equal to 1, and instruct the database driver to send a first setting instruction to the first business database, and the first setting instruction instructs to set the automatic submission function to Open state.

Optionally, the processing module is further configured to: determine that the number of database operation statements is greater than 1, and instruct the database driver to send a second setting instruction to the first business database, and the second setting instruction instructs to set the automatic submission function to Disabled.

Optionally, the processing module is further configured to: receive the execution result of the database operation statement included in each database operation instruction; determine according to the execution result that the database operation statement included in each database operation instruction is executed successfully, and instruct the database driver Send a second commit instruction for the transaction branch to the first service database.

Optionally, the business client further includes: receiving the execution result of the database operation statement included in each database operation instruction; determining, according to the execution result, that the execution of the database operation statement included in any database operation instruction has failed, and instructing the database driver to The first service database sends a second rollback instruction for the transaction branch.

In another aspect, a network agent node is provided. The network agent node includes a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor implements the foregoing when the computer program is executed. The distributed transaction processing method performed by the network agent node provided by the aspect.

In another aspect, a business client is provided. The business client includes a memory, a processor, and a computer program stored in the memory and running on the processor, and the processor implements the foregoing when the computer program is executed. The distributed transaction processing method performed by the first business client provided by the aspect.

In yet another aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions. When the instructions are executed by a processor, the distributed transaction executed by the network agent node as provided in the above aspect is realized.的处理方法。 Treatment methods.

In yet another aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions. When the instructions are executed by a processor, the distributed system executed by the first business client as provided in the above aspect is implemented. The processing method of the transaction.

In another aspect, a distributed transaction processing system is provided. The distributed transaction processing system includes: a transaction server, a plurality of business servers, and a plurality of business databases;

Each service server includes the network agent node provided in the above-mentioned aspect, and the service client provided in the above-mentioned aspect.

In summary, this application provides a method, device, and system for processing distributed transactions. In the process of processing distributed transactions, the solution provided in this application can be carried in the database operation instructions sent by the business client to the business database. There is a distributed transaction context, so that the network agent node can create and process transaction branches based on the distributed transaction context and the database operation statement. Since transaction branches can be created and processed through network proxy nodes, there is no need for the business client to deploy interfaces for creating and processing transaction branches (such as try, confirm, and cancel interfaces), thereby effectively reducing the application of business clients to distributed The development cost of the transaction processing system.

Description of the drawings

FIG. 1 is a schematic structural diagram of a distributed transaction processing system provided by an embodiment of the present application;

Figure 2 is a schematic structural diagram of another distributed transaction processing system provided by an embodiment of the present application;

FIG. 3 is a flowchart of a method for processing distributed transactions according to an embodiment of the present application;

FIG. 4 is a flowchart of another distributed transaction processing method provided by an embodiment of the present application;

FIG. 5 is a flowchart of a method for a network proxy node to intercept data packets according to an embodiment of the present application;

FIG. 6 is a schematic structural diagram of another distributed transaction processing system provided by an embodiment of the present application;

Fig. 7 is a schematic structural diagram of yet another distributed transaction processing system provided by an embodiment of the present application.

Detailed ways

The following describes in detail the distributed transaction processing method, device, and system provided by the embodiments of the present application with reference to the accompanying drawings.

FIG. 1 is a schematic structural diagram of a distributed transaction processing system provided by an embodiment of the present application. As shown in FIG. 1, the system may include: multiple business servers 01, transaction servers 02, and multiple business databases 03. Among them, each business database 03 corresponds to a business server 01, and each business database 03 is used to store the business data of its corresponding business server 01. In addition, each business database 03 is deployed in a database server.

In the embodiment of the present application, the distributed transaction processing system may adopt a service mesh architecture to implement communication between business servers 01, so as to ensure that the services running in the business client 011 in each business server 01 can be Reliable call. As shown in Figure 1, each service server 01 in the system may be deployed with a network agent node 012 in addition to a service client 011. The network agent nodes 012 in each business server 01 can form a service grid, which can realize the communication between the business clients 011 in different business servers 01, the communication between the business clients 011 and the transaction server 02, and the business clients The terminal 011 communicates with the service database 03.

Optionally, each service server 01 may run one or more virtual machines, and the service client 011 and the network proxy node 012 may be deployed in the same virtual machine, or they may be deployed in different virtual machines. Alternatively, each service server 01 may run one or more containers, and the service client 011 and the network agent node 012 may be deployed in the same container, or they may be deployed in different containers.

Each of the business server 01, the transaction server 02, and the database server on which the business database 03 is deployed can be a physical server, or a physical server cluster composed of several physical servers, or a cloud computing center.

Optionally, any two of the multiple service servers 01, the transaction server 02, and the database server where the service database 03 is deployed may be independent physical servers. That is, the transaction server 02, each service client 011, and each service database 03 are physically isolated, thereby ensuring the operational performance of the transaction server 02, each service client 011, and each service database 03.

Alternatively, at least two of the multiple service servers 01, the transaction server 02, and the database server where the service database 03 is deployed may be deployed in the same physical server. For example, multiple service servers 01 can be deployed in the same physical server.

Multiple business servers 01 in the distributed transaction processing system can participate in implementing the same distributed transaction (also called a global transaction), and each business server 01 can implement a transaction branch in the distributed transaction (for this For the business server 01, it can also be referred to as the local transaction of the business server 01). The transaction server 02 is responsible for coordinating the processing of the entire distributed transaction. For example, it can handle the initiation of distributed transactions, the creation of transaction branches, the commit or rollback of distributed transactions, and the timeout check of distributed transactions.

Optionally, FIG. 2 is a schematic structural diagram of another distributed transaction processing system provided by an embodiment of the present application. As shown in FIG. 2, the system may include a first service server 01a for implementing distributed transactions, and at least A second service server 01b. Only one second service server 01b is schematically shown in FIG. 2. Wherein, the first service server 01a may be a service server used to initiate the distributed transaction, and therefore may also be referred to as a main service server. As one of the participants of the distributed transaction, each second service server 01b can also be referred to as a slave service server. And, referring to FIG. 2, it can be seen that the business data of the first business client 011a in the first business server 01a can be stored in the first business database 03a, and the business data of the second business client 011b in the second business server 01b It can be stored in the second service database 03b.

In the embodiment of the present application, each business server 01 can implement one transaction branch by performing one or more operations on the business data in its corresponding business database 03. The transaction branch may be a transaction branch of a distributed transaction, or may not be a branch of a distributed transaction, that is, the transaction branch may not participate in a distributed transaction. Among them, every time an operation is performed on the business data in the business database 03, the business client 011 in the business server 01 needs to generate a database operation statement, and execute the database operation statement in the business database 03. After the business database 03 receives the commit instruction sent by the business client 011, it will persistently update its business data based on the execution result of the database operation statement, that is, execute the commit operation.

Therefore, if a transaction branch contains only one operation for the business database 03, the business client 011 in the business server 01 only needs to generate and execute a database operation statement in order to implement the transaction branch, and the database operation statement can be executed. Commit the transaction branch. If a transaction branch contains multiple operations on the business database, the business client 011 in the business server 01 needs to generate and execute multiple database operation statements in order to implement the transaction branch, and the multiple database operation statements must be executed before they are completed. Commit the transaction branch.

Based on this, the business client 011 in each business server 01 provided in the embodiment of the present application, if it is determined that the number of database operation statements used to implement the transaction branch to be executed is equal to 1, the corresponding business database The auto-commit function of 03 is set to the on state, that is, the business database 03 can automatically commit the transaction branch. If the business client 011 determines that the number of database operation statements used to implement the transaction branch to be executed is greater than 1, then the automatic submission function of its corresponding business database 03 can be set to the off state, that is, the business database 03 needs to receive After the commit instruction sent by the business client 011, the transaction branch can be committed.

FIG. 3 is a flowchart of a distributed transaction processing method provided by an embodiment of the present application. The method can be applied to the system shown in FIG. 1 or FIG. 2. In the embodiment of the present application, the method is applied to the system shown in FIG. 2 and the transaction branch to be executed by the first business client includes only one operation on the database as an example for description. Referring to Figure 3, the method may include:

Step 101: The first business client sends a creation request of a distributed transaction to the transaction server.

After the first service client receives the service request, if it is determined that the service requested by the service request needs to be realized through the joint participation of the first service client and at least one second service client, it may respond to the service request and send The transaction server sends a request to create a distributed transaction.

For example, suppose that the first business client is a business client of Bank A, and the business request is a transfer request for transferring money from the first account of Bank A to the second account of Bank B. Since the transfer service requested by the transfer request requires the business client of Bank A and the business client of Bank B to participate in the implementation, the business client of Bank A can respond to the business request by sending distributed transaction information to the transaction server. Create a request.

Step 102: The transaction server sends the identification of the distributed transaction to the first service client.

After the transaction server receives the creation request of the distributed transaction, it can assign an identification (identification, ID) to the distributed transaction, and send the identification of the distributed transaction to the first service client.

Optionally, as shown in FIG. 2, an application programming interface (application programming interface, API) module 0111 may be deployed in the first service client 011a, and the API module 0111 includes a Begin Transaction (Begin Transaction) API. The first service client 011a may send a distributed transaction creation request R1 to the transaction server 02 by calling the Begin Transaction API to obtain the ID of the distributed transaction, and then construct the context of the distributed transaction. The input parameter of the Begin Transaction API may include the address of the transaction server 02, and the return value may include the ID of the distributed transaction. If the ID allocation fails due to factors such as the failure of the transaction server 02, the return value can be -1. The address of the transaction server 02 is stored locally by the first business client 011a, and the address of the transaction server 02 may include the Internet protocol (IP) address and port number of the transaction server. The data type of the input parameter of the Begin Transaction API can be string, and the data type of the return value can be long.

It can also be seen with reference to FIG. 2 that the first service client 011a also includes a communication module 0112. The creation request R1 of a distributed transaction sent by the API module 0111 can be sent to the first network agent node 012a through the communication module 0112, and then The first network agent node 012a transparently transmits to the transaction server 02. Correspondingly, the distributed transaction ID returned by the transaction server 02 can also be transparently transmitted by the first network agent node 012a to the communication module 0112 of the first service client 011a, and then transmitted by the communication module 0112 to the API module 0111.

Step 103: The first business client generates a database operation statement for implementing the transaction branch to be executed in the distributed transaction.

After the first business client receives the ID of the distributed transaction, it can determine the transaction branch to be executed by the first business client in the distributed transaction according to the business request, and generate the transaction branch to be executed in the distributed transaction. A database operation statement of the transaction branch. The first business database corresponding to the first business client may be a relational database, and the database operation statement may be a structured query language (SQL) statement.

It can also be seen with reference to FIG. 2 that the first business client 011a further includes a processing module 0115, which can generate a database operation statement for implementing the transaction branch to be executed in the distributed transaction.

For example, suppose the service request is a transfer request of 1000 yuan from the first account of Bank A to the second account of Bank B, then the business client of Bank A can determine that the branch of the transaction to be executed is: 1,000 yuan will be deducted from the balance of the account. Correspondingly, the business client of the bank A can generate a database operation statement for instructing to reduce the balance of the first account by 1000.

Step 104: The first service client sends a first setting instruction to the first service database.

Since the number of database operation statements used to implement the transaction branch is equal to 1, the first business client can determine that the database operation statement is executed and can submit the transaction branch, and then can send the first setting to the first business database Instruction, the first setting instruction is used to instruct to set the automatic submission function of the first service database to an on state.

For example, referring to FIG. 2, the first service client 011a further includes a database driver (DB driver) 0113. The processing module 0115 can instruct the database driver 0113 to send the first setting instruction to the first service database 03 through the communication module 0112 when detecting that the number of database operation sentences is equal to 1.

Step 105: The first network agent node obtains the first setting instruction, and records that the automatic submission function of the first service database is turned on.

Since the first setting instruction sent by the first service client to the first service database needs to be forwarded by the first network proxy node, the first network proxy node can obtain the first setting instruction and record it according to the first setting instruction The automatic submission function of the first business database is turned on. In addition, the first network agent node may forward the first setting instruction to the first service database after completing the status recording.

By recording the status of the automatic submission function of the first service database, the first network agent node can ensure that when a transaction branch is subsequently created, it can accurately determine whether the automatic submission function of the first service database is enabled according to the recorded status. Furthermore, the first network agent node can determine whether the number of database operation statements used to implement transaction branching is greater than 1 according to the state of the automatic submission function, and can obtain it in different ways according to the number of database operation statements. The lock information of the transaction branch, and the transaction branch is created.

For example, the first network agent node may record the status identifier of the first service database, and the first network agent node may set the status identifier to true after obtaining the first setting instruction to indicate the first service The automatic submission function of the database is turned on.

In the embodiment of the present application, as shown in FIG. 2, the first network agent node 012a may include a connection management module 0121, a parsing module 0122, and a transparent transmission module 0123. The connection management module 0121 can intercept each data packet sent by the first service client 011a, and detect whether the recipient of each data packet is the first service database 03a. If the recipient of the data packet is the first service database 03a, the connection management module 0121 can send the data packet to the parsing module 0122, and the parsing module 0122 can parse the data packet. If the recipient of the data packet is not the first service database 03a, the connection management module 0121 can send the data packet to the transparent transmission module 0123, and the transparent transmission module 0123 can directly transparently transmit the data packet. Among them, transparent transmission means that the data packet is directly transmitted to the destination address without analyzing the content of the data packet or making any changes to the content of the data packet.

Taking Figure 2 as an example, suppose that the first network proxy node 012a receives the distributed transaction creation request R1 sent by the first service client 011a, then since the recipient of the distributed transaction creation request R1 is the transaction server 02, and It is not the first service database 03a, so the transparent transmission module 0123 of the first network agent node 012a can directly transparently transmit the creation request R1 of the distributed transaction to the transaction server 02.

Step 106: The first business client generates a database operation instruction based on the database operation statement and the context of the distributed transaction.

In the embodiment of the present application, the first business client may combine the context of the distributed transaction with the database operation statement to generate a database operation instruction. The context of the distributed transaction includes the identification of the distributed transaction. In addition, the address of the transaction server may also be included, and the address of the transaction server is pre-stored in the first service client.

Since the database operation instruction carries the context of distributed transactions, the first network agent node can create and process transaction branches based on the database operation instruction. Since there is no need for the first business client to create and process transaction branches, the impact on the original business logic of the first business client is small, thereby effectively reducing the development cost of the first business client applied to the distributed transaction processing system.

Optionally, the first business client may add the context of the distributed transaction as a hint to the database operation statement according to the syntax format corresponding to the database type (DB type) of the first business database, thereby obtaining A database operation instruction. For example, referring to FIG. 2, the API module 0111 of the first business client 011a further includes an operation instruction creation API, and the first business client 011a can generate a database operation instruction L1 by calling the operation instruction creation API. Among them, the input parameters of the operation instruction creation API may include: database operation statement, database type, and context of distributed transaction. The data type of the database operation statement and the data type of the database type may both be string, and the context of the distributed transaction The data type can be long. The return value of the operation instruction creation API is the database operation instruction carrying the context of the distributed transaction. If the operation instruction creation API fails to execute, the return value is empty. The data type of the return value can be string.

In addition, in order to facilitate the first network agent node to recognize the context of the distributed transaction in the database operation instruction, the first business client may also add a distributed transaction keyword to the database operation instruction, and the distributed transaction keyword can be used The context of distributed transaction is added to the instruction to indicate the database operation.

For example, suppose the distributed transaction keyword is AA, the identifier of the distributed transaction is ID1, the IP address of the transaction server is xxxx, and the database operation statement used to indicate that the balance of the first account "yy" is reduced by 1000 For the SQL statement:

UPDATE table1 SET a1=a1-1000 WHERE b1='yy';

Then, after the first business client combines the SQL statement and the context of the distributed transaction through the operation instruction creation API, the generated database operation instruction can be:

/*AA; ID: ID1; IP: x.x.x.x*/UPDATE table1 SET a1=a1-1000 WHERE b1='yy'.

Step 107: The first service client sends the database operation instruction to the first service database.

After the first business client generates the database operation instruction, it can send the database operation instruction to the first business database.

Optionally, referring to FIG. 2, the database driver 0113 in the first service client 011a may send the database operation instruction L1 generated by the API module 0111 to the first service database 03a. Since the first network agent node 012a can intercept the data packet sent by the first service client 011a, as shown in FIG. 2, the first network agent node 012a can obtain the database operation instruction L1 sent by the first service client 011a . The database operation instruction L1 can be used for the first network agent node that has obtained the database operation instruction to create and process the transaction branch.

Step 108: The first business client sends a service invocation request to the second business client.

Since the distributed transaction also requires the second service client in the second service server to participate in the implementation, the first service client also needs to send a service invocation request to the second service client. The service call request may carry the context of the distributed transaction. Wherein, the service call request may be a remote procedure call (remote procedure call, RPC) request.

For example, referring to FIG. 2, the first business client 011a further includes a service invocation module 0114. The service invocation module 0114 can send a service invocation request Q1 to the second business client 011b, and the service invocation request Q1 can be proxied through the first network agent. The node 012a and the second network agent node 012b transparently transmit to the second service client 011b. Wherein, after intercepting the service call request Q1, the first network agent node 012a can recognize that the recipient of the service call request Q1 is not the first service database 03a, so the first network agent node 012a can directly send the second The service client 011b forwards the data packet.

Assuming that the business request received by the first business client 011a is a transfer request of 1000 yuan from the first account of Bank A to the second account of Bank B, then the business client of Bank A can send the business client of Bank B to the business customer of Bank B. The terminal sends a service call request for instructing to increase the balance of the second account by 1000.

Step 109: The first network agent node obtains the database operation instruction, and obtains the data set targeted by the database operation statement from the first service database.

Since the receiver of the database operation instruction is the first service database, the first network agent node can obtain the database operation instruction and obtain the data set targeted by the database operation statement from the first service database. Optionally, the first network agent node can parse out the database operation statement from the database operation instruction, and then create and run the data set acquisition statement, so that the data set targeted by the database operation statement can be obtained from the first business database .

For example, as shown in FIG. 2, the first network agent node 012a further includes a transaction branch processing module 0124 and a database driver 0125. The parsing module 0122 can parse out database operation statements (such as SQL statements) and the context of distributed transactions from the database operation instructions, and send the database operation statements and the context of distributed transactions to the transaction branch processing module 0124. The transaction branch processing module 0124 can create a data set acquisition statement. For example, the data set acquisition statement created by the transaction branch processing module 0124 may be: Select for update. After that, the transaction branch processing module 0124 can run the data set acquisition statement: Select for update through the database driver 0125, so as to obtain the data set targeted by the database operation statement.

Optionally, in the embodiment of the present application, after obtaining the database operation instruction sent by the first service client, the first network agent node may also first detect whether the database operation instruction carries the context of distributed transactions. If the database operation instruction carries the context of the distributed transaction, the data set targeted by the database operation statement can be obtained and subsequent operations can be continued.

If the database operation instruction does not carry the context of the distributed transaction, the first network agent node can determine that the database operation statement in the database operation instruction is not used to implement the transaction branch in the distributed transaction, so it can directly send to the first The business database transparently transmits the database operation instructions without obtaining the data set and performing subsequent operations.

Step 110: The first network agent node obtains the lock information of the data set.

Since in step 105, the first network agent node has determined that the automatic submission function of the first service database is turned on according to the first setting instruction, it can be determined that the database operation statement in the database operation instruction can independently implement a transaction branch. . Furthermore, the first network agent node can obtain the lock information of the data set targeted by the database operation statement, and the lock information of the data set is the lock information of the transaction branch. For example, referring to FIG. 2, the transaction branch processing module 0124 in the first network agent node 012a can obtain the lock information of the data set targeted by the database operation statement.

Wherein, the data set targeted by the database operation statement may refer to a collection of data operated by the database operation statement. The lock information of the data set can be used to uniquely identify the data set targeted by the database operation statement in the first business database. For example, the lock information of the data set may include the table name of the data table where the data set is located, and the primary key of the row where the data set is located.

Step 111: The first network agent node sends a transaction branch creation request to the transaction server.

After the first network agent node obtains the lock information of the data set, that is, the lock information of the transaction branch, it can send a transaction branch creation request to the transaction server. The transaction branch creation request may include the lock information of the data set and the identification of the distributed transaction. For example, referring to FIG. 2, the transaction branch processing module 0124 in the first network agent node 012a may send a transaction branch creation request S1 to the transaction server 02.

In the embodiment of the present application, the automatic submission function for the first service database is turned on, and the transaction branch to be executed by the first service client participates in a distributed transaction scenario. Since the first network agent node needs to execute database operation statements in the first business database, it also needs to perform operations such as obtaining data sets, obtaining lock information of the data sets, and requesting to create a transaction branch, and the above operations can be submitted only after successful execution Transaction branch. Therefore, before the first network agent node applies to the transaction server to create a transaction branch of a distributed transaction, it also needs to send a second setting instruction to the first service database. The second setting instruction is used to instruct the first service database to The automatic submission function is set to off. As a result, it can be ensured that the first service database will not automatically submit the transaction branch after the execution of the database operation statement is completed, but can be used in the first network agent node after the first network agent node determines that the transaction branch is successfully created. Commit the transaction branch under the instructions of. Wherein, the second setting instruction may be sent by the transaction branch processing module 0124 to the first service database 03a through the database driver 0125.

Step 112: The transaction server sends a creation response to the first network agent node.

After receiving the transaction branch creation request, the transaction server can detect whether the transaction branch can be created based on the lock information of the data set.

If the transaction server detects that the lock information of the data set in the creation request is different from the lock information of other transaction branches stored in it, it can determine that the data set targeted by the database operation statement used to implement the transaction branch is not locked. Therefore, it can be determined that the transaction branch can be created. The transaction server may then assign an identifier to the transaction branch, and send a first creation response indicating that the transaction branch is successfully created to the first network agent node, and the first creation response carries the identifier of the transaction branch. In addition, the transaction server may also store the lock information of the data set in the creation request, that is, lock the data set targeted by the database operation statement.

If the transaction server detects that the lock information of the data set in the creation request is the same as the lock information of some other transaction branch stored in it, it can determine that the data set targeted by the database operation statement used to implement the transaction branch has been added Lock, so it can be determined that the transaction branch cannot be created. The transaction server may further send to the first network agent node a second creation response indicating that the creation of the transaction branch fails.

Step 113: The first network agent node detects whether the transaction branch is successfully created.

After the first network agent node receives the creation response sent by the transaction server, it can detect whether the transaction branch is successfully created according to the creation response. If the creation response received by the first network proxy node is the second creation response used to indicate that the transaction branch creation failed, the first network proxy node can perform step 114; if the creation response received by the first network proxy node is If the second creation response is used to indicate that the transaction branch is successfully created, the first network agent node may execute step 115. For example, the transaction branch processing module 0124 in the first network agent node 011a may detect whether the transaction branch is successfully created according to the received creation response.

Step 114: The first network agent node sends a first rollback instruction for the transaction branch to the first service database.

If the first network agent node receives the second creation response sent by the transaction server, it can be determined that the transaction branch has failed to be created, and then the first rollback instruction for the transaction branch can be sent to the first service database. The first service database may perform a rollback operation in response to the first rollback instruction. For example, the first service database may respond to the first rollback instruction to restore its automatic submission function to the on state.

For example, the transaction branch processing module 0124 in the first network agent node 011a may send the first rollback instruction for the transaction branch to the first service database 03a through the database driver 0125.

Step 115: The first network agent node executes the database operation statement in the first service data.

If the first network agent node receives the first creation response sent by the transaction server, it can be determined that the transaction branch is successfully created, and the database operation statement can be executed in the first service data.

For example, referring to FIG. 2, the transaction branch processing module 0124 in the first network agent node 012a can execute SQL statements in the first service data 03a through the database driver 0125.

Step 116: The first network agent node stores the identifier of the transaction branch and the corresponding relationship of the data set in the transaction log of the distributed transaction.

After the first network agent node executes and completes the database operation statement, it can also record the transaction branch identifier and the corresponding relationship of the data set targeted by the database operation statement in the transaction log of the distributed transaction, so that the subsequent need to roll back the database operation statement When a transaction is branched, a rollback operation can be performed based on the data set recorded in the transaction log. Wherein, the transaction log may be a log table created in the first business database for recording related data of distributed transactions. For example, the transaction branch processing module 0124 in the first network agent node 011a may correspondingly store the identifier of the transaction branch and the data set in the transaction log of the distributed transaction.

Optionally, the above steps 115 and 116 can also be performed after step 109 and before step 111, that is, the first network agent node can also execute the database operation statement first, and then request the creation of a transaction branch. Correspondingly, in the above step 114, when the first business database performs a rollback operation, it also needs to roll back its business data to the state before the database operation statement is executed. It can be seen that by executing the database operation statement after determining that the transaction branch is successfully created, it is possible to avoid the problem that the previously executed database operation statement is invalid if it is determined that the transaction branch creation fails after the database operation statement is executed. That is, in a scenario where the creation of a transaction branch fails, the database operation statement is no longer executed, which can avoid wasting the computing resources of the first business server.

Step 117: The first network agent node sends a first commit instruction for the transaction branch to the first service database.

After the first network agent node determines that the transaction branch is successfully created, and records the identifier of the transaction branch and the corresponding data set in the transaction log of the distributed transaction, the first network agent node can send the first commit instruction for the transaction branch to the first service database , The first commit instruction is used to instruct the first business database to commit the transaction branch. For example, the transaction branch processing module 0124 in the first network agent node 011a may send the first commit instruction for the transaction branch to the first service database 03a through the database driver 0125.

Step 118: The first network proxy node sends the commit result of the transaction branch to the first service client.

After sending the first commit instruction for the transaction branch to the first service database, the first network agent node may also receive the commit response returned by the first service database. If the first service database normally completes the commit of the transaction branch, the commit response may indicate that the commit of the transaction branch is successful. Correspondingly, the first network agent node may send to the first service client a submission result indicating that the transaction branch is successfully submitted. If the first service database fails to commit the transaction branch due to factors such as failure, the commit response may indicate that the transaction branch fails to commit. Correspondingly, the first network agent node may send to the first service client a submission result indicating that the transaction branch fails to be submitted. For example, the transaction branch processing module 0124 in the first network agent node 011a may send the commit result of the transaction branch to the first service client 011a.

Optionally, after sending the first submission instruction, the first network proxy node may also delete its cached lock information. In addition, if the first network agent node determines that the transaction branch commit failed, it may also send a fourth rollback instruction for the transaction branch to the first service database, and send a notification carrying the transaction branch identifier to the transaction server information. Wherein, the fourth rollback instruction may be used to instruct the first business database to perform a rollback operation, and the notification message may be used to instruct the transaction server to delete the lock information of the transaction branch, that is, to instruct the transaction server to release the transaction branch for the transaction. Lock.

The first network agent node can complete the first phase of the distributed transaction after sending the completion of the first rollback instruction to the first service database or sending the commit result of the transaction branch to the first service client. This first stage may also be referred to as the request stage or the voting stage. Because in the process of implementing the first phase of the distributed transaction operation, the creation and processing of transaction branches can be implemented by the network agent node, and the business client only needs to call the transaction start API and the operation instruction creation API. The call has little impact on the original business logic of the business client, so it can effectively reduce the cost of adapting the business client to the distributed transaction processing architecture.

Step 119: The second business client sends a service invocation response to the first business client.

In the embodiment of the present application, after the second business client receives the service invocation request carrying the context of the distributed transaction sent by the first business client, it may determine that the second business client is to be executed based on the service invocation request The transaction branch can then be used to generate the database operation statement used to implement the transaction branch.

For example, suppose the second business client is the business client of Bank B, and the service call request received by the business client of Bank B is used to indicate that the balance of the second account is increased by 1000, then the balance of the B bank The business client may generate a database operation statement used to instruct the balance of the second account to increase by 1000.

It can be seen with reference to FIG. 2 that the API module 0111, the communication module 0112, the database driver 0113, the service invocation module 0114, and the processing module 0115 are also deployed in the second service client 011b. The processing module 0115 of the second business client 011b can generate a database operation instruction L2 by calling the API module 0111, and send the database operation instruction L2 to the second business database 03b through the database driver 0113. As shown in FIG. 2, the connection management module 0121 in the second network agent node 012b can obtain the database operation instruction L2, and the analysis module 0122 can parse the database operation instruction L2. Furthermore, the transaction branch processing module 0124 can send a transaction branch creation request S2 to the transaction server 01 based on the parsed database operation instruction L2 to create and process the transaction branch. After the transaction branch processing module 0124 of the second network agent node 012b completes the transaction branch, it can return the commit result of the transaction branch to the second service client 011b.

If the processing module 0115 of the second business client 011b determines that the transaction branch is submitted successfully according to the submission result, it may send a service invocation response indicating the success of the service invocation to the first business client 011a. If the processing module 0115 of the second business client 011b determines that the transaction branch has failed to be submitted according to the submission result, it may send a service invocation response indicating the failure of the service invocation to the first business client 011a. The service invocation response can be transparently transmitted to the first service client 011a through the second network agent node 012b and the first network agent node 012a.

That is, after step 108, the second service client 011b can perform the methods shown in step 103, step 104, and step 106 to step 108, and the second network proxy node 012b can perform step 105 and step 109. Go to the method shown in step 118. For the operations performed by the second service client 011b and the second network proxy node 012b, reference may be made to the relevant descriptions of the foregoing step 103 to step 118, which will not be repeated here.

Optionally, after the processing module 0115 of the second business client 011b receives the service invocation request sent by the first business client 011a, if it is determined that it can run its own service to implement the transaction branch to be executed, there is no need to Invoking the services of other business clients, that is, there is no need to perform the method shown in step 108 above. If the processing module 0115 of the second service client 011b determines that the service of the third service client in the third service server needs to be invoked, the service invocation module 0114 may be instructed to execute the method shown in step 108 above. Correspondingly, the third service client and the third network proxy node in the third service server also need to execute the methods shown in step 103 to step 118 above. That is, in addition to the first service server and the second service server, the third service server is also one of the participants of the distributed transaction.

Optionally, the first business client may also send the service invocation request to the second business client after determining that its transaction branch is successfully submitted. That is, the above step 108 can also be executed after step 118. Correspondingly, the context of the distributed transaction carried in the service invocation request sent by the first business client to the second business client may further include: the identifier of the transaction branch executed by the first network proxy node. The identifier of the transaction branch may be sent to the first service client after the first network agent node receives the first creation response.

If the distributed transaction context carried in the service invocation request received by the second business client also includes the identifier of the transaction branch executed by the first network proxy node, then the database operation instruction generated by the second business client carries The context of the distributed transaction also includes the identifier of the transaction branch executed by the first network agent node. Therefore, the transaction branch creation request sent by the second network agent node to the transaction server can carry the identifier of the distributed transaction and the identifier of the transaction branch executed by the first network agent node. After the transaction server receives the transaction branch creation request, it can determine that the first business client has invoked the service of the second business client. That is, the transaction server can clarify the service invocation status between various business clients based on the identifier of the transaction branch carried in the transaction branch creation request.

Optionally, the first business client may also generate a database operation statement after determining that the service call of the second business client is successful. That is, the above step 108 and step 109 can also be executed before step 103. Alternatively, the above step 108 can also be performed synchronously with step 103, that is, the first service server and the second service server can process the transaction branch synchronously, thereby ensuring the processing efficiency of the distributed transaction.

For the scenario where the first business client sends a service call request after processing its transaction branch, if the first business client determines that its transaction branch creation fails, or the transaction branch submission fails, it can be determined in advance that the distributed transaction execution failed . Therefore, the first business client does not need to send a service invocation request to the second business client, that is, the first business client may not need to perform step 108 again. In this way, it is possible to avoid wasting the computing resources of the second service server.

Similarly, for the scenario where the first business client first calls the service of the second business client and then processes its transaction branch, if the first business client determines that the service call of the second business client fails, the distribution can also be determined in advance The execution of the typed transaction failed. Therefore, the first service client does not need to perform step 103, step 104, step 106, and step 107. Therefore, it is possible to avoid wasting the computing resources of the first service server.

Step 120: The first business client sends a commit instruction or a rollback instruction for the distributed transaction to the transaction server according to the commit result and the service invocation response.

After the first business client receives the commit result of the transaction branch sent by the first network proxy node and the service call response sent by the second business client, if it is determined that the transaction branch in the first business server is successfully submitted, and the first Second, if the service call of the business client is successful, it can be determined that each transaction branch used to implement the distributed transaction is submitted successfully, and therefore, a commit instruction for the distributed transaction can be sent to the transaction server. The commit instruction is used to instruct to commit each transaction branch included in the distributed transaction.

If the first business client determines that the transaction branch commit in the first business server fails, or the service call of the second business client fails, it can send a rollback instruction for the distributed transaction to the transaction server, the rollback instruction Used to instruct to roll back each transaction branch included in the distributed transaction. Wherein, the commit instruction or the rollback instruction for the distributed transaction both carry the context of the distributed transaction.

Optionally, in this embodiment of the present application, the first business client may call services of multiple second business clients. Correspondingly, the first service client can receive the service invocation response sent by the multiple second service clients. Then, the first business client needs to determine that the transaction branch in the first business server is submitted successfully and the services of each second business client are successfully invoked before it can determine that the transaction branches used to implement the distributed transaction are all The commit is successful, and a commit instruction for the distributed transaction is sent. In the same way, if the first business client determines that the transaction branch submission in the first business server fails, or the service invocation of any second business client fails, it may send a rollback instruction for the distributed transaction.

For example, as shown in FIG. 2, the API module 0111 in the first business client 011a may also include a commit/rollback transaction API. The processing module 0115 of the first business client 011a can send a commit instruction R2 for the distributed transaction to the transaction server 02 by calling the commit transaction (Commit Transaction) API, or can call the rollback transaction (Rollback Transaction) API , Send a rollback instruction R2 for the distributed transaction to the transaction server 02. Referring to FIG. 2, it can be seen that the commit or rollback instruction R2 for the distributed transaction can be transparently transmitted to the transaction server 02 by the transparent transmission module 0123 of the first network agent node 012a.

The input parameters of each API in the commit transaction API and the rollback transaction API may include the address of the transaction server and the identifier of the distributed transaction. And the return value of the commit transaction API is 0 to indicate that the commit is successful, and the return value of -1 can indicate that the commit failed. In the same way, the return value of the rollback transaction API is 0 to indicate that the rollback is successful, and the return value of -1 can indicate that the rollback failed. The data type of the return value of each API in the commit transaction API and the rollback transaction API may be an integer (int).

Optionally, if the first business client can determine that the distributed transaction has failed to execute according to the received submission result or the received partial service call response, it can directly send a rollback for the distributed transaction to the transaction server Command without waiting for all submission results and service call responses to be received before sending the rollback command. As a result, the processing efficiency of distributed transactions can be effectively improved.

Step 121: The transaction server sends a third commit instruction or a third rollback instruction for the transaction branch to the network agent node in each business server participating in the distributed transaction.

After the transaction server receives the commit instruction or rollback instruction for the distributed transaction sent by the first business client, it may first determine the various business servers participating in the distributed transaction and the transaction branch executed by each business server. Furthermore, the third commit instruction or the third rollback instruction for the transaction branch executed by the business server may be sent to the network agent node in each business server respectively. Both the third commit instruction and the third rollback instruction may carry an identifier of the transaction branch executed by the business server.

For example, referring to FIG. 2, it is assumed that the business servers participating in a distributed transaction include a first business server 01a and a second business server 01b, and the first business server 01a executes transaction branch 1 of the distributed transaction, and the second business server 01b Transaction branch 2 of the distributed transaction is executed. Then, after the transaction server 02 receives the commit instruction for the distributed transaction sent by the first business client 011a, it can send the third commit instruction Z1 for the transaction branch 1 to the first network proxy node 012a, and can send The second network agent node 012b sends a third commit instruction Z2 for the transaction branch 2. If the second service server 01b also invokes the service client in the third service server to execute transaction branch 3, the transaction server 02 also needs to send the first transaction branch 3 to the network agent node 012b in the third service server. 3. Submit instructions.

Step 122: The first network agent node processes the received instruction.

If the first network agent node receives the third commit instruction for the transaction branch sent by the transaction server, it can clear the transaction log of the distributed transaction according to the transaction branch identifier carried in the third commit instruction The identifier of the transaction branch and the corresponding data set.

If the first network agent node receives the third rollback instruction for the transaction branch sent by the transaction server, it can obtain it from the transaction log of the distributed transaction according to the transaction branch identifier carried in the third rollback instruction The corresponding data set. Then the first network agent node can create a data set rollback statement based on the data set, and execute the data set rollback statement in the first business database, thereby rolling back the transaction branch. That is, the first network agent node can restore the business data in the first business database to the state before executing the transaction branch by executing the data set rollback statement.

For example, if the database operation statement used to implement the transaction branch is an update statement, the data set rollback statement created by the first network agent node may also be an update statement. If the database operation statement used to implement the transaction branch is an insert statement, the data set rollback statement created by the first network agent node may be a delete statement. If the database operation statement used to implement the transaction branch is a delete statement, the data set rollback statement created by the first network agent node may be an insert statement.

Optionally, after receiving the third commit instruction or third rollback instruction sent by the transaction server, the second network proxy node may also process the received instruction through the method shown in step 122 above. This will not be repeated here. For example, referring to FIG. 2, the transaction branch processing module 0124 in each network agent node may be used to process the received instructions. Each network agent node can complete the second phase of the distributed transaction after processing the third commit instruction or third rollback instruction sent by the transaction server. This second phase may also be referred to as the commit phase or the execution phase.

Based on the above description, in the process of implementing the second phase of the distributed transaction, the commit or rollback of the transaction branch can be implemented by the network proxy node, and the business client only needs to call the commit/rollback transaction API , The API call is less intrusive to the business, that is, it has less impact on the original business logic of the business client, so it can effectively reduce the adaptation of the business client to the distributed transaction processing architecture to achieve distributed transformation. cost.

Optionally, if a certain network agent node has already performed a rollback operation due to a transaction branch creation failure or a transaction branch commit failure before the above step 122, then in the above step 122, the network agent node may no longer need to process the first step. Three rollback instructions.

Alternatively, each network agent node may also send the commit result of the transaction branch to the transaction server after the above step 117, and the transaction server may then determine whether the transaction branch in each business server is executed successfully according to the commit result. Correspondingly, in the above step 121, the transaction server may only send the third rollback instruction to the network agent node in the business server that has successfully executed the transaction branch, and does not need to send the third rollback instruction to the network agent node in the business server that has failed to execute the transaction branch. Send the third rollback instruction.

In summary, the embodiments of the present application provide a distributed transaction processing method. In the distributed transaction processing method, the database operation instructions sent by the business client to the business database can carry the context of the distributed transaction. The network agent node can create and process transaction branches based on the context of the distributed transaction and the database operation statement. Since transaction branches can be created and processed through network proxy nodes, there is no need for the business client to deploy interfaces for creating and processing transaction branches (such as try, confirm, and cancel interfaces), thereby effectively reducing the application of business clients to distributed The development cost of the transaction processing system.

Moreover, compared with the traditional TCC technology, in the solution provided by the embodiments of this application, in the process of realizing distributed transactions, the creation and processing of transaction branches can be realized by network proxy nodes, and the business client only needs to call to start the transaction. API, operation instruction creation API, and submit/roll back transaction API. The invocation of the above API is less intrusive to the business, that is, it has less impact on the original business logic of the business client, so it can effectively reduce the business client’s platform The distributed transaction processing architecture is adapted to the platform as a service (platform as a service, PaaS) platform to realize the cost of the distributed transformation of the service and improve the efficiency of the distributed transformation of the business client. Moreover, the above-mentioned startup transaction API, operation instruction creation API, and commit/rollback transaction API can all be provided by the PaaS platform. Since the functions of the above-mentioned API are relatively simple, multiple programming languages can be supported. This can ensure that business clients developed and implemented in different programming languages can deploy the above APIs when performing distributed transformations, so that a distributed transaction processing system across programming languages can be realized at a lower development cost.

In addition, since each business client in the distributed transaction processing system uses a database protocol to interact with the business database, the network agent node can create and process transaction branches through database operation instructions that carry the context of distributed transactions. Therefore, even if each business client in the distributed transaction processing system is developed and implemented using different programming languages, it will not affect the creation and processing of transaction branches by the network agent node. That is, based on the solution provided by the embodiment of the present application, the network agent node only needs to support the database protocol to adapt to the business client developed using different programming languages. It can be seen from this that the solution of the embodiment of the present application can enable the distributed transaction processing system across programming languages to achieve data consistency of distributed transactions at a lower cost.

FIG. 4 is a flowchart of another distributed transaction processing method provided by an embodiment of the present application, and the method can be applied to the system shown in FIG. 1 or FIG. 2. In the embodiment of the present application, the method is applied to the system shown in FIG. 2 and the transaction branch to be executed by the first business client includes multiple operations on the database as an example for description. Referring to Figure 4, the method may include:

Step 201: The first business client sends a creation request of a distributed transaction to the transaction server.

For the implementation process of step 201, reference may be made to the related description of step 101 in the embodiment shown in FIG. 3, which will not be repeated here.

Step 202: The transaction server sends an identifier assigned to the distributed transaction to the first service client.

For the implementation process of step 202, reference may be made to the related description of step 102 in the embodiment shown in FIG. 3, which will not be repeated here.

Step 203: The first business client generates multiple database operation statements for implementing transaction branches to be executed in the distributed transaction.

For the implementation process of step 203, reference may be made to the related description of step 103 in the embodiment shown in FIG. 3, which will not be repeated here.

Step 204: The first service client sends a second setting instruction to the first service database.

Since the number of database operation statements used to implement the transaction branch is greater than 1, the first business client can determine that the multiple database operation statements are all executed before submitting the transaction branch, and then can send to the first business database The second setting instruction is used to instruct to set the automatic submission function of the first business database to the closed state. For example, referring to FIG. 2, the processing module 0115 of the first service client 011a may instruct the database driver 0113 to send the second setting instruction to the first service database 03a when detecting that the number of database operation sentences is greater than one.

Step 205: The first network agent node obtains the second setting instruction, and records that the automatic submission function of the first service database is in a closed state.

Since the second setting instruction sent by the first service client to the first service database needs to be forwarded by the first network proxy node, the first network proxy node can obtain the second setting instruction and record it according to the second setting instruction The automatic submission function of the first business database is closed. In addition, the first network agent node may forward the second setting instruction to the first service database after completing the status recording. The first network agent node records that the automatic submission function of the first business database is in the off state, and can determine that the number of database operation statements used to implement transaction branching is greater than one. Furthermore, after receiving the database operation instruction, the first network agent node can determine which method should be used to obtain the lock information of the transaction branch, and create the transaction branch.

For example, the first network agent node may record the status identifier of the first service database, and the first network agent node may set the status identifier to false after obtaining the second setting instruction to indicate the first service The automatic submission function of the database is closed. For example, the transaction branch processing module 0124 in the first network agent node 012a may record the status identifier of the first service database.

Step 206: The first business client generates a plurality of database operation instructions based on the plurality of database operation statements and the context of the distributed transaction.

In the embodiment of the present application, for each database operation statement used to implement the transaction branch, the first business client can combine the context of the distributed transaction with the database operation statement to generate a database operation instruction. Since in this embodiment, the number of database operation statements used to implement the transaction branch is greater than 1, the first business client can generate multiple database operation instructions based on the multiple database operation statements. Wherein, each database operation instruction includes at least one database operation statement and the context of the distributed transaction. In the embodiments of the present application, at least one refers to one or more, and multiple refers to two or more. For example, each database operation instruction may include a database operation statement. For the process of generating each database operation instruction, reference may be made to the related description of step 106 in the embodiment shown in FIG. 3, which will not be repeated here.

Step 207: The first service client sends multiple database operation instructions to the first service database.

After the first business client generates the multiple database operation instructions, it can send the multiple database operation instructions to the first business database in sequence.

For example, referring to FIG. 2, the database driver 0113 in the first network agent node 012a may send multiple database operation instructions to the first service database 03a.

Step 208: The first business client sends a service invocation request to the second business client.

For the implementation process of step 208, reference may be made to the related description of step 108 in the embodiment shown in FIG. 3, which will not be repeated here.

Step 209: The first network agent node obtains the multiple database operation instructions, and obtains the data set targeted by each database operation statement from the first service database.

For each acquired database operation instruction, the first network agent node can parse the database operation statement from the database operation instruction, and then obtain the data set targeted by the database operation statement from the first business database. For the process of obtaining the data set targeted by each database operation sentence, reference may be made to the related description of step 109 in the embodiment shown in FIG. 3, which will not be repeated here.

Step 210: The first network agent node obtains lock information of the data set targeted by each database operation statement.

The lock information of the data set targeted by each database operation statement may include the table name of the data table where the data set is located, and the primary key of the row where the data set is located. For example, the transaction branch processing module 0124 in the first network agent node 012a can obtain the lock information of the data set targeted by each database operation statement.

Step 211: The first network agent node stores the data set targeted by each database operation statement and the lock information of the data set targeted by each database operation statement.

In this embodiment of the application, if the first network agent node determines that the automatic submission function of the first service database is in the off state, it can determine that the number of database operation statements used to implement transaction branching is greater than one. Furthermore, the first network agent node can determine that only after the multiple database operation statements used to implement the transaction branch are executed successfully, can the transaction branch be created according to the acquired lock information request. Therefore, the first network agent node needs to store The data set targeted by each database operation statement and the lock information of the data set targeted by each database operation statement. In addition, in order to facilitate subsequent creation or rollback of a transaction branch, the first network agent node may use the identifier of the distributed transaction to implement the data set targeted by the multiple database operation statements of the transaction branch, and the lock information of the data set Perform corresponding storage. That is, the first network agent node can merge and store the data sets targeted by multiple database operation statements used to implement the same transaction branch, and can lock the data sets targeted by the multiple database operation statements. Information is merged and stored. For example, the transaction branch processing module 0124 in the first network agent node 012a may store the data set targeted by each database operation statement and the lock information of the data set targeted by each database operation statement.

For example, assuming that the identifier of the distributed transaction is ID1, in the above step 203, the database operation statements generated by the first business client to implement the transaction branch to be executed include Y1, Y2, and Y3. The three database operation statements are The targeted data sets are D1, D2, and D3, and the lock information of the three data sets are S1, S2, and S3, respectively. Then the first network agent node can store the identification ID1 of the distributed transaction, the corresponding relationship with the collection of data sets D1, D2, and D3, and the collection of lock information S1, S2, and S3.

Step 212: The first network agent node executes each database operation statement in the first service database.

For example, after the transaction branch processing module 0124 in the first network agent node 012a stores the data set targeted by each database operation statement and the lock information of the data set targeted by each database operation statement, it can use the database driver 0125 to access In the first service data 03a, the database operation statement in each database operation instruction is executed.

Step 213: The first network agent node sends the execution result of each database operation statement to the first service client.

Each time the first network agent node completes a database operation sentence, it can send the execution result of the database operation sentence to the first business client. The execution result may be used to indicate the success or failure of the execution of the database operation statement. For example, the transaction branch processing module 0124 in the first network agent node 012a may send the execution result of each database operation statement to the first service client 011a.

Step 214: The first business client detects whether each database operation statement is executed successfully.

The first service client can detect whether each database operation statement used to implement the transaction branch is executed successfully according to the execution result sent by the first network agent node. If the execution of any database operation statement fails, the first business client can execute step 215; if each database operation statement is executed successfully, the first business client can execute step 218. For example, the processing module 0115 in the first business client 011a can detect whether each database operation statement is executed successfully.

Step 215: The first service client sends a second rollback instruction for the transaction branch to the first service database.

If the first business client detects that any database operation statement has failed to execute, it can determine that the transaction branch has not been executed successfully, and therefore can send a second rollback instruction for the transaction branch to the first business database. For example, the processing module 0115 in the first business client 011a may instruct the database driver 0113 to send the second rollback instruction when it detects that any database operation statement fails to execute.

Step 216: The first network agent node deletes the stored data set and lock information.

If the first network agent node obtains the second rollback instruction for the transaction branch sent by the first business client, it can determine that the transaction branch has failed to execute, so it can delete the stored database operation statement for each The data set, and the lock information of the data set targeted by each database operation statement, to avoid the data set and lock information occupying too much storage space. For example, the transaction branch processing module 0124 in the first network agent node 012a can delete the stored data set for each database operation statement and the lock information of the data set for each database operation statement.

Step 217: The first network proxy node sends the second rollback instruction to the first service database.

After receiving the second rollback instruction, the first network proxy node may also forward the second rollback instruction to the first service database. After the first service database receives the second rollback instruction, the transaction branch can be rolled back. For example, the transaction branch processing module 0124 in the first network agent node 012a may send the second rollback instruction to the first service database 03a through the database driver 0125.

Step 218: The first service client sends a second commit instruction for the transaction branch to the first service database.

If the first business client detects that multiple database operation statements used to implement the transaction branch are executed successfully, it can determine that the transaction branch is executed successfully, and therefore can send a second commit instruction for the transaction branch to the first business database . For example, the processing module 0115 of the first business client 011a may instruct the database driver 0113 to send the second commit instruction when detecting that multiple database operation statements used to implement the transaction branch are executed successfully.

Step 219: The first network agent node obtains the lock information of the data set targeted by each stored database operation statement.

If the first network agent node obtains the second commit instruction for the transaction branch sent by the first service client, it can obtain the lock information of the data set for each database operation statement stored in step 211. The lock information of the data set targeted by the multiple database operation statements acquired by the first network agent node is the lock information of the transaction branch. For example, the transaction branch processing module 0124 in the first network agent node 012a may obtain the lock information of the data set for which each database operation statement is stored.

Optionally, if the database operation statement in the database operation instruction received by the first network agent node does not change the data in the first service database, for example, when the database operation statement is a query statement, the first network agent node does not The lock information of the data set targeted by the database operation statement will be acquired and stored. Therefore, after the first network agent node obtains the second submission instruction, if it does not obtain the lock information of its pre-stored data set, that is, the first network agent node does not store any data set before receiving the second submission instruction If the lock information is displayed, the first network agent node can directly forward the second submission instruction without performing subsequent operations.

Step 220: The first network agent node sends a transaction branch creation request to the transaction server.

After obtaining the lock information of the transaction branch, the first network agent node can send a transaction branch creation request to the transaction server. The transaction branch creation request may include the lock information of the data set and the identification of the distributed transaction. For example, the transaction branch processing module 0124 in the first network agent node 012a may send a transaction branch creation request to the transaction server 02.

After the first network agent node sends the transaction branch creation request, the transaction server can detect whether the transaction branch can be created according to the lock information carried in the creation request. In this scenario, the lock information of the transaction branch carried in the creation request includes the lock information of multiple data sets, so the transaction server can determine that the lock information of each data set is different from the lock information of other transaction branches stored in it. , Make sure that the transaction branch can be created. If the transaction server detects that the lock information of any data set is the same as the lock information of other transaction branches stored in it, it can determine that the transaction branch cannot be created.

After step 220, the distributed transaction processing system can continue to execute the method shown in step 112 to step 122 in the embodiment shown in FIG. 3, so it will not be repeated here.

In summary, the embodiment of the present application provides a distributed transaction processing method. In the distributed transaction processing method, the network agent node can accurately determine the status of the automatic submission function of the service database to implement the transaction. Whether the number of branched database operation statements is greater than 1. Furthermore, the network agent node can obtain lock information and create transaction branches in different ways according to the number of database operation statements, thereby effectively improving the flexibility of creating transaction branches.

In the distributed transaction processing system provided by the embodiment of the present application, the network agent node in each service server can intercept the data packet sent by the service client in the service server, and can detect the data packet sent by the service client. Whether the receiver is a business database, and if the receiver of the data packet is a business database, the network proxy node can obtain the data packet and analyze the data packet. If the receiver of the data packet is not the service database, the network proxy node can directly forward the data packet.

In order to effectively intercept the data packets sent by the business client to the business database, referring to Figure 5, the network agent node in each business server can also perform the following operations:

Step 301: Intercept the data packet sent by the service client.

Step 302: Detect whether the data packet is a new connection request.

For each data packet sent by the business client, the network proxy node can detect whether the data packet is a new connection request. If the data packet is a new connection request, the network proxy node can perform step 303; if the data packet is not a new connection request, the network proxy node can perform step 306.

Step 303: Create a new connection.

If the data packet sent by the service client is a new connection request, the network proxy node can establish a new connection with the connecting party requested by the new connection request. For example, the network proxy node can create a socket connection with the connecting party. After that, the network agent node may perform step 304.

Step 304: Detect whether the connection is a connection with a service database.

After completing the connection with the connecting party, the network agent node can continue to detect whether the connection is a connection with the service database. If the connection is a connection with a service database, step 305 can be executed. If the connection is not a connection to the service database, then step 301 can be continued, that is, the data packet sent by the service client is continued to be intercepted. For example, if the connection is a connection with a transaction server, the network agent node may continue to perform step 301.

Optionally, the network agent node may detect whether the connection is a connection with the service database according to the connection agreement between the service client and the connection party.

Step 305: Mark the connection.

If the network agent node detects that the connection is a connection to the service database, it can mark the connection. For example, the network agent node can add a detection mark in the attribute description field of the connection, so as to mark the connection. By marking the connection to the service database, it is convenient to quickly detect whether the receiver of the data packet sent by the service client is the service database. After that, the network agent node can continue to perform step 301, that is, continue to intercept data packets sent by the service client.

Step 306: Detect whether the data packet belongs to the marked connection.

In the above step 302, if the network agent node detects that the data packet is not a new connection request, it can continue to detect whether the data packet belongs to a marked connection, that is, continue to detect whether the data packet is sent to the service database data pack. For example, the network agent node can detect whether a detection mark is added in the attribute description field of the connection to which the data packet belongs. If the detection mark is added, it can be determined that the data packet belongs to the marked connection; if the detection mark is not added, it can be determined that the data packet does not belong to the marked connection.

If the data packet belongs to a marked connection, the network proxy node can determine that the data packet is a data packet sent to the service database, so step 307 can be performed; if the data packet does not belong to a marked connection, the network proxy node can determine the The data packet is not a data packet sent to the service database, so step 308 can be executed.

For example, referring to FIG. 2, each network agent node may include a connection management module 0121, and the above steps 301 to 306 may be implemented by the connection management module 0121.

Step 307: Obtain and parse the data packet.

If the network agent node detects that the data packet belongs to a marked connection, it can obtain and parse the data packet. For example, the network agent node can parse the data packet based on the database protocol. Referring to FIG. 2, each network agent node may include a parsing module 0122, and the parsing module 0122 may parse the data packet.

Optionally, the network proxy node may first detect whether the data packet is a setting instruction for setting the automatic submission status of the business database. If the data packet is the setting instruction, the network proxy node may execute the above step 105 or step 205. Indicates the method. If the data packet is not the setting instruction, the network agent node can continue to detect whether the data packet is a commit instruction or a rollback instruction for a transaction branch.

If the data packet is a commit instruction for a transaction branch, the network proxy node can execute the methods shown in steps 218 and 219; if the data packet is a rollback instruction for a transaction branch, the network proxy node can perform the above steps 216 shows the method. If the data packet is not a commit instruction or a rollback instruction for a transaction branch, the network agent node can continue to detect whether the data packet is a database operation instruction carrying the context of a distributed transaction.

If the data packet does not carry the context of the distributed transaction, the network agent node can directly forward the data packet to the service database; if the data packet is a database operation instruction carrying the context of the distributed transaction, the network agent node can Perform the method shown in step 109 or step 209 above.

In the embodiment of this application, since the network proxy node only needs to parse the data packets sent by the business client to the business database, and the business clients all interact with the business database based on the database protocol, the network proxy node only needs to support the database protocol It can be adapted to business clients developed in different programming languages. That is, the solutions provided by the embodiments of the present application can be applied to a distributed transaction processing system across programming languages.

Step 308: Transparently transmit the data packet.

If the network agent node detects that the data packet does not belong to the marked connection, it can directly transparently transmit the data packet. For example, if the data packet is a data packet sent to a transaction server or other business servers, the network agent node can directly transparently transmit the data packet. Referring to FIG. 2, each network agent node may include a transparent transmission module 0123, and the transparent transmission module 0123 may transparently transmit the data packet.

In summary, in the method for the network agent node to intercept data packets provided by the embodiments of the present application, since the network agent node can mark the connection when establishing a new connection with the service database, it can facilitate the subsequent rapid detection of the data sent by the service client Whether the receiver of the packet is the service database, thereby effectively improving the efficiency of detecting the receiver of the data packet. In addition, since the network proxy node can realize the creation and processing of transaction branches according to the data packets sent by the business client to the business database, the network proxy node only needs to parse the data packets sent by the business client to the business database. Data packets to other receivers can be directly transmitted transparently. This can avoid increasing the number of data packets parsed by the network proxy node, and improve the efficiency of the network proxy node in parsing data packets.

Optionally, the sequence of the steps of the distributed transaction processing method provided in the embodiment of the present application can be adjusted appropriately, and the steps can also be increased or decreased accordingly according to the situation. For example, step 106 can be performed before step 105, step 206 can be performed before step 205; step 108 can be performed before step 107, and step 208 can be performed before step 207. Or step 115 and step 116 can be performed before step 111. Alternatively, step 119 may also be performed before step 118. Alternatively, step 108 may be performed after step 109, and step 208 may also be performed after step 209. For example, step 108 may be performed after step 118, and step 208 may be performed after step 218. Any person familiar with the technical field can easily think of a method of change within the technical scope disclosed in this application, which should be covered by the protection scope of this application, and therefore will not be repeated.

Moreover, compared with the traditional TCC technology, in the solution provided by the embodiments of this application, in the process of realizing distributed transactions, the creation and processing of transaction branches can be realized by network proxy nodes, and the business client only needs to call to start the transaction. API, operation instruction creation API, and submit/roll back transaction API. The invocation of the above API is less intrusive to the business, that is, it has less impact on the original business logic of the business client, so it can effectively reduce the business client’s platform The distributed transaction processing architecture is adapted to the PaaS platform as a service to realize the cost of the distributed transformation of the business and improve the efficiency of the distributed transformation of the business client. Moreover, the above-mentioned startup transaction API, operation instruction creation API, and commit/rollback transaction API can all be provided by the PaaS platform. Since the functions of the above-mentioned API are relatively simple, multiple programming languages can be supported. This can ensure that business clients developed and implemented in different programming languages can deploy the above APIs when performing distributed transformations, so that a distributed transaction processing system across programming languages can be realized at a lower development cost.

The embodiment of the present application provides a network agent node, which can be deployed in a business server of a distributed transaction processing system, for example, can be deployed in a business server of a distributed transaction processing system as shown in FIG. 1 or FIG. 2 01 in. It can be seen with reference to FIGS. 1 and 2 that the distributed transaction processing system further includes a transaction server 02 and a plurality of service databases 03, and a service client 011 is also deployed in the service server 01. As shown in FIG. 2, the network agent node includes: a connection management module 0121, a parsing module 0122, a transparent transmission module 0123, a transaction branch processing module 0124, and a database driver 0125.

The connection management module 0121 is configured to receive one or more database operation instructions sent by the business client, and send the one or more database operation instructions to the analysis module 0122.

The parsing module 0122 is used to obtain and analyze each database operation instruction sent by the business client. Each database operation instruction includes: a database operation statement and a distributed transaction context, wherein the one or more database operation instructions The included database operation statement is used to implement the transaction branch of the distributed transaction, and the context of the distributed transaction includes the identifier of the distributed transaction. The parsing module 0122 is also used to send the parsed database operation statement and the context of the distributed transaction to the transaction branch processing module 0124. For the functional realization of the parsing module 0122, reference may be made to the related descriptions of step 109 and step 209 in the foregoing method embodiment.

The transaction branch processing module 0124 is configured to: execute the database operation statement in the business database; and send a transaction branch creation request to the transaction server, and the transaction branch creation request includes the identifier of the distributed transaction. For the functional realization of the transaction branch processing module 0124, reference may be made to the related description of step 111 and step 220 in the foregoing method embodiment.

Optionally, the transaction branch processing module 0124 is also used to: obtain lock information of a data set, the data set being targeted by a database operation statement included in the one or more database operation instructions, and the lock information of the data set The data set is identified in the business database; correspondingly, the transaction branch creation request also includes the lock information of the data set.

Optionally, the transaction branch processing module 0124 may be used to: determine that the automatic submission function of the business database is in an on state, and after receiving the first creation response sent by the transaction server indicating that the transaction branch is successfully created, The database operation statements included in each database operation instruction are executed in the business database. For the functional realization of the transaction branch processing module 0124, reference may also be made to the related description of step 115 in the foregoing method embodiment.

The transaction branch processing module 0124 may be further configured to: after receiving the first creation response sent by the transaction server indicating that the transaction branch is successfully created, send the first commit instruction for the transaction branch to the business database.

Optionally, the transaction branch processing module 0124 may be further configured to: after receiving a second creation response sent by the transaction server indicating that the transaction branch creation fails, send to the business database the first creation response for the transaction branch. A rollback instruction. For the functional realization of the transaction branch processing module 0124, reference may also be made to the related descriptions of step 112 to step 114 and step 117 in the foregoing method embodiment.

Optionally, the transaction branch processing module 0124 can also be used to determine that the automatic submission function of the business database is turned off, and send the execution result of the database operation statement included in each database operation instruction to the business client; After the second commit instruction for the transaction branch sent by the business client, the lock information of the data set is acquired.

Wherein, if the number of database operation statements used to implement the transaction branch is greater than 1, the automatic submission function of the business database is set to the closed state by the business client; the second submission instruction is that the business client is The execution result is determined to be sent after each database operation statement used to implement the transaction branch is successfully executed. For the functional realization of the transaction branch processing module 0124, reference may also be made to the related descriptions of step 210 to step 213 and step 219 in the foregoing method embodiment.

Optionally, the transaction branch processing module 0124 can also be used to obtain the transaction branch sent by the business client after the execution result of the database operation statement included in each database operation instruction is sent to the business client. The second rollback instruction is to delete the lock information of the data set, and send the second rollback instruction to the business database; wherein, the second rollback instruction is that the business client determines any one of the transaction branches used to implement the transaction branch. Sent after the execution of the database operation statement fails. Wherein, both the second commit instruction and the second rollback instruction may be sent to the transaction branch processing module 0124 through the connection management module 0121 and the parsing module 0122. For the functional realization of the transaction branch processing module 0124, reference may also be made to the related description of step 216 and step 217 in the foregoing method embodiment.

Optionally, the transaction branch processing module 0124 may be used to: obtain the first setting instruction sent by the business client, and record the automatic submission function of the business database as the on state according to the first setting instruction; wherein, the first setting The instruction is sent when the business client determines that the number of database operation statements used to implement the transaction branch is equal to 1.

Optionally, the transaction branch processing module 0124 may be used to: obtain a second setting instruction sent by the business client, and record according to the second setting instruction that the automatic submission function of the business database is turned off; the second setting instruction is Sent when the business client determines that the number of database operation statements used to implement the transaction branch is greater than 1. For the functional realization of the transaction branch processing module 0124, reference may also be made to the related descriptions of step 105 and step 205 in the foregoing method embodiment.

Optionally, the first creation response carries an identifier assigned by the transaction server to the transaction branch; the transaction branch processing module 0124 can also be used to:

After receiving the first creation response, store the identifier of the transaction branch and the corresponding relationship of the data set in the transaction log of the distributed transaction; receive the third commit instruction for the transaction branch sent by the transaction server, and clean up The identifier of the transaction branch and the data set recorded in the transaction log. Or, receiving the third rollback instruction for the transaction branch sent by the transaction server, obtaining the data set from the transaction log according to the identifier of the transaction branch, and rolling back the transaction branch according to the data set.

Wherein, the third commit instruction is sent by the transaction server after receiving the commit instruction for the distributed transaction sent by the business client, and the third rollback instruction is sent by the transaction server after receiving the business client. Sent after the rollback instruction for the distributed transaction. For the functional implementation of the transaction branch processing module 0124, reference may also be made to the related descriptions of step 116 and step 122 in the foregoing method embodiment.

Optionally, the transaction branch processing module 0124 can also be used to:

After sending the first commit instruction for the transaction branch to the service database, the lock information of the data set is deleted. If it is determined that the transaction branch is submitted successfully, then send to the business client a commit result indicating that the transaction branch is submitted successfully; if it is determined that the transaction branch has failed to commit, then send to the business client to indicate that the transaction branch failed to commit Send the fourth rollback instruction for the transaction branch to the business database, and send a notification message carrying the transaction branch identifier to the transaction server, and the notification message is used to instruct the transaction server to delete the transaction branch Lock information. For the functional realization of the transaction branch processing module 0124, reference may also be made to the related description of step 118 in the foregoing method embodiment.

Optionally, the connection management module 0121 can be used to: if it is detected that the recipient of the data packet sent by the service client is the service database, send the data packet to the parsing module 0122; if the service client is detected If the recipient of the sent data packet is not the service database, the data packet is sent to the transparent transmission module 0123. For the function implementation of the connection management module 0121, reference may be made to the related descriptions of step 301 to step 306 in the foregoing method embodiment.

The parsing module 0122 is used for parsing the data packet. For the functional realization of the parsing module 0122, reference may be made to the related description of step 307 in the foregoing method embodiment.

The transparent transmission module 0123 is configured to forward the data packet to the receiver, that is, transparently transmit the data packet. For the function implementation of the transparent transmission module 0123, reference may be made to the related description of step 308 in the foregoing method embodiment.

In summary, the embodiments of the present application provide a network agent node, which can create and process transaction branches according to the context of distributed transactions and database operation statements carried in database operation instructions. Since network agent nodes can create and process transaction branches, there is no need for business clients to deploy interfaces for creating and processing transaction branches (such as try, confirm, and cancel interfaces), thereby effectively reducing the application of business clients to distributed transaction processing systems Development costs.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of each module in the network agent node described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

The embodiment of the present application provides a business client, which can be deployed in a business server of a distributed transaction processing system, for example, can be deployed in a business server of a distributed transaction processing system as shown in FIG. 1 or FIG. 2 01. It can be seen with reference to Fig. 1 and Fig. 2 that the distributed transaction processing system further includes a transaction server 02 and a plurality of service databases 03, and a network agent node is also deployed in the service server 01. As shown in FIG. 2, the business client may include: an API module 0111, a communication module 0112, a database driver 0113, a service calling module 0114, and a processing module 0115. In the following description, the service client is the first service client 011a in the first service server 01a, and the first service server 01a further includes the first network proxy node 012a as an example.

The processing module 0115 is configured to generate one or more database operation statements for implementing the transaction branch according to the transaction branch to be executed by the first business client in the distributed transaction. For the functional realization of the processing module 0115, reference may be made to the related descriptions of step 103 and step 203 in the foregoing method embodiment.

The API module 0111 is used to generate one or more database operation instructions based on the one or more database operation statements and the context of the distributed transaction, wherein each database operation instruction includes: at least one database operation statement and the distributed transaction The context, which includes the identity of the distributed transaction. For the functional realization of the API module 0111, reference may be made to the related descriptions of step 106 and step 206 in the foregoing method embodiment.

The database driver 0113 is configured to send the one or more database operation instructions to the first service database, and the one or more database operation instructions are used for the first network agent node that obtains the one or more database operation instructions Create and process the transaction branch. For the function implementation of the database driver 0113, reference may be made to the related descriptions of step 107 and step 207 in the foregoing method embodiment.

Optionally, the API module 0111 is further configured to send the creation request of the distributed transaction to the transaction server in response to the service request; and receive the identifier of the distributed transaction sent by the transaction server. For the functional realization of the API module 0111, reference may also be made to the related descriptions of step 101, step 102, step 201, and step 202 in the foregoing method embodiment.

The service invocation module 0114 is configured to send a service invocation request to a second business client participating in the distributed transaction, and the service invocation request carries an identifier of the distributed transaction. For the function implementation of the service calling module 0114, reference may be made to the related descriptions of step 108 and step 208 in the foregoing method embodiment.

Optionally, the processing module 0115 is further configured to determine the transaction branch to be executed by the first business client in the distributed transaction according to the business request.

The processing module 0115 is further configured to receive the commit result of the transaction branch sent by the first network proxy node, and receive the service invocation response sent by the second business client in response to the service invocation request.

The processing module 0115 can also be used to instruct the API module 0111 to send a commit instruction or a rollback instruction for the distributed transaction to the transaction server according to the commit result and the service call response. The commit instruction is used to instruct to submit each transaction branch included in the distributed transaction, and the commit instruction for the distributed transaction is used to instruct to roll back each transaction branch included in the distributed transaction. For the functional realization of the processing module 0115, reference may also be made to the related description of step 118 to step 120 in the foregoing method embodiment.

Optionally, the processing module 0115 can also be used to: receive a service invocation request sent by a second business client, the service invocation request carries the context of the distributed transaction; according to the service invocation request, determine the distributed transaction The transaction branch to be executed by the first business client in the transaction.

Optionally, the processing module 0115 can also be used to:

It is determined that the number of database operation statements used to implement the transaction branch is equal to 1, and the database driver 0113 is instructed to send a first setting instruction to the first business database, and the first setting instruction is used to instruct to set the automatic commit function to the on state of.

Or, determining that the number of database operation statements used to implement the transaction branch is greater than 1, instructing the database driver 0113 to send a second setting instruction to the first business database, and the second setting instruction is used to instruct to set the automatic commit function to Closed. For the functional realization of the processing module 0115, reference may also be made to the related descriptions of step 104 and step 204 in the foregoing method embodiment.

Optionally, the processing module 0115 can also be used to:

After instructing the database driver 0113 to send to the first service database the second setting instruction for instructing the automatic submission function to be set to the off state, the database operation statement included in each database operation instruction sent by the first network agent node is received Results of the;

According to the execution result, it is determined that each database operation statement used to implement the transaction branch is executed successfully, and the database driver 0113 is instructed to send a second commit instruction for the transaction branch to the first service database.

Or, according to the execution result, it is determined that the execution of any of the database operation statements used to implement the transaction branch fails, and the database driver 0113 is instructed to send the second rollback instruction for the transaction branch to the first service database. For the functional realization of the processing module 0115, reference may also be made to the related descriptions of step 213 to step 215 and step 218 in the foregoing method embodiment.

Optionally, each request or instruction sent by the API module 0111 and the database driver 0113 in the business client is sent through the communication module 0112.

In summary, the embodiments of the present application provide a business client. The database operation instructions sent by the business client to the business database can carry the context of the distributed transaction, so that the network proxy node can be based on the distributed transaction. Context, and the database operation statement to create and process transaction branches. Since transaction branches can be created and processed through network proxy nodes, there is no need for the business client to deploy interfaces for creating and processing transaction branches (such as try, confirm, and cancel interfaces), thereby effectively reducing the application of business clients to distributed The development cost of the transaction processing system.

Those skilled in the art can clearly understand that, for the convenience and concise description, the specific working process of each module in the business client described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

It should be understood that the network proxy node and service client provided in the embodiments of the present application can also be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. The distributed transaction processing method provided by the foregoing method embodiment can also be implemented by software. When the distributed transaction processing method provided by the foregoing method embodiment is implemented by software, the various modules in the network proxy node and the business client can also be implemented. It is a software module.

The following describes the architecture of the distributed transaction processing system provided by the embodiments of the present application. As shown in FIG. 6, the distributed transaction processing system may be a server cluster. The server cluster includes at least one server 1000, and each server 1000 Establish a communication path through the communication network.

Each server 1000 includes a bus 1001, a processor 1002, a communication interface 1003, and a memory 1004. The processor 1002, the memory 1004, and the communication interface 1003 communicate with each other through the bus 1001.

The processor 1002 may be composed of one or more general-purpose processors, such as a central processing unit (CPU), or a combination of a CPU and a hardware chip. The above-mentioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above-mentioned PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (generic array logic, GAL), or any combination thereof.

The memory 1004 may include a volatile memory (volatile memory), such as random access memory (RAM). The memory 1004 may also include non-volatile memory (NVM), such as read-only memory (read-only memory, ROM), flash memory, hard disk drive (HDD), or solid-state drive (solid-disk drive, HDD). state drive, SSD). The memory 1004 may also include a combination of the above types.

The memory 1004 stores executable codes, and the processor 1002 can read the executable codes in the memory 1004 to implement functions, and can also communicate with other servers through the communication interface 1003.

In the embodiment of the present application, the processor 1002 in each server 1000 can implement one or more of the following functions: the function of at least one service client 011, the function of at least one network agent node 012, and the transaction server 02 The functions of at least one business database 03. That is, the processor 1002 in each server 1000 may only implement the functions of one node in the business client 011, the network agent node 012, the transaction server 02, and the business database 03, or may also implement the functions of multiple nodes. . Correspondingly, the memory 1004 stores modules for realizing the functions of the processor 1002.

In the embodiment of the present application, the processors 1001 in the multiple servers 1000 may coordinate work to execute the distributed transaction processing method provided in the embodiment of the present application.

Optionally, as shown in FIG. 7, the distributed transaction processing system may include multiple service servers 2000, one transaction server 3000, and multiple database servers 4000. Only two service servers 2000 and two database servers 4000 are schematically shown in FIG. 7.

Among them, each service server 2000 includes a bus 2001, a processor 2002, a communication interface 2003, and a memory 2004. The processor 2002, the memory 2004 and the communication interface 2003 communicate through a bus 2001. The transaction server 3000 includes a bus 3001, a processor 3002, a communication interface 3003, and a memory 3004. The processor 3002, the memory 3004, and the communication interface 3003 communicate with each other through the bus 3001. Each database service server 4000 includes a bus 4001, a processor 4002, a communication interface 4003, and a memory 4004. The processor 4002, the memory 4004, and the communication interface 4003 communicate with each other through the bus 4001. For the types of the processor 2002, the processor 3002, and the processor 4002, reference may be made to the relevant description of the processor 1002, which will not be repeated here. For the types of the memory 2004, the memory 3004, and the memory 4004, please refer to the relevant description of the memory 1004, which will not be repeated here.

In the embodiment of the present application, the processor 2002 in each service server 2000 can realize the function of a service client 011 and the function of a network agent node 012 by running a computer program in the memory 2004. Correspondingly, as shown in FIG. 7, the memory 2004 in each service server 2000 stores various modules of the service client 011 (for example, the API module 0111, the communication module 0112, the database driver 0113, and the service calling module 0114), and the network The various modules of the proxy node 012 (for example, the connection management module 0121, the analysis module 0122, the transparent transmission module 0123, the transaction branch processing module 0124, and the database driver 0125).

The processor 3002 in the transaction server 3000 can implement the functions of the transaction server 02 in the foregoing embodiment by running a computer program in the memory 3004. The processor 4002 in each database server 4000 can implement the function of the service database 03 in the foregoing embodiment by running the computer program in the memory 4004.

In summary, the embodiment of the present application provides a distributed transaction processing system. Each service server in the system includes a service client and a network agent node. The network agent node can intercept data packets sent by the service client. . Among them, the database operation instruction sent by the business client to the business database may carry the context of the distributed transaction, so that the network agent node can create and process the transaction branch based on the context of the distributed transaction and the database operation statement. Since the transaction branch can be created and processed through the network proxy node, there is no need for the business client to deploy an interface for creating and processing the transaction branch, thereby effectively reducing the development cost of the business client applied to the distributed transaction processing system.

The embodiment of the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, and the instructions are executed by a processor to implement the steps executed by the network agent node in the foregoing method embodiments.

The embodiment of the present application also provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, and the instructions are executed by a processor to implement the steps executed by the business client in the foregoing method embodiments.

The embodiments of the present application also provide a computer program product containing instructions, which when the computer program product runs on a computer, cause the computer to execute the steps performed by the network agent node in the foregoing method embodiments.

The embodiments of the present application also provide a computer program product containing instructions, which when the computer program product runs on a computer, cause the computer to execute the steps executed by the business client in the foregoing method embodiments.

The above-mentioned embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented using software, the above-mentioned embodiments may be implemented in the form of a computer program product in whole or in part. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more sets of available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium. The semiconductor medium may be a solid state drive (SSD).

The foregoing descriptions are only optional embodiments of the application, and are not intended to limit the application. Any person skilled in the art can easily think of various equivalent modifications, equivalent substitutions, and equivalents within the technical scope disclosed in the application. Improvements, etc., should all be included in the scope of protection of this application.

Claims

A method for processing distributed transactions is characterized in that it is applied to a distributed transaction processing system. The distributed transaction processing system includes multiple service servers, transaction servers, and service databases, and each service server includes a network agent node and a service database. Client; the method includes:

The network agent node obtains one or more database operation instructions sent by the business client, each database operation instruction includes: a database operation statement and the context of the distributed transaction, and the one or more database operation instructions include The database operation statement of is used to implement the transaction branch of the distributed transaction, and the context of the distributed transaction includes the identifier of the distributed transaction;

The network agent node executes a database operation statement included in each database operation instruction in the service database;

The network agent node sends a transaction branch creation request to the transaction server, and the transaction branch creation request includes an identifier of the distributed transaction.
The method according to claim 1, wherein the method further comprises:

The network agent node obtains lock information of a data set, where the data set is targeted by a database operation statement included in the one or more database operation instructions, and the lock information of the data set is used in the service database Identify the data set;

The transaction branch creation request also includes lock information of the data set.
The method according to claim 1 or 2, wherein the execution of the database operation statement included in each database operation instruction by the network agent node in the service database comprises:

The network agent node confirms that the automatic submission function of the service database is in an on state;

After receiving the first creation response sent by the transaction server for indicating that the transaction branch is successfully created, the network agent node executes the database operation statement included in each database operation instruction in the business database;

The method further includes: in response to the first creation response, the network agent node sends a first commit instruction for the transaction branch to the service database.
The method according to claim 1 or 2, wherein the method further comprises:

Receiving, by the network proxy node, a second creation response sent by the transaction server and used to indicate that the transaction branch creation failed;

In response to the second creation response, the network agent node sends a first rollback instruction for the transaction branch to the service database.
The method according to claim 2, wherein the method further comprises:

The network agent node confirms that the automatic submission function of the service database is in a closed state;

Sending, by the network agent node, the execution result of the database operation sentence included in each database operation instruction to the business client;

The acquiring of lock information of the data set by the network agent node includes:

The network agent node acquires the lock information of the data set after acquiring the second commit instruction for the transaction branch sent by the business client;

Wherein, the second submission instruction is sent by the business client after determining, according to the execution result, that the database operation statements included in each database operation instruction are executed successfully.
The method according to claim 5, wherein after the network agent node sends the execution result of the database operation sentence included in each database operation instruction to the service client, the method further comprises:

Acquiring, by the network proxy node, a second rollback instruction for the transaction branch sent by the business client, and deleting the lock information of the data set;

Sending, by the network agent node, the second rollback instruction to the service database;

Wherein, the second rollback instruction is sent by the business client after determining that any database operation statement included in any database operation instruction has failed to execute.
The method according to claim 3 or 5 or 6, wherein the method further comprises:

Acquiring, by the network agent node, the first setting instruction sent by the service client;

The network agent node records, according to the first setting instruction, that the automatic submission function of the service database is turned on;

Wherein, the first setting instruction is sent when the business client determines that the number of database operation statements used to implement the transaction branch is equal to one.
The method according to claim 3 or 5 or 6, wherein the method further comprises:

Acquiring, by the network agent node, a second setting instruction sent by the service client;

The network agent node records, according to the second setting instruction, that the automatic submission function of the service database is in a closed state;

Wherein, the second setting instruction is sent when the business client determines that the number of database operation statements used to implement the transaction branch is greater than one.
The method according to any one of claims 1 to 8, wherein the first creation response carries an identifier assigned by the transaction server to the transaction branch; the method further comprises:

After the network agent node receives the first creation response sent by the transaction server for indicating the successful creation of the transaction branch, the network agent node stores the identifier of the transaction branch and the transaction log in the transaction log of the distributed transaction. Correspondence of data sets;

The network agent node receives the third commit instruction for the transaction branch sent by the transaction server, and clears the transaction branch identifier and the data set recorded in the transaction log;

Wherein, the third commit instruction is sent by the transaction server after receiving the commit instruction for the distributed transaction sent by the business client.
The method according to any one of claims 1 to 8, wherein the first creation response carries an identifier assigned by the transaction server to the transaction branch; the method further comprises:

After the network agent node receives the first creation response sent by the transaction server for indicating the successful creation of the transaction branch, the network agent node stores the identifier of the transaction branch and the transaction log in the transaction log of the distributed transaction. Correspondence of data sets;

The network agent node receives the third rollback instruction for the transaction branch sent by the transaction server, obtains the data set from the transaction log according to the identifier of the transaction branch, and returns according to the data set Roll the transaction branch;

Wherein, the third rollback instruction is sent by the transaction server after receiving the rollback instruction for the distributed transaction sent by the business client.
A method for processing distributed transactions is characterized in that it is applied to a distributed transaction processing system. The distributed transaction processing system includes multiple service servers, transaction servers, and service databases, and each service server includes a network agent node and a service database. Client; the method includes:

The first business client generates one or more database operation statements for implementing the transaction branch according to the transaction branch to be executed by the first business client in the distributed transaction;

The first business client generates one or more database operation instructions according to the one or more database operation statements, and each database operation instruction includes: at least one database operation statement and the context of the distributed transaction. The context of the distributed transaction includes the identifier of the distributed transaction;

The first service client sends the one or more database operation instructions to a first network agent node, where the first network agent node and the first service client are deployed on the same service server.
The method according to claim 11, wherein the method further comprises:

The first service client sends the creation request of the distributed transaction to the transaction server in response to the service request;

Receiving, by the first service client, the identifier of the distributed transaction sent by the transaction server;

Sending, by the first business client, a service invocation request to a second business client participating in the distributed transaction, and the service invocation request carries an identifier of the distributed transaction;

The first business client determines the transaction branch to be executed by the first business client in the distributed transaction according to the business request.
The method according to claim 12, wherein the method further comprises:

Receiving, by the first service client, the commit result of the transaction branch sent by the first network proxy node;

Receiving, by the first business client, a service invocation response sent by the second business client in response to the service invocation request;

Sending, by the first business client, a commit instruction or a rollback instruction for the distributed transaction to the transaction server according to the commit result and the service invocation response;

Wherein, the commit instruction for the distributed transaction is used to instruct to submit each transaction branch included in the distributed transaction, and the commit instruction for the distributed transaction is used to instruct to roll back each transaction branch included in the distributed transaction. .
The method according to claim 11, wherein the method further comprises:

Receiving, by the first business client, a service invocation request sent by a second business client, the service invocation request carrying the context of the distributed transaction;

The first business client determines the transaction branch to be executed by the first business client in the distributed transaction according to the service invocation request.
The method according to any one of claims 11 to 14, wherein the method further comprises:

The first business client determines that the number of the database operation statements is equal to 1, and sends a first setting instruction to the first business database, where the first setting instruction indicates that the automatic submission function is set to an on state.
The method according to any one of claims 11 to 14, wherein the method further comprises:

The first business client determines that the number of the database operation statements is greater than 1, and sends a second setting instruction to the first business database, where the second setting instruction indicates that the automatic submission function is set to a closed state.
The method according to claim 16, wherein the method further comprises:

The first business client receives the execution result of the database operation sentence included in each database operation instruction;

The first business client determines, according to the execution result, that the database operation statements included in each database operation instruction are executed successfully, and sends a second commit instruction for the transaction branch to the first business database.
The method according to claim 16, wherein the method further comprises:

The first business client receives the execution result of the database operation sentence included in each database operation instruction;

The first business client determines, according to the execution result, that the execution of a database operation sentence included in any database operation instruction fails, and sends a second rollback instruction for the transaction branch to the first business database.
A network agent node is characterized by being applied to a distributed transaction processing system. The distributed transaction processing system includes a plurality of business servers, transaction servers and business databases, and each business server includes a network agent node and a business client; The network agent node includes:

The parsing module is used to obtain one or more database operation instructions sent by the business client, each database operation instruction includes: a database operation statement and the context of the distributed transaction, and the one or more database operation instructions include The database operation statement of is used to implement the transaction branch of the distributed transaction, and the context of the distributed transaction includes the identifier of the distributed transaction;

The transaction branch processing module is used to execute database operation statements included in each database operation instruction in the business database, and send a transaction branch creation request to the transaction server, the transaction branch creation request including the distributed transaction Logo.
The network agent node according to claim 19, wherein the transaction branch processing module is further configured to:

Acquire lock information of a data set, the data set being targeted by a database operation statement included in the one or more database operation instructions, and the lock information of the data set is used to identify the data set in the business database ；

The transaction branch creation request also includes lock information of the data set.
The network agent node according to claim 19 or 20, wherein the transaction branch processing module is configured to:

Confirming that the automatic submission function of the business database is in an on state;

After receiving the first creation response sent by the transaction server for indicating that the transaction branch is successfully created, execute the database operation statement included in each database operation instruction in the business database;

The transaction branch processing module is further configured to: in response to the first creation response, send a first commit instruction for the transaction branch to the business database.
The network agent node according to claim 19 or 20, wherein the transaction branch processing module is further configured to:

Receiving a second creation response sent by the transaction server and used to indicate that the creation of the transaction branch fails;

In response to the second creation response, a first rollback instruction for the transaction branch is sent to the service database.
The network agent node according to claim 20, wherein the transaction branch processing module is further configured to:

Confirm that the automatic submission function of the business database is in a closed state;

Sending the execution result of the database operation sentence included in each database operation instruction to the business client;

After acquiring the second commit instruction for the transaction branch sent by the business client, acquiring the lock information of the data set;

Wherein, the second submission instruction is sent by the business client after determining, according to the execution result, that the database operation statements included in each database operation instruction are executed successfully.
A business client, characterized in that it is applied to a distributed transaction processing system, the distributed transaction processing system includes a plurality of business servers, a transaction server and a business database, and each business server includes a network agent node and a business client; The business client includes:

A processing module, configured to generate one or more database operation statements for implementing the transaction branch according to the transaction branch to be executed by the business client in the distributed transaction;

The application program interface module is used to generate one or more database operation instructions according to the one or more database operation statements. Each database operation instruction includes: at least one database operation statement and the context of the distributed transaction. The context of the distributed transaction includes the identifier of the distributed transaction;

The database driver is configured to send the one or more database operation instructions to the first network agent node, wherein the first network agent node and the service client are deployed on the same service server.
The business client according to claim 24, wherein the application program interface module is further used for:

In response to the service request, sending the creation request of the distributed transaction to the transaction server;

Receiving the identifier of the distributed transaction sent by the transaction server;

The business client also includes:

The service invocation module is configured to send a service invocation request to a second business client participating in the distributed transaction, and the service invocation request carries an identifier of the distributed transaction;

The processing module is further configured to determine the transaction branch to be executed by the business client in the distributed transaction according to the business request.
The service client according to claim 25, wherein the processing module is further configured to:

Receiving the commit result of the transaction branch sent by the first network proxy node;

Receiving a service invocation response sent by the second business client in response to the service invocation request;

Sending a commit instruction or a rollback instruction for the distributed transaction to the transaction server according to the commit result and the service invocation response;

Wherein, the commit instruction for the distributed transaction is used to instruct to submit each transaction branch included in the distributed transaction, and the commit instruction for the distributed transaction is used to instruct to roll back each transaction branch included in the distributed transaction. .
The service client according to claim 24, wherein the processing module is further configured to:

Receiving a service invocation request sent by a second business client, where the service invocation request carries the context of the distributed transaction;

According to the service invocation request, determine the transaction branch to be executed by the business client in the distributed transaction.
A network agent node, characterized in that the network agent node includes a memory, a processor, and a computer program stored on the memory and capable of running on the processor, and the processor executes the computer program Realize the distributed transaction processing method according to any one of claims 1 to 10.
A business client, wherein the business client includes a memory, a processor, and a computer program stored in the memory and capable of running on the processor, and the processor executes the computer program Realize the distributed transaction processing method according to any one of claims 11 to 18.
A computer-readable storage medium, characterized in that instructions are stored in the computer-readable storage medium, and the instructions are executed by a processor to implement the distributed transaction processing method according to any one of claims 1 to 10 .
A computer-readable storage medium, characterized in that instructions are stored in the computer-readable storage medium, and the instructions are executed by a processor to implement the distributed transaction processing method according to any one of claims 11 to 18 .
A distributed transaction processing system, characterized in that the distributed transaction processing system includes: multiple business servers, transaction servers, and multiple business databases;

Each of the service servers includes the network agent node according to any one of claims 19 to 23 and 28, and the service client according to any one of claims 24 to 27, and 29.