WO2017041637A1

WO2017041637A1 - Database operating method and device

Info

Publication number: WO2017041637A1
Application number: PCT/CN2016/097266
Authority: WO
Inventors: 王晶昱
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2015-09-08
Filing date: 2016-08-30
Publication date: 2017-03-16
Also published as: CN106503027A; CN106503027B

Abstract

A database operating method and device. The method comprises: in a process of executing a target transaction of an application server, acquiring sequentially database operation instructions in the target transaction executed by the application server (301); performing a speculative execution of the database operation instructions and returning the result of the speculative execution to the application server for the application server to determine a next database operation instruction to execute, and locally recording the database operation instruction and, if the database operation instruction belongs to a modification type of database instructions, recording speculative execution data generated by the speculative execution (302); and when a transaction commit instruction in the target transaction is acquired, controlling a database corresponding to the application server to actually execute the target transaction according to the locally recorded database operation instruction and the speculative execution data (303).

Description

Database operation method and device

The present application claims priority to Chinese Patent Application Serial No. No. No. No. No. No. No. No. No. No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

Technical field

The present application relates to the field of database technologies, and in particular, to a database operation method and apparatus.

Background technique

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 splitting conditions and jumps between these database operation instructions, meaning that the transaction is in one transaction. There may be some database operation instructions that are 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 has lower transaction throughput.

Summary of the invention

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

An aspect of the present application provides a database operation method, including:

And acquiring, in the process of executing the target transaction by the application server, the database operation instruction in the target transaction executed by the application server;

Performing predictive execution on the database operation instruction, 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 database The operation instruction belongs to the prediction execution data generated by the prediction execution when the database type instruction is modified;

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

In another aspect of the present application, a database operating device is provided, including:

An obtaining module, configured to acquire the application service in sequence during execution of a target transaction by the application server a database operation instruction in the target transaction to which the device executes;

a predictive execution module, configured to perform predictive execution on the database operation instruction, return a predicted execution result to the application server, for the application server to determine a next database operation instruction to be executed, and locally record the database operation And predicting execution data generated by the prediction execution when the database operation instruction belongs to modifying a database class instruction;

a control execution module, configured to: when the transaction commit instruction in the target transaction is obtained, control the database corresponding to the application server to actually execute the target transaction according to the database operation instruction recorded locally and the predicted execution data .

In the present application, 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 for the instructions belonging to the modified database class. The database operation instruction records the predicted execution data generated by the prediction execution to adapt to the read committed isolation level, provides conditions for the real execution of the transaction, and then controls the database corresponding to the application server to actually execute the target according to the recorded database operation instruction and the predicted execution data. Transactions help improve execution efficiency and increase transaction throughput.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are the present application. For some embodiments, other drawings may be obtained from those of ordinary skill in the art in light of the inventive workability.

1 is a deployment diagram of a database application system in the prior art;

2 is a deployment diagram of a database application system according to an embodiment of the present application;

FIG. 3 is a schematic flowchart of a database operation method according to an embodiment of the present application;

FIG. 4 is a schematic structural diagram of a database operating device according to an embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present application. It is a part of the embodiments of the present application, and not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts are Within the scope of this application.

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 multiple. Only one database 20 is shown by way of example in FIG. When it is desired to access the database 20 in a transactional manner, the application server 10 executes transaction logic to sequentially apply 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 throughput is lower.

In view of the deficiencies of the prior art, the present application provides a new database application system, as shown in FIG. 2 . The system adds a database operating device 30 between the application server 10 and the database 20. The database operating device 30 is configured to execute the database operation method provided by the present application, and implement a new transaction execution logic under the isolation level of the read commit, that is, the prediction execution is performed on the transaction, and the database operation to be performed in the transaction is obtained in advance. The instruction, the prediction of the execution path is implemented, and the read execution level is submitted only for the database execution instruction record of the database operation instruction record belonging to the modified database class instruction, and the database operation instruction generated based on the prediction execution is executed. And predicting execution data actually executing transactions on the database 20, which is beneficial to improve transaction execution efficiency and increase transaction throughput. Transaction throughput is 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 deployed at one end of the application server 10, or can be deployed in the database 20. Implemented at one end.

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

