CN114443232A - Transaction management method and device, electronic equipment and storage medium - Google Patents
Transaction management method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114443232A CN114443232A CN202210112999.3A CN202210112999A CN114443232A CN 114443232 A CN114443232 A CN 114443232A CN 202210112999 A CN202210112999 A CN 202210112999A CN 114443232 A CN114443232 A CN 114443232A
- Authority
- CN
- China
- Prior art keywords
- transaction
- node
- template
- calling
- transactions
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
Abstract
The embodiment of the application discloses a transaction management method and device, electronic equipment and a storage medium. The method comprises the following steps: under the condition that a business application initiates a target transaction, acquiring a transaction template corresponding to the target transaction; calling corresponding transactions according to the transaction flow in the transaction template, and acquiring transaction parameters fed back by each transaction; and feeding back the transaction data to the service application to complete the target transaction initiated by the service application. By utilizing the quoted transaction template, the agent end can call corresponding transactions according to the transaction flow in the transaction template, so that the transaction parameters fed back by each transaction are obtained, and based on the transaction parameters, the service application does not need to be responsible for calling the transactions any more, and the agent end is completely responsible for calling the transactions, so that the transaction management is decoupled from the service application, the coupling degree of the service application is reduced, the development difficulty can be effectively reduced, and the maintenance and the management of complex transactions are facilitated.
Description
Technical Field
The embodiment of the application relates to the technical field of service calling, in particular to a transaction management method and device, electronic equipment and a storage medium.
Background
Under the microservice architecture, because the same global transaction relates to a plurality of systems, databases of the systems are mutually independent, and the data consistency under the global transaction cannot be ensured by the local database transaction, so that a Two-Phase commit Protocol (hereinafter referred to as 2PC) is generated, and a TCC mode adopted by more systems in practice is realized based on the 2PC Protocol.
For the 2PC protocol, the main idea is to inform all participants in one phase to perform resource check and pre-occupation (i.e. Try operation), and to perform two-phase validation (i.e. Confirm operation) when all participants in one phase succeed; if part of the participator operations fail in one stage, all the participators which are successfully executed are informed to release the pre-occupied resources (namely, the Cancel operation). Because databases among systems under the micro-service architecture are independent from each other, the consistency of data under the global transaction can not be guaranteed by a host, and various distributed transaction frameworks are born under the background to guarantee the consistency of data.
For a distributed Transaction solution, such as Seata, the core components typically include Transaction Manager (TM), Transaction Coordinator (TC), and Resource Manager (RM). Wherein, TM opens distributed transaction (TM registers global transaction record with TC); the RM is responsible for consistency of local branch transactions, registers the branch transactions with the TC, and sends the execution success or failure state of the branch transactions to the TC; the TM ends the distributed transaction, transaction one phase ends (TM informs the TC to commit/roll back the global transaction); the TC determines whether the global transaction is committed or rolled back according to the TM commit/roll back instruction; the TC notifies all RMs to commit/rollback resources and the transaction two phase ends.
When the Seata system is called, the business application is coupled with the calling of the service system, which means that the business application needs to manage the execution flow of the business and control the processing of the transaction inside, and the strong coupling causes great development difficulty and is inconvenient for maintaining and managing complex transactions.
Disclosure of Invention
The embodiment of the application provides a transaction management method, a transaction management device, electronic equipment and a storage medium, so as to reduce the difficulty of development, maintenance and management.
In a first aspect, an embodiment of the present application provides a transaction management method, where the method includes:
under the condition that a business application initiates a target transaction, acquiring a transaction template corresponding to the target transaction;
calling corresponding transactions according to the transaction flow in the transaction template, and acquiring transaction parameters fed back by each transaction;
and feeding back the transaction data to the service application to complete the target transaction initiated by the service application.
In a second aspect, an embodiment of the present application further provides a transaction management apparatus, where the transaction management apparatus includes:
the transaction template acquisition module is used for acquiring a transaction template corresponding to a target transaction under the condition that the service application initiates the target transaction;
the transaction parameter acquisition module is used for calling corresponding transactions according to the transaction flow in the transaction template and acquiring the transaction parameters fed back by each transaction;
and the transaction parameter feedback module is used for feeding back the transaction data to the service application so as to complete the target transaction initiated by the service application.
In a third aspect, an embodiment of the present application further provides an electronic device, where the electronic device includes:
one or more processors;
a storage device to store one or more programs,
when executed by the one or more processors, the one or more programs cause the one or more processors to implement a transaction management method as provided in any embodiment of the present application.
In a fourth aspect, this embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the transaction management method according to any embodiment of the present application.
According to the technical scheme of the embodiment of the application, the agent end can call corresponding transactions according to the transaction flow in the transaction template by utilizing the quoted transaction template, so that the transaction parameters fed back by each transaction are obtained, based on the transaction parameters, the business application does not need to be responsible for calling the transactions, the agent end is completely responsible for calling the transactions, the transaction management is decoupled from the business application, the coupling degree of the business application is reduced, the development difficulty can be effectively reduced, and the maintenance and the management of complex transactions are facilitated.
Drawings
Fig. 1 is a schematic flowchart of a transaction management method according to an embodiment of the present application;
FIG. 2 is a flow diagram of a prior art nested transaction implementation;
fig. 3 is a schematic diagram illustrating a transaction flow initiation provided in a first embodiment of the present application;
fig. 4 is a schematic diagram of another transaction flow initiation provided in the first embodiment of the present application;
fig. 5 is a schematic structural diagram of a transaction management apparatus according to a second embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to a third embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic flowchart of a transaction management method according to an embodiment of the present application, which is applicable to a scenario of transaction management. The method can be executed by a transaction management device, which can be implemented in hardware and/or software, and can be generally integrated in an electronic device such as a computer with data operation capability, and specifically includes the following steps:
It should be noted that the service application is a party initiating the transaction, and in this embodiment, after the service application initiates the transaction, the transaction is determined to be completed by waiting for the transaction parameters returned after the transaction is completed.
In this embodiment, although the logic code of the developer is simplified after the transaction template is used, due to the introduction of the transaction template, the transaction template is not flexible enough when complex transactions are processed, and especially in a nested transaction scenario, the transaction template cannot guarantee data consistency between transactions.
For ease of illustration, reference may be made to FIG. 2, which is a flow diagram of a prior art nested transaction implementation, wherein each service represents a transaction. The global transaction initiated by the initiator a through the proxy includes three branch transactions: and the agent generates a global transaction ID for the global transaction to record information such as the state of the global transaction, and generates a corresponding branch transaction ID for each branch transaction to save information of related branch transactions.
At this time, if a branch transaction B itself is also the initiator, a global transaction also needs to be initiated by the proxy. In this case, when the branch transaction B is used as the initiator to invoke the services E and F through the proxy, it generates a new global transaction ID and the ID cannot be associated with the global ID generated when the initiator a invokes the proxy, so that the two stages of invocation cannot be regarded as the same global transaction, and the consistency of data cannot be guaranteed.
In order to ensure data consistency in a nested transaction scenario after a transaction template is introduced, the embodiment may first obtain a node calling condition pre-stored in a root node transaction that needs to be initiated by a target transaction; and then configuring a template table according to the pre-stored node calling condition to obtain a transaction template corresponding to the target transaction.
It should be noted that the node calling situations can be divided into two categories, one category is the pre-stored node calling situations including the child node transaction after the root node transaction and the child node calling situations of the child node transaction, that is, the root node transaction knows the depth of the calling node transaction and the calling situations of all node transactions; one type is that the pre-stored node calling cases only include the calling cases of the child node transactions, that is, the root node transaction only knows the child node transactions, and does not know the calling cases of the child node transactions.
For the first type, the child node transactions and the child nodes of the child node transactions can be registered in a first preset template table, and the transaction parameter dependency relationships among the root node transactions, the child node transactions and the child nodes of the child node transactions are configured to obtain the transaction template corresponding to the target transaction.
In one specific example, the resulting transaction template is shown in Table 1 below:
TABLE 1
As can be appreciated from Table 1, transaction A is a root node transaction, transaction C1 is a child node transaction of transaction B1, and transaction N is a child node transaction of transaction N-1; the triggering of transaction C1 needs to be dependent on the transaction parameters of transaction B1, and the triggering of transaction N needs to be dependent on the transaction parameters of transaction N-1.
For another type, each node transaction is both a participant and a possible initiator, and since the initiator transaction only knows the calling (combined transaction) condition of its child node transaction, all the node information registration involved in the transaction cannot be imported into the access template, and only the configuration information of its child node can be imported by the current node transaction (transaction) registration.
In one specific example, the resulting transaction template is shown in tables 2, 3, 4, and 5 below:
TABLE 2
It should be noted that transaction a is registered by the initiator and imported into the configuration table.
TABLE 3
The transactions B1 and B2 are registered and imported in the configuration table by the transaction a.
TABLE 4
The transaction C1 is registered and imported in the configuration table by the transaction B1.
TABLE 5
The transaction N is registered and imported in the configuration table by the transaction N-1.
And 102, calling corresponding transactions according to the transaction flow in the transaction template, and acquiring the transaction parameters fed back by each transaction.
In this step, the transaction flow refers to the dependency relationship embodied in the transaction template, taking table 1 as an example, specifically referring to fig. 3, and fig. 3 is a schematic diagram of initiating the transaction flow according to an embodiment of the present application.
As shown in fig. 3, Try transactions (A, B1, B2, C1,....... and N) are initiated in sequence according to table 1, and if Try succeeds, a Confirm action is performed, and if Try fails, a Cancel action is performed.
In addition, taking tables 2, 3, 4, and 5 as examples, specifically, reference may be made to fig. 4, where fig. 4 is another schematic diagram of initiating a transaction flow provided in the first embodiment of the present application.
It should be noted that each participant (transaction) needs to provide idempotent, anti-suspension, and idle rollback functions to ensure the solution of the problems caused by calling in abnormal transaction situations. The initiation of each branch transaction needs to be judged to be called according to the result returned to the present invention by the previous branch transaction, i.e. the next branch transaction is not known in advance, and the next call needs to be judged according to the return information assembled by the call node transaction (for example, the call B1 is not known in the beginning of the present embodiment, and the call B1 needs to be judged according to the result returned by a).
As shown in FIG. 4, A deal (combining B1 and B2), A deal is invoked first, i.e., the deal invocation traverses in tree-form predecessor. And the A transaction return parameter at least comprises a combined transaction mark, and if the A transaction return parameter is combined transaction, the branch transaction (the transaction of the A combination is called up) is continuously initiated according to the A transaction return parameter.
If the transaction is a combined transaction, the template number of the combined transaction of the transaction A needs to be provided, and the branch transaction number is searched according to the template number (namely, table 3).
If it is a combined transaction, A transaction returns instance data for Try for all combined transactions (B1, B2), providing call usage.
It should be noted that other types of combination transactions are similar to those described above, and are not described herein again.
And step 103, feeding back the transaction data to the service application to complete the target transaction initiated by the service application.
In the embodiment, the agent end can call the corresponding transaction according to the transaction flow in the transaction template by using the quoted transaction template, so that the transaction parameter fed back by each transaction is obtained, and based on the transaction parameter, the service application does not need to be responsible for calling the transaction any more, and the agent end is completely responsible for calling the transaction, so that the transaction management is decoupled from the service application, the coupling degree of the service application is reduced, the development difficulty can be effectively reduced, and the maintenance and the management of the complex transaction are facilitated.
Example two
Fig. 5 is a schematic structural diagram of a transaction management device according to a second embodiment of the present application. The transaction management device provided by the embodiment of the application can execute the transaction management method provided by any embodiment of the application, and has corresponding functional modules and beneficial effects of the execution method. The device can be implemented in software and/or hardware, and as shown in fig. 5, the transaction management device specifically includes: a transaction template obtaining module 501, a transaction parameter obtaining module 502 and a transaction parameter feedback module 503.
The transaction template acquisition module is used for acquiring a transaction template corresponding to a target transaction under the condition that the service application initiates the target transaction;
the transaction parameter acquisition module is used for calling corresponding transactions according to the transaction flow in the transaction template and acquiring the transaction parameters fed back by each transaction;
and the transaction parameter feedback module is used for feeding back the transaction data to the service application so as to complete the target transaction initiated by the service application.
In the embodiment, the agent end can call the corresponding transaction according to the transaction flow in the transaction template by using the quoted transaction template, so that the transaction parameter fed back by each transaction is obtained, and based on the transaction parameter, the service application does not need to be responsible for calling the transaction any more, and the agent end is completely responsible for calling the transaction, so that the transaction management is decoupled from the service application, the coupling degree of the service application is reduced, the development difficulty can be effectively reduced, and the maintenance and the management of the complex transaction are facilitated.
Further, the transaction template obtaining module comprises:
a node calling condition obtaining unit, configured to obtain a node calling condition pre-stored in a root node transaction that needs to be initiated by the target transaction;
and the trading template configuration unit is used for configuring a template table according to the pre-stored node calling condition to obtain a trading template corresponding to the target trade.
Further, the transaction template configuration unit includes:
and the configuration subunit is configured to register the child node transactions and the child nodes of the child node transactions in a first preset template table, and configure a transaction parameter dependency relationship among the root node transactions, the child node transactions and the child nodes of the child node transactions to obtain a transaction template corresponding to the target transaction, if the pre-stored node calling condition includes the child node transactions after the root node transactions and the child node calling condition of the child node transactions.
Further, the transaction template configuration unit includes:
a sub-node transaction calling situation obtaining subunit, configured to sequentially obtain sub-node transaction calling situations of the sub-node transactions if the pre-stored node calling situation only includes a calling situation of the sub-node transaction;
the template table registration subunit is used for registering the calling condition of the child node included in any node transaction into a second preset template table to obtain the template table of the node transaction;
and the trading template generating subunit is used for determining the trading template corresponding to the target trade according to the template tables of all the node transactions.
EXAMPLE III
Fig. 6 is a schematic structural diagram of an electronic device according to a third embodiment of the present application, as shown in fig. 3, the electronic device includes a processor 610, a memory 620, an input device 630, and an output device 640; the number of the processors 610 in the electronic device may be one or more, and one processor 610 is taken as an example in fig. 6; the processor 610, the memory 620, the input device 630 and the output device 640 in the electronic apparatus may be connected by a bus or other means, and the connection by the bus is exemplified in fig. 6.
The memory 620, as a computer-readable storage medium, may be used for storing software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the transaction management method in the embodiment of the present invention (for example, the transaction template obtaining module 501, the transaction parameter obtaining module 502, and the transaction parameter feedback module 503 in the transaction management device). The processor 610 executes various functional applications and data processing of the electronic device by executing software programs, instructions and modules stored in the memory 620, that is, implements the transaction management method described above:
under the condition that a business application initiates a target transaction, acquiring a transaction template corresponding to the target transaction;
calling corresponding transactions according to the transaction flow in the transaction template, and acquiring transaction parameters fed back by each transaction;
and feeding back the transaction data to the service application to complete the target transaction initiated by the service application.
Further, the obtaining of the transaction template corresponding to the target transaction includes:
acquiring a node calling condition prestored in a root node transaction which is required to be initiated by the target transaction;
and configuring a template table according to the pre-stored node calling condition to obtain a transaction template corresponding to the target transaction.
Further, the configuring a template table according to the pre-stored node calling situation to obtain a transaction template corresponding to the target transaction includes:
if the pre-stored node calling condition comprises a child node transaction after the root node transaction and a child node calling condition of the child node transaction, registering the child node transaction and a child node of the child node transaction in a first preset template table, and configuring a transaction parameter dependency relationship among the root node transaction, the child node transaction and the child node of the child node transaction to obtain a transaction template corresponding to the target transaction.
Further, the configuring a template table according to the pre-stored node calling situation to obtain a transaction template corresponding to the target transaction includes:
if the pre-stored node calling condition only comprises the calling condition of the sub-node transaction, sequentially acquiring the sub-node transaction calling condition of the sub-node transaction;
for any node transaction, registering the included child node calling condition in a second preset template table to obtain the template table of the node transaction;
and determining a trading template corresponding to the target trade according to the template tables of all the node trades.
The memory 620 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 620 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, the memory 620 can further include memory located remotely from the processor 610, which can be connected to an electronic device through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
Example four
A fourth embodiment of the present application further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a transaction management method, the method including:
under the condition that a business application initiates a target transaction, acquiring a transaction template corresponding to the target transaction;
calling corresponding transactions according to the transaction flow in the transaction template, and acquiring transaction parameters fed back by each transaction;
and feeding back the transaction data to the service application to complete the target transaction initiated by the service application.
Further, the obtaining of the transaction template corresponding to the target transaction includes:
acquiring a node calling condition prestored in a root node transaction which is required to be initiated by the target transaction;
and configuring a template table according to the pre-stored node calling condition to obtain a transaction template corresponding to the target transaction.
Further, the configuring a template table according to the pre-stored node calling situation to obtain a transaction template corresponding to the target transaction includes:
if the pre-stored node calling condition comprises a child node transaction after the root node transaction and a child node calling condition of the child node transaction, registering the child node transaction and a child node of the child node transaction in a first preset template table, and configuring a transaction parameter dependency relationship among the root node transaction, the child node transaction and the child node of the child node transaction to obtain a transaction template corresponding to the target transaction.
Further, the configuring a template table according to the pre-stored node calling situation to obtain a transaction template corresponding to the target transaction includes:
if the pre-stored node calling condition only comprises the calling condition of the sub-node transaction, sequentially acquiring the sub-node transaction calling condition of the sub-node transaction;
for any node transaction, registering the included child node calling condition in a second preset template table to obtain the template table of the node transaction;
and determining a trading template corresponding to the target trade according to the template tables of all the node trades.
From the above description of the embodiments, it is obvious for those skilled in the art that the present application can be implemented by software and necessary general hardware, and certainly can be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods of the embodiments of the present application.
It should be noted that, in the embodiment of the above search apparatus, each included unit and module are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only used for distinguishing one functional unit from another, and are not used for limiting the protection scope of the application.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments illustrated herein, and that various obvious changes, rearrangements and substitutions may be made therein by those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.
Claims (10)
1. A transaction management method applied to an agent side, the method comprising:
under the condition that a business application initiates a target transaction, acquiring a transaction template corresponding to the target transaction;
calling corresponding transactions according to the transaction flow in the transaction template, and acquiring transaction parameters fed back by each transaction;
and feeding back the transaction data to the service application to complete the target transaction initiated by the service application.
2. The method of claim 1, wherein the obtaining a transaction template corresponding to the target transaction comprises:
acquiring a node calling condition prestored in a root node transaction which is required to be initiated by the target transaction;
and configuring a template table according to the pre-stored node calling condition to obtain a transaction template corresponding to the target transaction.
3. The method according to claim 2, wherein the configuring a template table according to the pre-stored node calling situation to obtain the transaction template corresponding to the target transaction comprises:
if the pre-stored node calling condition comprises a child node transaction after the root node transaction and a child node calling condition of the child node transaction, registering the child node transaction and a child node of the child node transaction in a first preset template table, and configuring a transaction parameter dependency relationship among the root node transaction, the child node transaction and the child node of the child node transaction to obtain a transaction template corresponding to the target transaction.
4. The method according to claim 2, wherein the configuring a template table according to the pre-stored node calling situation to obtain the transaction template corresponding to the target transaction comprises:
if the pre-stored node calling condition only comprises the calling condition of the sub-node transaction, sequentially acquiring the sub-node transaction calling condition of the sub-node transaction;
for any node transaction, registering the included child node calling condition in a second preset template table to obtain the template table of the node transaction;
and determining a trading template corresponding to the target trade according to the template tables of all the node trades.
5. A transaction management apparatus, the apparatus comprising:
the transaction template acquisition module is used for acquiring a transaction template corresponding to a target transaction under the condition that the service application initiates the target transaction;
the transaction parameter acquisition module is used for calling corresponding transactions according to the transaction flow in the transaction template and acquiring the transaction parameters fed back by each transaction;
and the transaction parameter feedback module is used for feeding back the transaction data to the service application so as to complete the target transaction initiated by the service application.
6. The apparatus of claim 5, wherein the transaction template acquisition module comprises:
a node calling condition obtaining unit, configured to obtain a node calling condition pre-stored in a root node transaction that needs to be initiated by the target transaction;
and the trading template configuration unit is used for configuring a template table according to the pre-stored node calling condition to obtain a trading template corresponding to the target trade.
7. The apparatus of claim 6, wherein the transaction template configuration unit comprises:
and the configuration subunit is configured to register the child node transactions and the child nodes of the child node transactions in a first preset template table, and configure a transaction parameter dependency relationship among the root node transactions, the child node transactions and the child nodes of the child node transactions to obtain a transaction template corresponding to the target transaction, if the pre-stored node calling condition includes the child node transactions after the root node transactions and the child node calling condition of the child node transactions.
8. The apparatus of claim 6, wherein the transaction template configuration unit comprises:
a sub-node transaction calling situation obtaining subunit, configured to sequentially obtain sub-node transaction calling situations of the sub-node transactions if the pre-stored node calling situation only includes a calling situation of the sub-node transaction;
the template table registration subunit is used for registering the calling condition of the child node included in any node transaction into a second preset template table to obtain the template table of the node transaction;
and the trading template generating subunit is used for determining the trading template corresponding to the target trade according to the template tables of all the node transactions.
9. An electronic device, comprising:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the transaction management method of any of claims 1-4.
10. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the transaction management method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210112999.3A CN114443232A (en) | 2022-01-29 | 2022-01-29 | Transaction management method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210112999.3A CN114443232A (en) | 2022-01-29 | 2022-01-29 | Transaction management method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114443232A true CN114443232A (en) | 2022-05-06 |
Family
ID=81372155
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210112999.3A Pending CN114443232A (en) | 2022-01-29 | 2022-01-29 | Transaction management method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114443232A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115914240A (en) * | 2023-01-06 | 2023-04-04 | 江苏荣泽信息科技股份有限公司 | Cross-chain transaction template management system based on DNS (Domain name System) analysis |
-
2022
- 2022-01-29 CN CN202210112999.3A patent/CN114443232A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115914240A (en) * | 2023-01-06 | 2023-04-04 | 江苏荣泽信息科技股份有限公司 | Cross-chain transaction template management system based on DNS (Domain name System) analysis |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7904567B2 (en) | Method, apparatus and computer program product for integrating heterogeneous systems | |
| JP2000242615A (en) | Server computing device, operation method and storage device | |
| CN111277639B (en) | Method and device for maintaining data consistency | |
| US6895408B1 (en) | Method and apparatus to facilitate interaction management between loosely coupled applications | |
| CN110083661B (en) | Capacity expansion method of block chain system, terminal device and storage medium | |
| CN111651244A (en) | Processing system for distributed transactions | |
| CN112817995B (en) | Data processing method and device, electronic equipment and storage medium | |
| WO2019149032A1 (en) | Distributed transaction processing method and device | |
| CN114443232A (en) | Transaction management method and device, electronic equipment and storage medium | |
| CN114237994A (en) | Test method and system for distributed system, electronic device and storage medium | |
| JPH0628292A (en) | Method and apparatus for reduction of number of synchronizing points at inside of network for control of transaction processing and method for reduction of number of protocol messages flowing in network | |
| US6542922B1 (en) | Client/server transaction data processing system with automatic distributed coordinator set up into a linear chain for use of linear commit optimization | |
| CN113961332A (en) | Method and device for realizing workflow engine, electronic equipment and storage medium | |
| CN113377875B (en) | Cross-chain data processing method and device, electronic equipment and readable storage medium | |
| CN113297329A (en) | Transaction processing method, device, equipment, storage medium and program product | |
| WO2021052237A1 (en) | Transaction processing method and apparatus, device, storage medium and database | |
| WO2022206429A1 (en) | Distributed transaction implementation method and distributed system | |
| US10007547B2 (en) | Specifying an invocation order of a plurality of resources in a transaction according to resource distance | |
| CN107465725B (en) | Heterogeneous long transaction processing system and method based on client information control system | |
| CN112395104B (en) | Method and device for realizing distributed transaction context transfer in routing layer | |
| CN111399851B (en) | Batch processing execution method based on distributed system | |
| CN111143040A (en) | Transaction processing method, device, system and storage medium | |
| KR100233238B1 (en) | Two way authentication communication method using multithread in distributed transaction system | |
| CN113486033A (en) | Method, apparatus, device and computer readable medium for controlling transaction consistency | |
| Böttcher et al. | Reducing sub-transaction aborts and blocking time within atomic commit protocols |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |