TW201828164A - Database operation method and device capable of improving transaction execution efficiency of database transaction with higher delivery amount of transactions - Google Patents

Abstract

The invention provides a database operation method and device. The method includes: in the process of executing the target transaction by the application server, sequentially acquiring the database operation instruction in the target transaction executed by the application server; performing prediction execution on the database operation instruction, and returning the prediction execution result to the application server. The provisioning server determines the next database operation instruction to be executed, and records the database operation instruction locally and records the predicted execution data generated by the prediction execution when the database operation instruction belongs to the modified database type instruction; when the target transaction is acquired When the transaction in the transaction commits the instruction, the database corresponding to the locally recorded database operation instruction and the predicted execution data controls the database corresponding to the application server to actually execute the target transaction. The invention can improve transaction execution efficiency.

Description

 Database operation method and device  

The invention relates to the technical field of database, in particular to a database operation method and device.

Database Transaction refers to a series of operations performed as a single logical unit of work, either completely or completely. A transaction consists of a series of database operation instructions, such as Structured Query Language (SQL) statements. There are logics such as splitting conditions and jumps between these database operation instructions, meaning that the transaction is executed in one execution. Some database operation instructions may be skipped and not executed. However, in the prior art, since the database operation instruction that needs to be executed in the transaction cannot be known in advance, the execution judgment can only be performed according to the execution logic, and the statement in the transaction is sequentially executed to implement the operation on the database. This type of transaction execution is less efficient, especially when the transaction settings read committed isolation level is less efficient and the transaction volume is lower.

Aspects of the present invention provide a database operation method and apparatus for improving transaction execution efficiency and increasing transaction throughput.

An aspect of the present invention provides a database operation method, including: sequentially acquiring, in an execution process of an application server, a database operation instruction in the target transaction executed by the application server; The database operation instruction performs prediction execution, returns the predicted execution result to the application server for the application server to determine the next database operation instruction to be executed, and locally records the database operation instruction and the local The database operation instruction belongs to the prediction execution data generated by the prediction execution when the database instruction is modified; when the transaction commit instruction in the target transaction is acquired, according to the database operation instruction of the local record and the Predicting the execution data, and controlling the database corresponding to the application server to actually execute the target transaction.

In another aspect of the present invention, a database operating device is provided, including: an obtaining module, configured to sequentially acquire data in the target transaction executed by the application server during a process of executing a target transaction by an application server a library operation instruction; a prediction execution module, configured to perform prediction execution on the database operation instruction, and return the prediction execution result to the application server for the application server to determine a next database operation instruction to be executed And recording the database operation instruction locally and recording the predicted execution data generated by the prediction execution when the database operation instruction belongs to the modification database type instruction; and controlling the execution module, when acquiring the target When the transaction in the transaction commits the instruction, the database corresponding to the application server is controlled to actually execute the target transaction according to the database operation instruction and the predicted execution data recorded locally.

In the present invention, the database operating device cooperates with the application server to join the predictive execution process in the process of executing the target transaction by the application server, and obtains and records all the database operation instructions that need to be executed in the target transaction in advance, and only belongs to the modification. The database operation instruction record of the database class instruction records the prediction execution data generated by the prediction execution to adapt to the read isolation level, provides conditions for the real execution transaction, and then controls the application servo according to the recorded database operation instruction and the prediction execution data. The corresponding database of the device actually executes the target transaction, which is beneficial to improve the execution efficiency and thereby increase the transaction volume.

10‧‧‧Application Server

20‧‧‧Database

30‧‧‧Database operating device

301, 302, 303‧ ‧ method steps

41‧‧‧Get the module

42‧‧‧Predictive Execution Module

43‧‧‧Control Execution Module

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are some of the present invention. For the embodiments, other drawings may be obtained from those skilled in the art without any inventive labor.