FIG. 3 is a schematic flowchart diagram of a database operation method according to an embodiment of the present application. 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 record the database operation instruction locally and when the database operation instruction belongs to the modified database type instruction The predicted execution data generated by the prediction execution is recorded.

303. When the transaction commit instruction in the target transaction is obtained, according to the locally recorded 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 on 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 rollback instruction, and the like. These instructions are actually statements written in the database language. Depending on the database language, 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. Some databases default to reading the isolation level that has been submitted. For example, the Oracle database defaults to read the isolation level that has been submitted. Some databases do not read the isolation level by default. For example, the MySQL database is repeatable by default. An isolation level. 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, you can configure the database to read this isolation level before the target server performs the target transaction.

Under the premise that the isolation level of the database is read and committed, the method provided in this embodiment can 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 database operation instructions in the target transaction executed by the application server during the execution of the target transaction by the application server.

In an alternative embodiment, the application server sends database operation instructions to the database in an existing manner to enable 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 to change the processing logic that originally sent the database operation instructions to the database to the database operating device. Based on this, the database operating device can receive the database operation instruction actively issued by the application server.

Herein, 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 obtains the database operation instruction executed by the application server. , can intercept the transaction start instruction in the target transaction sent by the application server to the database, and according to the transaction start instruction, know that the target transaction needs to be executed. Alternatively, the database operating 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 For 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 acquiring 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 database operation instruction to be executed. 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. The purpose of controlling the execution logic of the entire target transaction by the application server is achieved by returning the predicted execution result to the application server.

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 modification to the database, for example, an instruction starting with update, insert, etc.; generally, the instruction beginning with select is not a modified database type instruction. The predicted execution data mainly refers to some data in the process of predictive execution of database operation instructions.

For example, the database operating device can locally create a memory library, and store the acquired database operation instructions and predicted execution data into the 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 that has been submitted for reading on the basis of the core idea of predictive execution, this embodiment only records the prediction execution data generated by the prediction execution for the database operation instruction belonging to the modified database class instruction, but does not Record the predicted execution data corresponding to the database operation instruction that does not modify the database class instruction. 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 in the subsequent process of executing the target transaction in the database in the database operation instruction and the prediction execution data based on the local record. The amount of data to be processed is relatively small, which is beneficial to further improve execution efficiency and performance, and increase transaction throughput.

Among them, the operation of the database operation instruction on the database is mainly to access the data in the database, then the data environment of the database operation instruction can be simulated, and the database operation instruction is predicted and executed based on the simulated data environment. Further, considering that the database operation instruction that is not a modification of the database class instruction does not cause a change of the database, the database operation instruction can be directly predicted and executed in the database, which can save the operation of the simulation data environment, and is relatively simple to implement. Conducive to saving resources and improving execution efficiency. However, For database operation instructions belonging to the modified database class instructions, since it will cause changes in the database (mainly refers to the data in the database is changed), it is necessary to simulate the data environment and perform prediction execution in the simulated data environment.

Based on the above analysis, a way to predict execution of database operation instructions can be:

Identify the category of the obtained database operation instruction;

If the database operation instruction belongs to the modification database class instruction, the data environment of the database operation instruction is simulated in the locally created memory library, and the database operation instruction is predicted and executed based on the simulated data environment;

If the database operation instruction is not a modification database class instruction, the database operation instruction is executed in the database to perform prediction execution on the database operation instruction.

Further, a data environment simulating a database operation instruction in a locally created memory library, and an implementation manner of predicting execution of the database operation instruction based on the simulated data environment includes:

The obtained database operation instruction is split into a read instruction and a write instruction, and 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. Into the local memory library to simulate the data environment required for database operation instructions. Then, the write instruction is applied to the memory library to implement predictive execution of the database operation instruction, that is, the write instruction is executed in the memory library to modify the read data set, for example, to update or query the related data in the read data set. Wherein, executing a write instruction to modify the read data set may generate a result data set (affectRowInMemdb), the result data set including a 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 may locally record the read data set read by the read instruction and the result data set generated by executing the write instruction. As can be seen, the predicted execution data may include a read data set and a result data set, or may also include partial data in the read data set and the result data set, such as some data that can have a beneficial effect on actually executing the target transaction in the database. For example, various indexes of some values, such as a primary index, a secondary index, a primary key value, and the like.

When the database operation device acquires the transaction commit instruction in the target transaction (that is, the application server executes to the transaction commit instruction), the database corresponding to the locally recorded database operation instruction and the predicted execution data may be used to control the database corresponding to the application server to actually execute the target transaction.

In the foregoing, according to the locally recorded database operation instruction and the predicted execution data, an optional implementation manner of controlling the database corresponding to the actual execution target transaction of the application server includes:

The database operating device sends the locally recorded database operation instruction to the database to indicate the database Executing a database operation instruction, and receiving an actual execution result of the database operation instruction returned by the database; then, comparing the actual execution result of the database operation instruction with the predicted execution result, and if the actual execution result is the same as the predicted execution result, sending a transaction to the database The instruction is submitted for the database to submit the target transaction; if the actual execution result is different from the predicted execution result, a transaction rollback instruction is sent to the database for the database to roll 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, which is A lot of network resources will be consumed 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 database operation instructions of the local record, have been obtained in advance by the prediction execution process, so the database operation instruction of the local record is sent to the database to instruct the database to execute the database. During the operation of the instruction, the database operation instruction of the local record can be simultaneously and/or sent to the database, which is conducive to saving network resources. In addition, for some parallel database operation instructions, the database can also operate in parallel, which is beneficial to further improve transaction execution efficiency and increase transaction throughput.

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

Further, in an optional implementation manner of controlling the actual execution target transaction of the database corresponding to the application server according to the locally recorded database operation instruction and the predicted execution data, the database operation device may determine whether the target transaction is based on the locally recorded database operation instruction. For a stand-alone transaction; if the result of the determination is yes, according to the locally recorded database operation instruction and the predicted execution data, the single-machine transaction logic is used to control the database to actually execute the target transaction; if the judgment result is no, the database operation instruction according to the local record and Predictive execution data, with distributed transaction processing logic to control 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 database operation instruction recorded locally acts on the same physical device. If the determination result is yes, the target transaction can be determined to be a stand-alone transaction; if the determination result is no, the target transaction can be determined as Distributed transactions.

Because the processing logic of distributed transactions is different from the processing logic of stand-alone transactions, the processing logic of single-machine transactions is relatively simple, for example, it does not involve problems such as read-write and lock, so the resources consumed are relatively small. based on Therefore, in this embodiment, by identifying whether the target transaction is a stand-alone transaction, the processing logic of the single-machine transaction is processed when it is recognized as a stand-alone transaction, instead of uniformly processing the distributed transaction processing logic as in the prior art, which is advantageous for improving processing. Efficiency, saving processing costs.

In an optional implementation manner, if the database operation device acquires a transaction rollback instruction in the target transaction (that is, the application server performs a transaction rollback instruction), the database operation instruction of the local record and the prediction execution data may be deleted, for example, Clear the local memory library directly 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 rollback, the transaction efficiency can be improved by using the method of this embodiment.

It can be seen from the above that in the method provided by the embodiment, 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 the execution path of the target transaction can be obtained in advance during the predictive execution process. That is, the database operation instruction that really needs to be executed, and only the prediction execution data generated by the prediction execution of the database operation instruction belonging to the modified database class instruction is adapted to read the submitted isolation level, and the condition for the real execution transaction is provided, and then the record is based on the record. When the database operation instruction and the prediction execution data actually execute the target transaction, for example, based on the prediction execution data, related data information can be acquired in advance and jumps between instructions can be reduced, etc., thereby improving execution efficiency and increasing transaction throughput.

In the following, taking the inventory reduction transaction as an example, the workflow of the technical solution of the present application will be described in detail. 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:

Begin transaction

Select*from inventory where itemId=? (Use the product id to view the current inventory, note that there is no for update external display lock)

If(item.inventory>0)

Item.inventory--;

Update inventory set item.inventory=$item.inventory where itemId=?