1 is a deployment diagram of a database application system in the prior art; FIG. 2 is a deployment diagram of a database application system according to an embodiment of the present invention; FIG. 3 is a schematic flowchart of a database operation method according to an embodiment of the present invention; FIG. 4 is a schematic structural diagram of a database operating device according to an embodiment of the present invention.

The technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is a partial embodiment of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

FIG. 1 is a deployment diagram of a database application system in the prior art. As shown in FIG. 1, the system includes an application server 10 and a database 20. The database 20 may be one or more than one. Only one database 20 is shown by way of example in FIG. When the database 20 needs to be accessed in a transactional manner, the application server 10 executes the transaction logic to sequentially apply the database operation instructions in the transaction to the database 20. Because the database operation instructions that need to be executed in the transaction cannot be known in advance, the transaction execution efficiency is low, especially when the configuration read commit isolation level is configured, the execution efficiency is lower, and the transaction volume is lower.

In view of the deficiencies of the prior art, the present invention provides a new database application system, as shown in FIG. The system adds a database operating device 30 between the application server 10 and the database 20. The database operation device 30 is configured to execute the database operation method provided by the present invention, and implement a new transaction execution logic under the isolation level of the read commit, that is, predictive execution of the transaction and obtaining the data to be executed in the transaction in advance. The library operation instruction realizes the prediction of the execution path, and the read execution level has been submitted only for the prediction execution data generated by the prediction execution of the database operation instruction record belonging to the modified database class instruction, and then obtained based on the prediction execution. The database operation instruction and the prediction execution data actually execute the transaction on the database 20, which is beneficial to improve transaction execution efficiency and increase transaction volume. Transaction throughput refers to the number of transactions processed per unit of time.

It should be noted that the database operating device 30 is actually a logical processing device, which can be deployed separately, between the application server 10 and the database 20, or can be deployed on one end of the application server 10, or can be deployed. Implemented at the end of the database 20.

The following embodiment will specifically describe the method flow of the technical solution of the present invention.

FIG. 3 is a schematic flowchart diagram of a method for operating a database according to an embodiment of the present invention. As shown in FIG. 3, the method includes:

301. In the process of executing the target transaction by the application server, sequentially acquiring the database operation instruction in the target transaction executed by the application server.

302. Perform predictive execution on the database operation instruction, return the predicted execution result to the application server to supply the server to determine the next database operation instruction to be executed, and locally record the database operation instruction and the database operation instruction. The forecast execution data generated by the prediction execution is recorded when the database type instruction is modified.

303. When the transaction commit instruction in the target transaction is obtained, according to the local record database operation instruction and the predicted execution data, the database corresponding to the application server is controlled to actually execute the target transaction.

First, for convenience of description, the present embodiment refers to a transaction that the application server needs to perform as a target transaction. The target transaction mainly includes operation instructions for operating the database, and in addition to the database operation instructions, some control instructions for controlling the execution state of the target transaction, such as a transaction start instruction, a transaction commit instruction, a transaction recovery instruction, and the like. These instructions are actually statements written in the database language. Depending on the language of the database, these instructions can be statements written in different languages. For example, if SQL is used, the above database operation instructions and control instructions are actually a series of SQL statements.

The method provided in this embodiment is applicable to operating a database whose isolation level is read and submitted. Among them, some database presets are read and submitted this isolation level. For example, the Oracle database preset is to read the isolation level that has been submitted. Some database presets are not read and submitted, such as MySQL data. The library preset is the level of isolation that can be read repeatedly. Based on this, before performing the method provided in this embodiment, it can be determined whether the isolation level of the database is a read commit, and if not, the database needs to be pre-configured to read the isolation level. For example, the repository can be configured to read this isolation level before the application server performs the target transaction.

Under the premise that the isolation level of the database is read, the method provided in this embodiment may be executed to execute the target transaction in the database. The specific process is as follows: The application server controls the execution logic of the entire target transaction, and the target transaction can be executed in the existing manner. The database operating device sequentially acquires the database operation instruction in the target transaction executed by the application server during the execution of the target transaction by the application server.

In an optional implementation, the application server sends the database operation instruction to the database in an existing manner to implement access to the database. The database operating device can monitor the communication between the application server and the database to intercept the database operation instructions sent by the application server to the database.

In another alternative embodiment, the processing logic of the application server is slightly modified, and the processing logic that originally sent the database operation instruction to the database is changed to be sent to the database operating device. Based on this, the database operating device can receive the database operation instruction actively issued by the application server.

Here, if the target transaction is an explicit transaction, the first instruction in the target transaction is a transaction start instruction, such as a begin transaction, based on which the database operation device acquires the database to which the application server executes. Before the operation instruction, the transaction start instruction in the target transaction sent by the application server to the database may be intercepted, and according to the transaction start instruction, the target transaction needs to be executed. Alternatively, the database operation device may receive a transaction start instruction in the target transaction actively issued by the application server before acquiring the database operation instruction executed by the application server, and according to the transaction start instruction, learn that the target transaction needs to be executed. If the target transaction is an implicit transaction, the first instruction of the target transaction is the database operation instruction, and does not include the step of obtaining the transaction start instruction.

After obtaining the database operation instruction executed by the application server, the database operation device performs predictive execution on the acquired database operation instruction, returns the predicted execution result to the application server, and uses the server to determine the next execution required. Database operation instructions. The predicted execution result determines the execution path of the target transaction, where the execution path refers to the jump logic between the database operation instructions. By returning the predicted execution result to the application server, the purpose of controlling the execution logic of the entire target transaction by the application server is achieved.

In addition, the database operating device also needs to locally record the acquired database operation instruction, and record the predicted execution data generated by predictive execution of the database operation instruction when the database operation instruction belongs to the modified database type instruction. The modified database class instruction refers to a database operation instruction that has a modified database, for example, an instruction starting with update, insert, etc.; generally, an instruction beginning with a select does not belong to a modified database class instruction. The predicted execution data mainly refers to some materials in the process of predictive execution of the database operation instructions.

For example, the database operating device may locally establish a memory library, and store the acquired database operation instructions and predicted execution data in a memory library. Further, if the predicted execution data does not include the predicted execution result, the predicted execution result may also be stored in the memory bank.

In essence, reading the committed isolation level only guarantees that writing multiple data is atomic, and does not lock when reading, which can improve the concurrency of the system and improve the efficiency of transaction execution. In order to implement the simulation of the isolation level submitted to the read on the basis of the core idea of predictive execution, the present embodiment records only the predicted execution data generated by the prediction execution for the database operation instruction belonging to the modified database class instruction. The predicted execution data corresponding to the database operation instruction that does not belong to the modified database class instruction is not recorded. It can be seen that in the case that the reading has been submitted to the isolation level, the amount of recorded data is relatively small, so that the subsequent target transaction based on the local record-based database operation instruction and the prediction execution data is actually executed in the database. In the process, the amount of data to be processed is relatively small, which is beneficial to further improve execution efficiency and performance, and increase transaction volume.

Among them, the operation of the database operation instruction to the database is mainly to access the data in the database, and the data environment of the database operation instruction can be analogized, and the database operation instruction is predicted and executed based on the analog data environment. Further, considering that the database operation instruction that is not the instruction to modify the database class does not cause the change of the database, the database operation instruction can be directly predicted and executed in the database, thereby saving the operation of the analog data environment. The implementation is relatively simple, which is conducive to saving resources and improving execution efficiency. However, for the database operation instructions belonging to the modified database class instruction, since it will cause changes in the database (mainly refers to the data in the database is changed), an analog data environment is required, which is performed in the analog data environment. Forecast execution.