Commit;

Else

Rollback; (If the current inventory is greater than 0, reduce, update the commodity inventory and submit, otherwise roll back)

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 executed by the application server, and needs to be executed. SQL statements, as well as commit/rollback instructions.

First, after starting the transaction, the database operating device creates a memory library locally;

When the database operating device gets select*from inventory where itemId=? For update this SQL statement, recognize that this SQL statement will not modify the database, so this SQL statement directly in the actual database, that is, execute the SQL statement in the database to obtain the query result, that is, read the data set , 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. Since it is a read isolation level, there is no need to record any data 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 determination result is yes, the current inventory quantity is reduced, and the update statement is executed, that is, 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 operation device will get the rollback statement. Once the database storage device obtains the rollback statement, the local memory library is cleared, mainly referring to the select*from inventory where itemId=? For update this SQL statement. In this case, because the transaction is not executed in the database, there is no need for the database 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=? In this SQL statement, it is recognized that the SQL statement will modify the database, so the SQL statement is disassembled into a read instruction, 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 (version) corresponding to the primary key. Then, according to update inventory set item.inventory=? Where itemId=? This statement is updated in the local memory library to obtain the resulting data set and return the resulting 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 modification 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 operating 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:

{

Select*from inventory where itemId=?

Update inventory set item.inventory=? Where itemId=? [readVersion:itemId=xxx and version=xxx/affectRow=1]

Commit()

}

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 performs the execution based on this, which is beneficial to save 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 executed the submission 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 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 application is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present application. In the following, 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 application.

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 application. As shown in FIG. 4, the apparatus 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 a database operation instruction in the target transaction executed by the application server during the execution of the target transaction by the application server.

The prediction 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 locally record the database operation instruction and the database operation instruction belongs to The predicted execution data generated by the prediction execution is recorded when the database class instruction is modified.

The control execution module 43 is configured to, when acquiring the transaction commit instruction in the target transaction, 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.

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 a database operation instruction sent by the application server to the database; or receive a database operation instruction that is 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 a transaction start instruction in the target transaction sent by the application server to the database; or receiving the application The transaction start instruction in the target transaction that the server actively delivers.

In an optional implementation, the prediction execution module 42 is specifically configured to:

If the database operation instruction acquired by the obtaining module 41 belongs to the modified database class instruction, the data environment of the database operation instruction is simulated in the locally created memory library, and the database operation instruction is predicted and executed based on the simulated data environment;

If the database operation instruction acquired by the obtaining module 41 does not belong to the modified database class instruction, the database operation instruction is executed in the database to perform prediction execution on the database operation instruction.

Further, in the case that the database operation instruction acquired by the obtaining module 41 belongs to the modified database class instruction, the prediction execution module 42 simulates the data environment of the database operation instruction in the locally created memory library, and operates the database based on the simulated data environment. When the instruction performs the operation of predictive execution, it is specifically used to:

Splitting database operation instructions into read instructions and write instructions;

Executing a read instruction in the database to obtain a read data set, and storing the read data set in a memory library to simulate a data environment of the database operation instruction;

A write instruction 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:

The database operation instruction of the local record is sent to the database to instruct the database to execute the database operation instruction, and receives the actual execution result of the database operation instruction returned by the database;

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, a transaction rollback instruction is issued to the database for the database 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, and is beneficial to improving the success probability of the transaction execution.

Further, when the database execution instruction of the local record is sent to the database, the control execution module 43 can be used to: simultaneously send the database operation instruction of the local record to the database, which is beneficial to save 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.

Determining whether the target transaction is a stand-alone transaction according to a locally recorded database operation instruction;

If the result of the determination is yes, according to the locally recorded database operation instruction and the predicted execution data, the single-machine transaction logic is used to control the database to actually execute the target transaction;

If the result of the determination is no, the database actually controls the target transaction by the distributed transaction logic according to the locally recorded database operation instruction and the predicted execution data. Because the processing logic of distributed transactions is different from the processing logic of stand-alone transactions, the processing logic of single-machine transactions is relatively simple, for example, it does not involve problems such as read-write and lock, 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 beneficial to improve processing efficiency and save 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 rollback instruction in the target transaction is acquired.

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