Based on the above analysis, a method for predicting execution of the database operation instruction may be: identifying the category of the obtained database operation instruction; if the database operation instruction belongs to the modification database type instruction, the locally established memory The data environment of the analog database operation instruction in the library predicts execution of the database operation instruction based on the analogy data environment; if the database operation instruction does not belong to the modified database type instruction, the database operation instruction is executed in the database, Predictive execution of the database operation instructions.

Further, a data environment of an analog database operation instruction in a locally established memory library, and an implementation manner of predicting execution of the database operation instruction based on the analog data environment includes: splitting the obtained database operation instruction into A read instruction and a write instruction, the read instruction is run on a real database, that is, the read instruction is executed in the database to obtain a read data set (ReadSet), and the read data set is stored in the local memory library, The data environment required for the analog database operation instructions. Then, the write command is applied to the memory bank to implement predictive execution of the database operation instruction, that is, executing a write instruction in the memory bank to modify the read data set, for example, updating or querying related data in the read data set. Processing and so on. Wherein, executing a write command to modify the read data set may generate a result data set (affectRowInMemdb), the result data set including the predicted execution result.

In the above prediction execution process, if the database operation instruction belongs to the modification database class instruction, the database operation device can locally record the read data set read by the read instruction and the result data set generated by executing the write instruction. It can be seen that the predicted execution data may include a read data set and a result data set, or may also include some data in the read data set and the result data set, for example, some of the beneficial effects on the actual execution of the target transaction in the database. Data, such as various indexes of some values, such as primary index, secondary index, primary key value, and so on.

When the database operation device acquires the transaction commit instruction in the target transaction (ie, the application server executes to the transaction commit instruction), the database corresponding to the application server may be controlled according to the locally recorded database operation instruction and the predicted execution data. Actual execution of the target transaction.

According to the database operation instruction and the prediction execution data recorded locally, an optional implementation manner of controlling the database corresponding to the application server to actually execute the target transaction includes: the database operation device transmitting the local record to the database An operation instruction to instruct the database to execute the database operation instruction, and receive the actual execution result of the database operation instruction returned by the database; and then compare the actual execution result of the database operation instruction with the predicted execution result, if the actual execution result Same as the predicted execution result, the transaction commit instruction is sent to the database for the database to submit the target transaction; if the actual execution result is different from the predicted execution result, the transaction recovery instruction is sent to the database for the database to be rolled back. The target transaction.

In the above embodiment, considering the atomicity of the transaction, by comparing the actual execution result with the predicted execution result, the transaction execution process error can be avoided, which is advantageous for improving the success probability of the transaction execution.

Further, in the prior art, since all the database operation instructions that the transaction needs to execute cannot be known in advance, the database operation instruction can be executed sequentially according to the execution logic of the transaction, which causes frequent interaction between the application server and the database. This will consume a lot of network resources in the remote application scenario. However, in this embodiment, all the database operation instructions that need to be executed by the target transaction, that is, the local record database operation instruction, have been obtained in advance through the prediction execution process, so that the local record database operation instruction is sent to the database to In the process of instructing the database to execute the database operation instruction, the local record database operation instruction can be simultaneously (or collectively) sent to the database, which is conducive to saving network resources. In addition, for some parallel database operation instructions, the database can also work in parallel, which is beneficial to further improve transaction execution efficiency and increase transaction throughput.

Further, all the database operation instructions recorded locally can be sent to the database together with the locally recorded predicted execution data.

Further, in an optional implementation manner of controlling a database corresponding to the actual execution of the target transaction according to the locally recorded database operation instruction and the predicted execution data, the database operation device may operate the instruction according to the locally recorded database. Determining whether the target transaction is a stand-alone transaction; if the determination result is yes, according to the locally recorded database operation instruction and the predicted execution data, the single-machine transaction processing logic controls the database to actually execute the target transaction; if the judgment result is negative, according to the local Recorded database operation instructions and predictive execution data, and the distributed transaction processing logic controls the database to actually execute the target transaction.

The database operation instruction obtained during the prediction execution process can identify whether the target transaction is a stand-alone transaction or a distributed transaction. For example, it can be determined whether the operation object of the locally recorded database operation instruction acts on the same physical device. If the determination result is yes, it can be determined that the target transaction is a stand-alone transaction; if the determination result is no, the target transaction can be determined. For decentralized transactions.

Since the processing logic of a decentralized transaction is different from the processing logic of a stand-alone transaction, the processing logic of a stand-alone transaction is relatively simple, for example, it does not involve problems such as reading and writing locks, so the resources consumed are relatively small. Based on this, the present embodiment uses the processing logic of the single-machine transaction to identify whether the target transaction is a stand-alone transaction, and does not use the distributed transaction processing logic to process the same as the prior art, which is beneficial to improve processing. Efficiency, saving processing costs.

In an optional implementation manner, if the database operation device acquires the transaction recovery instruction in the target transaction (ie, the application server executes to the transaction recovery instruction), the local record database operation instruction and the predicted execution data may be deleted, for example, The local memory library can be directly emptied to implement the rollback operation. In this case, since the target transaction is not actually executed in the database, the database does not need to perform a rollback operation. It can be seen that in the case of transaction recovery, the transaction efficiency can be improved by using the method of the embodiment.

It can be seen from the above that in the method provided by the embodiment, the database operation device and the application server cooperate with each other, and the prediction execution process is added in the process of the application server executing the target transaction, and the target transaction can be obtained in advance during the prediction execution process. The execution path, that is, the database operation instruction that really needs to be executed, and only records the predicted execution data generated by the prediction execution for the database operation instruction belonging to the modified database class instruction to adapt to the read isolation level, and provides a real execution transaction. Condition, after actually executing the target transaction according to the recorded database operation instruction and the predicted execution data, for example, based on the predicted execution data, the related information information can be acquired in advance and the jump between the instructions can be reduced, thereby improving execution efficiency and increasing Large transaction volume.

The workflow of the technical solution of the present invention will be described in detail below by taking the inventory reduction transaction as an example. The isolation level of the database is the isolation level that the read has been submitted.

The SQL code for the inventory reduction transaction is as follows, the text in parentheses is a comment:

In the actual execution process, the application server is responsible for the entire logic of the inventory reduction transaction, and the database operation device (or may also be referred to as an execution server) only obtains the start transaction to which the application server executes, and the SQL statement that needs to be executed. And commit/rollback instructions.

First, after starting the transaction, the database operating device locally creates a memory bank; when the database operating device obtains select * from inventory where itemId=? For update this SQL statement, it is recognized that this SQL statement will not modify the database, so this SQL statement directly acts on the actual database, that is, execute the SQL statement in the database to obtain the query result, ie Read the data set and return all the query results to the application server to supply the server to determine the next SQL statement to be executed, and record the SQL statement in the local memory library. Since the read level is read, there is no need to record any information related to executing the SQL statement.

After receiving the query result returned by the database operation device, the application server determines whether the current inventory quantity in the query result is greater than 0. If the judgment result is yes, the current inventory quantity is reduced, and the update statement is executed, that is, the update inventory set item. Inventory=$item.inventory where itemId=? If the result of the judgment is no, the rollback statement is executed.

In the first case, if the application server executes the rollback statement, the database operating device will obtain the rollback statement. Once the database storage device obtains the rollback statement, the local memory library is emptied, mainly to clear the previously selected select * from inventory where itemId=? For update this SQL statement. In this case, because the transaction is not executed in the repository, there is no need for the repository to perform a rollback operation.