The database operating device provided in this embodiment 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 data that the target transaction needs to execute in advance. The library operates on instructions and records the predicted execution data generated by the prediction execution only for the database operation instructions belonging to the modified database class instruction to adapt to the read committed isolation level, providing conditions for the real execution of the transaction, and then based on the recorded database operation instructions and predictions. Executing data and controlling the database corresponding to the application server to actually execute the target transaction is beneficial to improve execution efficiency and increase transaction throughput.

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 application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. 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 Can be integrated into 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 in an electrical, mechanical or other form.

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 application 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 hardware or in the form of hardware plus software functional units.

The above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium. The software functional unit described above 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 methods described in various embodiments of the present application. Part of the steps. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Finally, it should be noted that the above embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should Solution: The technical solutions described in the foregoing embodiments may be modified, or some of the technical features may be equivalently replaced; and the modifications or replacements do not deviate from the technical solutions of the embodiments of the present application. Spirit and scope.

Claims

A database operation method, comprising:

And acquiring, in the process of executing the target transaction by the application server, the database operation instruction in the target transaction executed by the application server;

Performing predictive execution on the database operation instruction, 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 database The operation instruction belongs to the prediction execution data generated by the prediction execution when the database type instruction is modified;

When the transaction commit instruction in the target transaction is obtained, the database corresponding to the application server is controlled to actually execute the target transaction according to the database operation instruction recorded locally and the predicted execution data.
The method of claim 1 further comprising:

The database is configured to read the committed isolation level before the application server executes the target transaction.
The method according to claim 1, wherein said predicting execution of said database operation instruction comprises:

If the database operation instruction belongs to a modification database class instruction, simulate a data environment of the database operation instruction in a locally created memory library, and perform prediction execution on the database operation instruction based on the simulated data environment;

If the database operation instruction does not belong to a modification database class instruction, the database operation instruction is executed in the database to perform prediction execution on the database operation instruction.
The method according to claim 3, wherein said data environment required for said database operation instruction is simulated in a locally created memory library, and said database operation instruction is predicted to be executed based on said simulated data environment ,include:

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 simulate a data environment of the database operation instruction;

The write instruction is executed in the memory bank to modify the read data set.
The method according to any one of claims 1 to 4, wherein the controlling the actual database corresponding to the application server according to the locally recorded database operation instruction and the predicted execution data Perform the target transaction, including:

And sending the locally recorded 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;

And 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, a transaction rollback instruction is sent to the database for the database to roll back the target transaction.
The method according to claim 5, wherein the issuing the database operation instruction of the local record to the database comprises:

The database operation instruction of the local record is simultaneously sent 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;

a predictive execution module, configured to perform predictive execution on the database operation instruction, return a predicted execution result to the application server, for the application server to determine a next database operation instruction to be executed, and locally record the database operation And predicting execution data generated by the prediction execution when the database operation instruction belongs to modifying a database class instruction;

a control execution module, configured to: when the transaction commit instruction in the target transaction is obtained, control the database corresponding to the application server to actually execute the target transaction according to the database operation instruction recorded locally and the predicted execution data .
The device according to claim 7, further comprising:

And a configuration module, configured to configure the database to read the submitted isolation level before the application server executes the target transaction.
The apparatus according to claim 7, wherein the prediction execution module is specifically configured to:

If the database operation instruction belongs to a modification database class instruction, simulate a data environment of the database operation instruction in a locally created memory library, and perform prediction execution on the database operation instruction based on the simulated data environment;

If the database operation instruction does not belong to a modification database class instruction, the database operation instruction is executed in the database to perform prediction execution on the database operation instruction.
The apparatus according to claim 9, wherein the prediction execution module is specifically configured to:

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 simulate a data environment of the database operation instruction;

The write instruction is executed in the memory bank 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:

And sending the locally recorded 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;

And 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, a transaction rollback instruction is sent to the database for the database to roll back the target transaction.
The device according to claim 11, wherein the control execution module is specifically configured to:

The database operation instruction of the local record is simultaneously sent to the database.