In the second case, suppose the application server executes update inventory set item.inventory=$item.inventory where itemId=? In this statement, the database operating device will get update inventory set item.inventory=$item.inventory where itemId=? This statement. Then the database operating device obtains update inventory set item.inventory=? Where itemId=? This SQL statement recognizes that the SQL statement will modify the database, so the SQL statement is split into a read command, ie select * from inventory where itemId=? And a write command, ie update inventory set item.inventory=? Where itemId=? Then, select * from inventory where itemId=? The statement is sent to the database, and the read data set is obtained, and the data in the read data set is written into the local memory library; wherein the read data set includes a primary key list (itemId) and a version number information corresponding to the primary key (version). . Then, according to update inventory set item.inventory=? Where itemId=? This statement performs an update operation in the local memory library to obtain the result data set and returns the result data set to the application server. The result data set may be modified record information similar to the modification of several records. For example, affectRow=1 indicates that a record is modified; or the result data set may also be modified details of the record modification detailed information. Among them, the result data set and the read data set constitute prediction execution data.

The application server executes the commit command at this time.

After the database operation device obtains the commit command, the inventory reduction transaction is executed in the database based on the SQL statement in the local memory library and the predicted execution data, and the transaction execution process is actually performed. For example, the locally recorded SQL statement and the predicted execution data are as follows:

Preferably, the database operating device can submit all the SQL statements in the local memory library to the database at one time, and the database is executed based on the data, thereby saving the network resources consumed by the transmission of the SQL statement.

This real execution will also return the execution result. You can compare the predicted execution result with the actual execution result. For example, you can compare the itemId and version of the two results first, and then compare the affectRow of the two results; if the comparison result is the same, You can submit this transaction in the database, and if the comparison result is not the same, then the submission is considered to be a failure, because in this case, the transaction itself has not actually been executed in the database, so it can be simple Roll back the entire request and let the application server resubmit.

Among them, after the above prediction execution, all the SQL statements that need to be executed, and the corresponding predicted execution data, such as all the segmentation conditions, the index of the values, etc., have been obtained, and the data is sufficient for us to advance whether the transaction is a stand-alone transaction. Make a judgment. Based on this, the corresponding transaction processing logic can be used for processing, which is conducive to saving resources.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the present invention is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present invention. Secondly, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the above embodiments, the descriptions of the various embodiments are different, and the details that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

FIG. 4 is a schematic structural diagram of a database operating device according to an embodiment of the present invention. As shown in FIG. 4, the device includes an acquisition module 41, a prediction execution module 42, and a control execution module 43.

The obtaining module 41 is configured to sequentially acquire the database operation instruction in the target transaction executed by the application server during the execution of the target transaction by the application server.

The predictive execution module 42 is configured to perform predictive execution on the database operation instruction, return the predicted execution result to the application server to supply the server to determine the next database operation instruction to be executed, and record the database operation instruction locally. And predicting the execution data generated by the prediction execution when the database operation instruction belongs to the modification database class instruction.

The control execution module 43 is configured to control the database corresponding to the application server to actually execute the target transaction according to the locally recorded database operation instruction and the predicted execution data when the transaction commit instruction in the target transaction is acquired.

In an optional implementation, the database operating device further includes: a configuration module, configured to configure the database to read the submitted isolation level before the application server performs the target transaction.

In an optional implementation, the obtaining module 41 is specifically configured to: intercept the database operation instruction sent by the application server to the database; or receive the database operation instruction actively sent by the application server.

In an optional implementation, the obtaining module 41 is further configured to: before acquiring the database operation instruction in the target transaction executed by the application server, intercepting the transaction start instruction in the target transaction sent by the application server to the database Or, receive a transaction start instruction in the target transaction actively issued by the application server.

In an optional implementation, the prediction execution module 42 is specifically configured to: if the database operation instruction acquired by the acquisition module 41 belongs to the modified database class instruction, the analog database operation instruction in the locally established memory library The data environment, based on the analogy data environment, predictive execution of the database operation instruction; if the database operation instruction acquired by the acquisition module 41 is not a modified database type instruction, the database operation instruction is executed in the data base to The library operation instruction performs prediction execution.

Further, in the case that the database operation instruction acquired by the acquisition module 41 belongs to the modified database class instruction, the prediction execution module 42 executes the data environment of the analog database operation instruction in the locally established memory library, based on the analogy. When the data environment performs prediction operation on the database operation instruction, it is specifically used to: split the database operation instruction into a read instruction and a write instruction; execute a read instruction in the database to obtain a read data set, and read the data set The data environment stored in the memory bank to operate the instruction in the analog library; the write command is executed in the memory bank to modify the read data set.

In an optional implementation, the control execution module 43 is specifically configured to: deliver a locally recorded database operation instruction to the database, instruct the database to execute the database operation instruction, and receive the database operation instruction returned by the database The actual execution result; if the actual execution result is the same as the predicted execution result, the transaction commit instruction is sent to the database for the database to submit the target transaction; if the actual execution result is different from the predicted execution result, the transaction is sent to the database for recovery. An instruction for the repository to roll back the target transaction. Considering the atomicity of the transaction, the control execution module 43 can avoid the error of the transaction execution process by comparing the actual execution result with the predicted execution result, which is beneficial to improving the success probability of the transaction execution.

Further, when the control execution module 43 sends the locally recorded database operation instruction to the database, the control execution module 43 can be used to: simultaneously send the locally recorded database operation instruction to the data library, which is beneficial to saving network resources.

Further, the control execution module 43 can send all the database operation instructions recorded locally together with the locally recorded predicted execution data to the database, which is beneficial to save network resources.

In an optional implementation, the control execution module 43 is specifically configured to: determine, according to the locally recorded database operation instruction, whether the target transaction is a stand-alone transaction; if the determination result is yes, according to the locally recorded database operation instruction and Predicting the execution data, the single-machine transaction processing logic controls the database to actually execute the target transaction; if the judgment result is no, the distributed transaction processing logic controls the database to actually execute the target transaction according to the locally recorded database operation instruction and the predicted execution data. . Since the processing logic of the decentralized transaction is different from the processing logic of the stand-alone transaction, the processing logic of the stand-alone transaction is relatively simple, for example, it does not involve problems such as reading and writing locks, so the resources consumed are relatively small. Based on this, the control execution module 43 performs processing by using the processing logic of the single-machine transaction when identifying the target transaction as a stand-alone transaction, which is advantageous for improving processing efficiency and saving processing cost.

In an optional implementation, the predictive execution module 42 is further configured to delete the locally recorded database operation instruction and the predicted execution data when the transaction recovery instruction in the target transaction is acquired.

The database operating device provided in this embodiment can be deployed separately, and is located between the application server and the database, and can also be deployed on one end of the application server, or can be deployed on one end of the database.

The database operation device provided in this embodiment cooperates with the application server to join the prediction execution process in the process of executing the target transaction by the application server, and obtains and records all the database operation instructions that need to be executed in the target transaction in advance, and only belongs to The database operation instruction for modifying the database class instruction records the prediction execution data generated by the prediction execution to adapt to the read isolation level, provides conditions for the real execution transaction, and then controls the application according to the recorded database operation instruction and the prediction execution data. The database corresponding to the server actually executes the target transaction, which is beneficial to improve execution efficiency and increase transaction volume.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or may be Consolidate to another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of a hardware or a hardware plus a soft functional unit.

The integrated unit described above in the form of a software functional unit can be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the embodiments of the present invention. Part of the steps of the method. The foregoing storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM), Random Access Memory (RAM), disk or CD, etc. Media.

It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and are not limited thereto; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the foregoing embodiments are modified, or the equivalents of the technical features are replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims (12)

 A database operation method, comprising: acquiring, in a process of executing a target transaction by an application server, a database operation instruction in the target transaction executed by the application server; and predicting the database operation instruction Executing, returning the predicted execution result to the application server for the application server to determine the next database operation instruction to be executed, and locally recording the database operation instruction and the operation instruction in the database belongs to the modification database class The instruction execution data is recorded when the instruction is executed; and when the transaction commit instruction in the target transaction is obtained, the database corresponding to the application server is controlled according to the database operation instruction and the predicted execution data recorded locally. The target transaction is actually executed.    The method of claim 1, wherein the method further comprises: configuring the database to read the submitted isolation level before the application server executes the target transaction.    The method of claim 1, wherein the predictive execution of the database operation instruction comprises: if the database operation instruction belongs to a modified database class instruction, analogy in the locally established memory library The data environment of the database operation instruction, predictive execution of the database operation instruction based on the analog data environment; and if the database operation instruction is not a modified database type instruction, executing the database operation instruction in the database To perform predictive execution on the database operation instructions.    According to the method of claim 3, wherein the locally established memory library is analogous to the data environment required by the database operation instruction, and the database operation instruction is predicted and executed based on the analog data environment. The method includes: splitting the database operation instruction into a read instruction and a write instruction; executing the read instruction in the database to obtain a read data set, and storing the read data set in the memory library to compare the database a data environment of the operation instruction; and executing the write instruction in the memory library to modify the read data set.    The method according to any one of claims 1 to 4, wherein, according to the database operation instruction recorded locally and the predicted execution data, controlling a database corresponding to the application server to actually execute a target transaction, The method includes: sending the local database operation instruction to the database to instruct the database to execute the database operation instruction, and receiving an actual execution result of the database operation instruction returned by the database; if the actual execution The result is the same as the prediction execution result, and the transaction commit instruction is sent to the database for the database to submit the target transaction; and if the actual execution result is different from the predicted execution result, the transaction is sent to the database. Restore the instruction for the repository to roll back the target transaction.    The method of claim 5, wherein the database operation instruction for issuing the local record to the database comprises: simultaneously transmitting the locally recorded database operation instruction to the database.    A database operating device, comprising: an obtaining module, configured to sequentially acquire a database operation instruction in the target transaction executed by the application server during a process of executing a target transaction by the application server; predictive execution a module, configured to perform predictive execution on the database operation instruction, return the predicted execution result to the application server for the application server to determine the next database operation instruction to be executed, and record the database operation locally The instruction and the predicted execution data generated by the prediction execution when the database operation instruction belongs to the modification database class instruction; and the control execution module, configured to: when acquiring the transaction commit instruction in the target transaction, according to the local record The database operation instruction and the prediction execution data control the database corresponding to the application server to actually execute the target transaction.    The device of claim 7, further comprising: a configuration module, configured to configure the database to read the submitted isolation level before the application server executes the target transaction.    The device of claim 7, wherein the predictive execution module is specifically configured to: if the database operation instruction belongs to a modified database class instruction, compare the database operation instruction in a locally established memory library The data environment, based on the analog data environment, predictive execution of the database operation instruction; and if the database operation instruction is not a modified database type instruction, executing the database operation instruction in the database to The database operation instruction performs prediction execution.    The apparatus of claim 9, wherein the predictive execution module is specifically configured to: split the database operation instruction into a read instruction and a write instruction; execute the read instruction in the database to obtain a read a data set, the read data set is stored in the memory library to be analogous to the data environment of the database operation instruction; and the write instruction is executed in the memory library to modify the read data set.    The device according to any one of claims 7 to 10, wherein the control execution module is specifically configured to: deliver the locally recorded database operation instruction to the database to indicate that the database is executed The database operation instruction receives the actual execution result of the database operation instruction returned by the database; if the actual execution result is the same as the prediction execution result, the transaction submission instruction is issued to the database for the data The library submits the target transaction; and if the actual execution result is different from the predicted execution result, a transaction recovery instruction is issued to the database for the database to roll back the target transaction.    The device of claim 11, wherein the control execution module is configured to: simultaneously send the locally recorded database operation instruction to the database.