WO2024098858A1

WO2024098858A1 - Database access system and method, computer device, and storage medium

Info

Publication number: WO2024098858A1
Application number: PCT/CN2023/111555
Authority: WO
Inventors: 谭锦志; 邱炜伟; 盛威锋; 戴唯威; 胡麦芳
Original assignee: 杭州趣链科技有限公司
Priority date: 2022-11-08
Filing date: 2023-08-07
Publication date: 2024-05-16
Also published as: CN115729912A

Abstract

The present application relates to the technical field of computers, and discloses a database access system and method, a computer device, and a storage medium. The database access system comprises an application system 101 and an ORM execution engine 102. The application system 101 comprises a first ORM framework, the ORM execution engine 102 comprises a second ORM framework, and the ORM execution engine 102 is communicatively connected to a database 103. The first ORM framework is used for generating an operation request according to a service statement, and sending the operation request to the ORM execution engine 102. The second ORM framework is used for performing parsing after acquiring the operation request, to obtain an SQL statement, and executing the SQL statement to access data in the database 103. In the present application, the application system 101 does not need to be directly connected to the database 103, and only the ORM execution engine 102 needs to interact with the database 103, so as to achieve an access to the database 103, thereby ensuring the security of the database 103.

Description

Database access system, method, computer device and storage medium

This application claims priority to the Chinese patent application filed with the China Patent Office on November 8, 2022, with application number 202211391763.4 and invention name “Database access system, method, computer device and storage medium”, the entire contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of computer technology, and in particular to a database access system, method, computer device and storage medium.

Background technique

For an application system, a large amount of business data is stored in the database. When performing business operations, an application system often needs to access the database to read, modify or store the business data.

In the related art, after configuring the database account and password in each application system, the application system can interact directly with the database. Each application system is integrated with an ORM (Object Relational Mapping) framework. The ORM framework can automatically compile the object-oriented programming language written by the technician into a database operation language that can be recognized by the database. In this case, the technician can write an object-oriented business program in the application system, and then the ORM framework will execute the business program to automatically compile the business program into an operation program that can be recognized by the database, and execute the operation program to access the database.

However, when multiple application systems need to access the same database, each of the multiple application systems needs to configure the database account and password. Then each application system will know the database account and password. The widespread use of such private data will bring great security risks to the database, thereby reducing the security of the database.

Application Contents

The purpose of the embodiments of the present application is to provide a database access system, method, computer device and storage medium, including but not limited to solving the problem of low database security.

The technical solution adopted in the embodiment of the present application is:

In a first aspect, a database access system is provided, the database access system comprising an application system and an object relation mapping (ORM) execution engine, the application system comprising a first ORM framework, the ORM execution engine comprising a second ORM framework, the ORM execution engine being in communication connection with a database;

The first ORM framework is used to generate an operation request according to the business statement, and send the operation request to the ORM execution engine, wherein the operation request is used to request to operate the data in the database;

The second ORM framework is used to parse the operation request after obtaining the operation request to obtain an SQL (Structured Query Language) statement; execute the SQL statement to access the data in the database to obtain the execution result of the SQL statement.

In a second aspect, a database access method is provided, which is applied to a relational object mapping (ORM) execution engine, wherein the ORM execution engine includes a second ORM framework, the ORM execution engine is communicatively connected to an application system, the ORM execution engine is communicatively connected to a database, the application system includes a first ORM framework, and the method includes:

The second ORM framework obtains an operation request sent by the first ORM framework, where the operation request is generated by the first ORM framework according to a business statement, and is used to request an operation to be performed on the data in the database;

After acquiring the operation request, the second ORM framework parses the operation request to obtain a structured query language SQL statement;

The second ORM framework executes the SQL statement to access the data in the database and obtains the execution result of the SQL statement.

In a third aspect, a computer device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the above-mentioned database access method when executed by the processor.

In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above-mentioned database access method is implemented.

In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the steps of the above-mentioned database access method.

The beneficial effect of the database access system provided by the embodiment of the present application is that the application system includes a first ORM framework, the ORM execution engine includes a second ORM framework, and the ORM execution engine is connected to the database for communication. The first ORM framework generates an operation request based on the business statement, and then sends the operation request to the ORM execution engine, that is, the application system sends an operation request to the ORM execution engine when it needs to access the database. After that, after the second ORM framework in the ORM execution engine receives the operation request, it parses the operation request to obtain an SQL statement, which is a statement that the database can recognize. After that, the second ORM framework executes the SQL statement to access the data in the database. In this way, the application system does not need to directly connect to the database, so there is no need to configure the database password in the application system, and only the ORM execution engine needs to interact with the database to access the database, thereby ensuring the security of the database.

The beneficial effect of the database access method provided by the embodiment of the present application is that the ORM execution engine includes a second ORM framework, the ORM execution engine is connected to the application system for communication, and the ORM execution engine is connected to the database for communication, and the application system includes a first ORM framework. The second ORM framework in the ORM execution engine obtains the operation request sent by the first ORM framework, and the operation request is generated by the first ORM framework according to the business statement, that is, the application system sends an operation request to the ORM execution engine when it needs to access the database. Afterwards, the second ORM framework parses the operation request to obtain an SQL statement, which is a statement that can be recognized by the database. The second ORM framework executes the SQL statement to access the data in the database. In this way, the application system does not need to directly connect to the database, so there is no need to configure the database password in the application system, but only the ORM execution engine needs to interact with the database to achieve access to the database, thereby ensuring the security of the database.

It can be understood that the beneficial effects of the third, fourth and fifth aspects mentioned above can be found in the relevant description of the second aspect mentioned above, and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or exemplary technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic diagram of the structure of a database access system provided in an embodiment of the present application;

FIG2 is a flow chart of a database access method provided in an embodiment of the present application;

FIG3 is a schematic diagram of an operation request provided in an embodiment of the present application;

FIG4 is a schematic diagram of the interaction between an application system and an ORM execution engine provided in an embodiment of the present application;

FIG5 is a flow chart of another database access method provided in an embodiment of the present application;

FIG6 is a flowchart of another database access method provided in an embodiment of the present application;

7 is a flowchart of another database access method provided in an embodiment of the present application;

FIG8 is a schematic diagram of another interaction between an application system and an ORM execution engine provided in an embodiment of the present application;

FIG9 is a schematic diagram of the structure of another database access system provided in an embodiment of the present application;

10 is a schematic diagram of the structure of another database access system provided in an embodiment of the present application;

FIG11 is a schematic diagram of a middleware module provided in an embodiment of the present application;

12 is a schematic diagram of the structure of another database access system provided in an embodiment of the present application;

FIG. 13 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present application.

It should be understood that the "multiple" mentioned in this application refers to two or more. In the description of this application, unless otherwise specified, "/" means or, for example, A/B can mean A or B; "and/or" in this article is just a way to describe the association relationship of related objects, indicating that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist at the same time, and A exists alone. B. In addition, in order to clearly describe the technical solution of the present application, the words "first", "second" and the like are used to distinguish the same or similar items with substantially the same functions and effects. Those skilled in the art can understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit the difference.

Before explaining the embodiments of the present application in detail, the application scenarios of the embodiments of the present application are first described.

The following is an explanation of the ORM framework involved in the application scenario.

The business logic layer and the user interface layer are object-oriented. When the information of an object changes, it is necessary to save the object information in a database (including but not limited to a relational database). However, object-oriented languages cannot be used to update the data in the database. Therefore, it is necessary to write a very complex database language to update the data in the database.

The ORM framework is a technology that solves the language mismatch between object-oriented and database. Specifically, it automatically persists objects in the program to the database by describing the metadata mapping between the object and the database. In other words, the ORM framework is a bridge connecting the business logic layer and the database. In general, a persistent class in the metadata corresponds to a table in the database, each instance of the class corresponds to a record in the table, and each attribute of the class corresponds to each field in the table.

Since the ORM framework provides a mapping between a database and an object, we no longer need to deal with complex database languages when operating the data in the database. We can just operate it like we normally operate an object. The ORM framework can make development more object-oriented. For technical personnel, they only need to write object-oriented business programs, which makes program writing more convenient, thus improving development efficiency and reducing development costs.

Generally, an application system based on an ORM framework accesses a database by directly communicating with the database. Specifically, the ORM framework in the application system executes the business program written by the technician to automatically compile the business program into an operation statement (SQL statement in the embodiment of the present application) that can be recognized by the database, and executes the operation statement to access the database. In this case, the following problems may occur.

First, the database account and password must be configured in each application system that accesses the same database. In this case, on the one hand, the configuration complexity of the application system will be increased, and on the other hand, each application system will know the database account and password, which will bring great security risks to the database.

Second, the database is set with a maximum number of TCP (Transmission Control Protocol) connections, which means that the database only allows a limited number of application systems to connect. Each connection between an application system and the database will consume the database's TCP connection number, and the number of TCP connections consumed by the application system is defined by itself, which means that the application system can define the number of TCP connections between itself and the database. For the database, the overall number of TCP connections is uncontrollable. Consider an extreme case, if the number of TCP connections defined by an application system is the maximum number of TCP connections that the database can support, then this will cause the other application systems to be unable to connect to the database, thereby affecting the performance of the other application systems.

Third, this direct connection between the application system and the database cannot coordinate the management of the entire database access. Although the database comes with some control configurations, it cannot meet all business needs and cannot add more advanced, special, and customized restrictions to the entire database access, such as user system authentication, blacklists and whitelists, and traffic control.

Fourth, if the database itself needs to be replaced (for example, from a MySQL database to a PostgreSQL database), all application systems need to update the database-related code and configuration simultaneously. In this case, the application system is more complex, and if there is a problem with the synchronous update, it is easy to cause problems in deployment, operation and maintenance, and development.

Fifth, the application system itself does not have the ability to cache data. Furthermore, since an application system's operations on database tables may be modified by other application systems at any time, the effectiveness of the cache cannot be guaranteed even if the data is cached in the application system.

To this end, the embodiment of the present application provides a database access method. When accessing a database is required, the application system can send an operation request to the ORM execution engine, and then the ORM execution engine can process the operation request, and then the ORM execution engine interacts with the database to achieve access to the database. In this way, the application system does not need to directly connect to the database, so there is no need to configure the database password in the application system, thereby ensuring the security of the database.

The system architecture involved in the embodiments of the present application is described below.

FIG1 is a schematic diagram of a database access system provided in an embodiment of the present application. Referring to FIG1 , the database access system includes: an application system 101 and an ORM execution engine 102 .

The application system 101 includes a first ORM framework, which is used to generate an operation request when access to the database 103 is required. The application system 101 can be deployed on a terminal or a server. The application system 101 can be connected to an ORM execution engine. 102 communicates via a wired connection or a wireless connection. The number of application systems 101 can be one or more, and the multiple application systems 101 all communicate with the ORM execution engine 102.

The database access system may include one ORM execution engine 102, or may include multiple ORM execution engines 102, and the multiple ORM execution engines 102 as a whole act as an ORM execution engine cluster to communicate with one or more application systems 101, and the multiple ORM execution engines 102 as a whole act as an ORM execution engine cluster to communicate with the database 103. The ORM execution engine 102 includes a second ORM framework, and the second ORM framework is used to process the received operation request and interact with the database 103. The ORM execution engine 102 can be deployed on a server, which can be a single server or a server cluster consisting of multiple servers.

The ORM execution engine 102 may communicate with the database 103 through a wired connection or a wireless connection, and may also communicate with the application system 101 through a wired connection or a wireless connection.

For example: when the application system 101 needs to access the data in the database 103, the first ORM framework in the application system 101 generates an operation request to access the database 103 and sends it to the ORM execution engine 102. After receiving the operation request, the second ORM framework in the ORM execution engine 102 processes the operation request and interacts with the database 103 to implement the operation on the data in the database 103.

In the embodiment of the present application, the ORM execution engine 102 directly communicates with the database 103, and the application system 101 does not need to directly communicate with the database 103, but accesses the database 103 through the ORM execution engine 102, so there is no need to configure the password of the database 103 in the application system 101, and it is only necessary to configure the password of the database 103 in the ORM execution engine 102. In the embodiment of the present application, when there is only one ORM execution engine 102 in the database access system, it is only necessary to configure the password of the database 103 in this ORM execution engine 102; when there are multiple ORM execution engines 102 in the database access system, it is only necessary to configure the password of the database 103 in the ORM execution engine cluster composed of the multiple ORM execution engines 102. As a user-oriented system, the security level of the application system is lower than that of the ORM execution engine 102, that is, the security level of the ORM execution engine 102 is higher. Therefore, compared with the solution in the related art in which multiple application systems directly communicate with the database and configure the database password in multiple application systems, the database access system provided in the embodiment of the present application configures the password of the database 103 in the ORM execution engine 102, which can improve the security of the database 103.

The database access method provided in the embodiment of the present application is explained in detail below.

Fig. 2 is a flow chart of a database access method provided in an embodiment of the present application. The database access method is applied to the database access system described in the embodiment of Fig. 1 above. Referring to Fig. 2, the method includes the following steps.

Step 201: The first ORM framework generates an operation request according to the business statement.

The business statement is a statement written by the technician using an object-oriented programming language. Optionally, the first ORM framework integrated in the application system can be an ORM-based SDK (Software Development Kit) deployed in the application system. In this case, the technician can directly use the ORM programming syntax to write object-oriented business statements. After that, the first ORM framework can generate an operation request based on the business statement written by the technician. The operation request is used to request an operation on the data in the database.

In an embodiment of the present application, when the application system calls a business statement, the first ORM framework parses the business statement and encapsulates the parsed result to obtain an operation request. In this way, the operation request will include information related to the business statement, that is, it will include relevant information on the operation of the database. Optionally, the operation request may include information such as the object identifier, the operation type, the original data of the object identified by the object identifier, and the updated data of the object identified by the object identifier.

The object identifier is the identifier of the object in the database to be accessed by the application system. For example, the object identifier can be the name of a table in the database, which is not limited in the embodiments of the present application. The operation type is the type of operation performed by the application system on the object in the database. For example, the operation type can include adding (INSERT), deleting (DELETE), updating (UPDATE), and finding (FIND).

For example, FIG3 is a data diagram of an operation request. The operation request shown in FIG3 includes information related to database operations, such as operation type, table name, original table data, original SQL data, and update data.

Step 202: The first ORM framework sends the operation request to the ORM execution engine.

In the embodiment of the present application, the first ORM framework provides an interface for communicating with the ORM execution engine. Thus, after generating the operation request, the first ORM framework in the application system can send the operation request to the ORM execution engine through the interface.

As an example, if a user wants to view the order information of an account, the user can click an order information query button in an application system to trigger the operation of accessing the order information of the account in the database. At this time, the application system will call the business statement for querying the order information, and the first ORM framework can encapsulate the business statement to obtain the corresponding operation request and send the operation request to The ORM execution engine, the operation request is a request to query the order information of the user's account from the database. After receiving the operation request, the ORM execution engine can perform corresponding processing, specifically, the following steps 203-205 can be executed.

Step 203: The second ORM framework in the ORM execution engine obtains the operation request.

The second ORM framework is an ORM framework integrated in the ORM execution engine, and is used to process the operation request after obtaining the operation request, so as to implement the access operation to the database.

In this case, after the second ORM framework in the ORM execution engine obtains the operation request, it can know that the application system wants to access the database.

In a possible implementation, the first ORM framework in the application system can communicate directly with the second ORM framework in the ORM execution engine. In this case, the operation request sent by the first ORM framework to the ORM execution engine can be directly received by the second ORM framework, that is, the second ORM framework can directly receive the operation request sent by the first ORM framework.

In another possible implementation, the ORM execution engine includes a middleware module, and the middleware module can communicate with the application system, that is, the middleware module can communicate directly with the first ORM framework. In this case, the operation request sent by the first ORM framework to the ORM execution engine can be directly received by the middleware module. The middleware module can first receive the operation request sent by the first ORM framework, and then send the operation request to the second ORM framework when the database access condition is met.

The database access conditions can be set in advance, and the database access conditions can be set by the technical staff according to the business needs. Optionally, the database access conditions can include but are not limited to at least one of the following:

First, the number of database accesses is less than the first count threshold.

The first number threshold is the maximum number of times a database can be accessed within a certain period (such as one day, one month, etc.). The first number threshold can be set in advance, and the first number threshold can be set by a technician according to business needs.

In this case, if the number of database accesses is less than the first number threshold, it means that the number of database accesses has not reached the maximum number of times the database can be accessed, so the database can continue to be accessed, and the middleware module can send the operation request to the second ORM framework. If the number of database accesses is greater than or equal to the first number threshold, it means that the number of database accesses has exceeded the maximum number of times the database can be accessed, so the database cannot continue to be accessed, and the middleware module cannot send the operation request to the second ORM framework.

For example, if the first number threshold is 10, the current database access number is 5, and the current database access number (5) is less than the first number threshold (10), it can be determined that this access meets the database access condition, and the middleware module can send the operation request to the second ORM framework.

Second, the access count of the object to be accessed by the operation request is less than a second count threshold.

The second number threshold is the maximum number of times the object to be accessed by the operation request can be accessed within a certain period (such as one day, one month, etc.) The second number threshold can be set in advance, and the second number threshold can be set by the technical staff according to business needs.

In this case, the number of accesses to the object to be accessed by the operation request is less than the second number threshold, indicating that the number of accesses to the object to be accessed by the operation request has not reached the maximum number of times the object to be accessed by the operation request can be accessed, so the database can continue to be accessed, and the middleware module can send the operation request to the second ORM framework. The number of accesses to the object to be accessed by the operation request is greater than or equal to the second number threshold, indicating that the number of accesses to the object to be accessed by the operation request has exceeded the maximum number of times the object to be accessed by the operation request can be accessed, so the database cannot be accessed, and the middleware module cannot send the operation request to the second ORM framework.

For example, the second count threshold is 5, the number of accesses to the object to be accessed by the current operation request is 3, and the number of accesses to the object to be accessed by the current operation request (3) is less than the second count threshold (5), then it can be determined that the operation request meets the database access condition, and the middleware module can send the operation request to the second ORM framework.

Third, the application system has access rights to the object that the operation request wants to access.

The access rights of the object to be accessed by the operation request are used to restrict the access of some application systems to the object to be accessed by the operation request, that is, the application system with the access rights of the object to be accessed by the operation request is allowed to access the object, while the application system without the access rights of the object to be accessed by the operation request is not allowed to access the object. The access rights of the object to be accessed by the operation request can be set by the technician according to business needs.

After the middleware module receives the operation request, it can first check whether the application system that sent the operation request has the access rights to the object that the operation request wants to access. If the application system has the access rights to the object that the operation request wants to access, it means that the application system is allowed to access the object that the operation request wants to access, and then it can continue to access the database. The middleware module can then send the operation request to If the application system does not have the access rights to the object to be accessed by the operation request, it means that the application system is not allowed to access the object to be accessed by the operation request, and then the database cannot be accessed, and the middleware module cannot send the operation request to the second ORM framework.

Fourth, the application system has access rights to the database.

The access rights of a database are used to restrict the access of some application systems to the database. That is, application systems with access rights to the database are allowed to access the database, while application systems without access rights to the database are not allowed to access the database. The access rights of the database can be set by the technical staff according to the business needs.

After the middleware module receives the operation request, it can first check whether the application system that sends the operation request has the access rights to the database. If the application system has the access rights to the database, it means that the application system is allowed to access the database, and then it can continue to access the database, and the middleware module can send the operation request to the second ORM framework. If the application system does not have the access rights to the database, it means that the application system is not allowed to access the database, and then it cannot continue to access the database, and the middleware module cannot send the operation request to the second ORM framework.

Fifth, the operation type in the operation request is the operation type that the database allows to be performed on the object to be accessed by the operation request.

Technical personnel can set the types of operations that can be performed on objects in the database according to business needs, thereby limiting the operations of the application system on objects in the database.

After receiving the operation request, the middleware module can first check whether the operation type in the operation request is the operation type that the database allows to perform on the object to be accessed by the operation request. If the operation type in the operation request is the operation type that the database allows to perform on the object to be accessed by the operation request, it means that the operation type that the operation request wants to perform on the object is an allowed operation type, then the database can continue to be accessed, and the middleware module can send the operation request to the second ORM framework. If the operation type in the operation request is not the operation type that the database allows to perform on the object to be accessed by the operation request, it means that the operation type that the operation request wants to perform on the object is an unallowed operation type, then the database cannot be accessed, and the middleware module cannot send the operation request to the second ORM framework.

Of course, in the embodiment of the present application, the middleware module can send the operation request to the second ORM framework when any one of the above five conditions is met; or, the middleware module sends the operation request to the second ORM framework only when multiple of the above five conditions are met at the same time. In addition, in addition to the above five conditions, the technician can also set other conditions, which are not limited in the embodiment of the present application.

In an embodiment of the present application, database access conditions are set in advance in the middleware module. Only when the database access conditions are met will the middleware module send the operation request to the second ORM framework. In this case, the middleware module can coordinate and manage the access to the entire database well, while meeting all business needs and supporting more advanced, special, and customized management and control configurations.

Step 204: The second ORM framework parses the operation request to obtain an SQL statement.

SQL statements are used to operate on data in a database. For example, the SQL statement can be a DML (Data Manipulation Language) statement. Specifically, the SQL statement can be used to add, delete, update, and search for data in a database.

Since the operation request is generated by the first ORM framework according to the object-oriented business statement, the operation request includes object-oriented operation information. In this case, the second ORM framework in the ORM execution engine can parse the object-oriented operation request into an SQL statement, that is, parse the object-oriented operation request into an SQL statement that can be recognized by the database to access the data in the database.

In this case, the second ORM framework can obtain SQL statements that the database can recognize, and then interact with the database, so that the technician does not need to write complex SQL statements, which provides convenience for the technician and improves development efficiency. In addition, in the embodiment of the present application, there is no need for the application system to communicate directly with the database, and there is no need to configure the database account password in the application system, thereby ensuring the security of the database.

The second ORM framework parses the operation request to obtain an SQL statement, which is similar to the operation of a device in the related art parsing an operation request to obtain an SQL statement, and the embodiment of the present application will not elaborate on this.

Step 205: The second ORM framework executes the SQL statement to access the data in the database and obtain the execution result of the SQL statement.

In the embodiment of the present application, the second ORM framework provides an interface for communicating with the database, so the second ORM framework can communicate with the database through Access the database through this interface.

In this case, the second ORM framework executes the SQL statement, that is, interacts with the database through the interface provided in the second ORM framework, that is, operates on the object to be accessed by the operation request in the database, thereby obtaining the execution result, which is the request result of the operation request.

Furthermore, after obtaining the execution result of the SQL statement, the second ORM framework may return the execution result of the SQL statement as the request result of the operation request to the application system to respond to the operation request sent by the application system.

For example, Figure 4 is a schematic diagram of the interaction between the application system and the ORM execution engine. Referring to Figure 4, Figure 4 includes an application system 401 and an ORM execution engine 402. The application system 401 sends the operation request to the ORM execution engine 402, and the second ORM framework in the ORM execution engine 402 executes the SQL statement obtained by parsing the operation request, and after obtaining the execution result, sends the execution result of the SQL statement as the request result of the operation request to the application system 401.

Optionally, the ORM execution engine may further include a cache module. In this case, after the second ORM framework obtains the operation request, if the operation type in the operation request is other than the query type, the above steps 204-205 may be directly executed to obtain the request result of the operation request. If the operation type in the operation request is a query type, the above steps 204-205 may not be executed first, but the cache module may be queried first to see if there is the data to be queried by the operation request.

The cache module is in communication connection with the ORM execution engine, and the cache module stores multiple key-value pairs, and each of the multiple key-value pairs stores the request result of an operation request whose operation type is a query type. The key value in each of the multiple key-value pairs is a hash value obtained by hashing the operation request whose operation type is a query type, and the value value in each of the multiple key-value pairs is the request result of the operation request whose operation type is a query type. That is, for any key-value pair stored in the cache module, the key value in this key-value pair is a hash value of an operation request whose operation type is a query type, and the value value in this key-value pair is the request result of this operation request, that is, the data queried from the database by this operation request. By way of example, the cache module can be a key-value storage system, for example, the cache module can be a redis (REmoteDIctionary Server, data structure server) cache system.

Specifically, after the second ORM framework obtains the operation request, if the operation type in the operation request is a query type, the second ORM framework performs a hash operation on the operation request to obtain a hash value; queries the cache module for a key value identical to the hash value; if a key value identical to the hash value is queried from the cache module, the value in the key-value pair of the key value identical to the hash value in the cache module is determined as the request result of the operation request. If a key value identical to the hash value is not queried from the cache module, the above steps 204-205 are executed, that is, the operation request is parsed to obtain the SQL statement, and the SQL statement is executed to access the data in the database, and the execution result of the SQL statement is obtained as the request result of the operation request. In this case, a target key-value pair can also be generated and stored in the cache module.

The key value in the target key-value pair is the hash value of the operation request. The value value in the target key-value pair is the execution result of the SQL statement, that is, the request result of the operation request, that is, the data queried from the database after executing the SQL statement.

If the key value that is the same as the hash value is found in the cache module, it means that the cache module contains the request result of the operation request, that is, the data that the application system wants to query. Then the value in the key-value pair containing the key value that is the same as the hash value in the cache module can be determined as the request result of the operation request, and the request result of the operation request can be further returned to the application system.

If the key value identical to the hash value is not found in the cache module, it means that the request result of the operation request does not exist in the cache module, that is, the data to be queried by the application system does not exist. The second ORM framework can parse the operation request, obtain the SQL statement, execute the SQL statement to access the data in the database, and obtain the execution result of the SQL statement as the request result of the operation request, and then generate the target key-value pair, and store the target key-value pair in the cache module. At this time, the request result of the operation request exists in the cache module. Furthermore, the second ORM framework can return the request result of the operation request to the application system.

In this way, when the application system needs to frequently and massively query data, the access pressure of the database can be reduced through the cache module. And for the users of the application system, they will not perceive the existence of the cache module when accessing the database. In addition, since the ORM execution engine accesses the cache module much faster than the database, when the data to be queried exists in the cache module, the data stored in the cache module is directly returned to the application system, which can improve the data query efficiency, which is equivalent to improving the database access efficiency for the application system.

For example, Fig. 5 is a flowchart of accessing a database when the operation type in the operation request is a query type. Referring to Fig. 5 , it includes steps 501 to 506 .

Step 501: The second ORM framework performs a hash operation on the operation request to obtain a hash value.

Step 502: The second ORM framework queries the cache module for a key value that is the same as the hash value.

Step 503: If the second ORM framework finds a key value identical to the hash value from the cache module, the value in the key-value pair where the key value is located is determined as the request result of the operation request and returned to the application system.

Step 504: If the second ORM framework does not find the key value identical to the hash value from the cache module, it reads the data to be queried by the operation request from the database.

Specifically, the second ORM framework parses the operation request to obtain the SQL statement, executes the SQL statement to read the data to be queried by the operation request from the database, and obtains the execution result of the SQL statement. Afterwards, the second ORM framework continues to execute step 505.

Step 505 : the second ORM framework determines the execution result of the SQL statement as the request result of the operation request and returns it to the application system, and the second ORM framework executes step 506 .

Step 506: The second ORM framework generates a target key-value pair and stores the target key-value pair in a cache module.

In some cases in the embodiment of the present application, the key-value pairs in the cache module can be deleted, which are specifically described below:

Optionally, when storing a key-value pair in the cache module, the key-value pair may be stored in association with the object identifier of the object to which the value in the key-value pair belongs. In this case, the value in the key-value pair stored in association with the object identifier of an object in the cache module is the data of the object.

For example, the association relationship between the key-value pairs and object identifiers in the cache module is shown in Table 1. The object identifier of the object to which the value in each of the three key-value pairs in Table 1 belongs is Table1, so the three key-value pairs are all associated with Table1 for storage.

Table 1

The embodiment of the present application only uses Table 1 above as an example to illustrate the association between the key-value pairs and the object identifiers in the cache module. Table 1 above does not limit the embodiment of the present application.

The first possible implementation method is that after the second ORM framework obtains the operation request, if the operation type in the operation request is an update type, it can first delete all key-value pairs stored in the cache module that are associated with the object identifier in the operation request, and then obtain the request result of the operation request through the above steps 204-205.

Since the operation type in the operation request is an update type, the purpose of this database access is to update the object identified by the object identifier in the operation request. If the data of the object identified by the object identifier in the operation request in the database changes, the value in the key-value pair associated with the object identifier in the operation request in the cache module will not be the latest data of the object identified by the object identifier. Therefore, all key-value pairs associated with the object identifier in the operation request in the cache module must be deleted.

A second possible implementation method is that after the second ORM framework obtains the operation request, if the operation type in the operation request is an update type, it first obtains the request result of the operation request through the above steps 204-205, and then deletes all key-value pairs stored in the cache module in association with the object identifier in the operation request.

A third possible implementation manner, for example, FIG6 is a flowchart of accessing a database when the operation type in the operation request is an update type. Referring to FIG6 , it includes steps 601 to 603 .

Step 601: after obtaining the operation request, if the operation type in the operation request is an update type, the second ORM framework deletes all key-value pairs stored in the cache module in association with the object identifier in the operation request.

Step 602: The second ORM framework obtains the request result of the operation request through the above steps 204 to 205.

That is, the second ORM framework parses the operation request to obtain the SQL statement, executes the SQL statement to update the object to be accessed by the operation request in the database, and obtains the execution result of the SQL statement. The second ORM framework can determine the execution result of the SQL statement as the request result of the operation request and return it to the application system.

Step 603: The second ORM framework deletes again all key-value pairs stored in the cache module in association with the object identifier in the operation request.

Consider a situation where, after the second ORM framework deletes all key-value pairs stored in the cache module in association with the object identifier in the operation request for the first time, there is another application system that queries the data of the object identified by the object identifier in the operation request. After reading the data to be queried, the other application system will re-store a key-value pair in the cache module, and this key-value pair is stored in association with the object identifier in the operation request. However, at this time, the second ORM framework has not yet updated the object to be accessed by the operation request in the database. In this case, after updating the object to be accessed by the operation request in the database, the data of the object stored in the database is different from the value in the key-value pair cached in the cache module. Then, by deleting all key-value pairs stored in association with the object identifier in the operation request in the cache module again, it can be ensured that after the data is updated, no key-value pairs stored in association with the object identifier in the operation request are stored in the cache module, thereby ensuring the consistency of the data in the database and the data cached in the cache module.

It is worth noting that the database access method provided by the embodiment of the present application does not need to configure the database account password in the application system, which reduces the configuration complexity of the application system, protects privacy data, and reduces data security risks. In addition, since the application system does not need to directly connect to the database, it no longer consumes the number of TCP connections of the database. For the database, the overall number of TCP connections is controllable and manageable.

Another point worth noting is that when there is a need to change the database, the database can be changed directly in the ORM execution engine. For the application system, the application system will not perceive the change of the database, so it will not affect the application system.

In an embodiment of the present application, the ORM execution engine includes a second ORM framework, the ORM execution engine is communicatively connected to the application system, and the ORM execution engine is communicatively connected to the database, and the application system includes a first ORM framework. The second ORM framework in the ORM execution engine obtains an operation request sent by the first ORM framework, and the operation request is generated by the first ORM framework according to the business statement, that is, the application system sends an operation request to the ORM execution engine when it needs to access the database. Afterwards, the second ORM framework parses the operation request to obtain an SQL statement, which is a statement that can be recognized by the database. The second ORM framework executes the SQL statement to access the data in the database. In this way, the application system does not need to directly connect to the database, so there is no need to configure the database password in the application system, but only the ORM execution engine needs to interact with the database to access the database, thereby ensuring the security of the database.

The above explains how the ORM execution engine processes an operation request when the application system sends it. The following explains how the ORM execution engine processes multiple operation requests when the application system sends them.

First, the relevant concepts of the affairs involved in the embodiments of the present application are explained.

A transaction is a collection of operations that form a single logical unit of work. A transaction can contain one or more operations that form a logical whole. These operations that form the logical whole are either all executed successfully or not executed at all. In other words, all the operations that constitute a transaction either have an impact on the database or have no impact at all, so that the database can always maintain a consistent state regardless of whether the transaction is executed successfully.

Transactions have ACID characteristics, which are: Atomicity: All operations in a transaction are inseparable as a whole, either all succeed or all fail. Consistency: The execution result of a transaction must make the database go from one consistent state to another. Isolation: Concurrently executed transactions will not affect each other, and their impact on the database is the same as when they are executed serially. Durability: Once a transaction is committed, its updates to the database are persistent.

In some embodiments, there are two situations in which transactions are used, and whether to automatically commit the transaction is determined by starting a transaction statement.

If the ORM execution engine does not receive the start transaction statement, the transaction is automatically submitted, that is, a non-persistent transaction is executed. Specifically, each time the ORM execution engine receives an operation request, it will submit a SQL statement obtained by parsing the operation request after execution. At this time, each SQL statement obtained is actually executed as a transaction. That is, in the above step 205, the second ORM framework will instruct the database to submit the execution result of the SQL statement after obtaining the execution result of the SQL statement. In this case, the automatic submission mode in the database access mode is used to implement access to data in the database.

If the ORM execution engine receives a start transaction statement, it will not automatically commit the transaction, that is, execute a persistent transaction. Specifically, when the ORM execution engine receives multiple operation requests, it will execute the multiple SQL statements obtained by parsing these multiple operation requests as a transaction, and commit or roll back the execution results of these multiple SQL statements at the same time. In this case, the manual commit mode in the database access mode is used to access the data in the database. This situation is explained in detail below.

Fig. 7 is a flow chart of a database access method provided in an embodiment of the present application. Referring to Fig. 7, the method includes the following steps.

Step 701: The first ORM framework sends a start transaction statement to the ORM execution engine.

The start transaction statement is used to instruct the ORM execution engine to start a transaction to resolve multiple operation requests subsequently sent by the first ORM framework. The multiple SQL statements obtained by the analysis are executed as a transaction, that is, multiple SQL statements are committed or rolled back at the same time.

When the application system determines that multiple database operations need to be performed in one transaction, the first ORM framework in the application system will send a start transaction statement to the ORM execution engine to instruct the ORM execution engine to create a transaction, thereby implementing the execution of multiple SQL statements obtained by parsing multiple operation requests subsequently sent by the first ORM framework as a transaction.

Optionally, the application system and the ORM execution engine can communicate through the GRPC (Google Remote Procedure Call) protocol.

In this case, when there is an ORM execution engine cluster including multiple ORM execution engines, if an application system establishes a connection with an ORM execution engine in the ORM execution engine cluster for the first time, the communication connection between the application system and the ORM execution engine is not interrupted, and the application system can continuously send multiple operation requests to the ORM execution engine. In this way, it can be ensured that the multiple operation requests sent by the first ORM framework after sending the start transaction statement are all sent to the same ORM execution engine, so that the ORM execution engine can execute the multiple SQL statements obtained by parsing the received multiple operation requests in the same transaction.

Step 702: After obtaining the start transaction statement, the second ORM framework in the ORM execution engine creates a target transaction.

Optionally, the middleware module in the ORM execution engine may receive a start transaction statement sent by the first ORM framework, and then send the start transaction statement to the second ORM framework.

After obtaining the start transaction statement, the second ORM framework in the ORM execution engine will create a target transaction. After that, the second ORM framework can use the multiple SQL statements obtained by parsing the multiple operation requests subsequently sent by the first ORM framework as SQL statements to be executed by the target transaction. Multiple SQL statements in the target transaction can be committed or rolled back at the same time. That is, target transaction commit means committing the execution results of multiple SQL statements in the target transaction at the same time; target transaction rollback means rolling back the execution results of multiple SQL statements in the target transaction at the same time.

The operation of the second ORM framework to create a target transaction is similar to the operation of a device creating a transaction in the related art, and the embodiment of the present application will not elaborate on this.

Step 703: The first ORM framework sends multiple operation requests to the ORM execution engine.

Optionally, after sending a start transaction statement to the ORM execution engine, the first ORM framework may continuously send multiple operation requests to the ORM execution engine through the GRPC protocol, each of the multiple operation requests being used to request an operation on data in the database.

Step 704: Whenever the second ORM framework obtains an operation request, it parses the obtained operation request to obtain the SQL statement belonging to the target transaction, and executes the latest obtained SQL statement belonging to the target transaction.

Optionally, the middleware module in the ORM execution engine may receive an operation request sent by the first ORM framework, and each time the middleware module receives an operation request, it may send the operation request to the second ORM framework if the database access condition is met.

Among them, the first ORM framework sends an operation request to the ORM execution engine. The processing process of the second ORM framework in the ORM execution engine on this operation request can refer to the relevant operations in the embodiment of Figure 2 above, and the embodiment of this application will not be repeated here.

Specifically, each time the second ORM framework obtains an operation request, it parses the operation request, obtains the SQL statement belonging to the target transaction, executes the latest SQL statement belonging to the target transaction, and obtains the execution result. In this case, after the first ORM framework sends multiple operation requests to the ORM execution engine, the second ORM framework executes the SQL statement obtained by parsing each of the multiple operation requests, and obtains the execution results of multiple SQL statements in the target transaction. Each time the execution result of an SQL statement is obtained, the execution result of the SQL statement can be returned to the application system as the request result of the corresponding operation request. In addition, in this case, each time the second ORM framework obtains the execution result of an SQL statement, it does not instruct the database to submit the execution result of the SQL statement.

For example, FIG8 is a schematic diagram of the interaction between the application system and the ORM execution engine. Referring to FIG8 , FIG8 includes an application system 801 and an ORM execution engine 802. After the application system 801 sends a start transaction statement to the ORM execution engine 802, it sends multiple operation requests. Every time the second ORM framework in the ORM execution engine 802 obtains an operation request, it executes the SQL statement belonging to the target transaction obtained by parsing the operation request, obtains the execution result of the SQL statement, and then sends the execution result of the SQL statement as the request result of the operation request to the application system 801, thereby sending the request result of each operation request in the multiple operation requests to the application system 801.

Step 705: The first ORM framework sends a commit statement or a rollback statement to the ORM execution engine.

The commit statement is used to instruct the target transaction to be committed, that is, to instruct the database to perform the execution results of all SQL statements in the target transaction. The rollback statement is used to instruct the target transaction to be rolled back, that is, to instruct the database to roll back the execution results of all SQL statements in the target transaction.

Step 706: If the second ORM framework obtains the commit statement, it instructs the database to commit the execution results of all SQL statements in the target transaction.

Optionally, the middleware module in the ORM execution engine may receive a commit statement sent by the first ORM framework, and then send the commit statement to the second ORM framework.

In some embodiments, before the execution results of all SQL statements in the target transaction are submitted, the operation on the data in the database is not actually completed, and the second ORM framework executes these SQL statements, which is manifested as the database recording the operation information of multiple operations on the objects in the database. Only when the database receives the commit instruction, will it submit the execution results of all SQL statements in the target transaction, that is, it truly realizes the operation on the data in the database, and performs multiple operations on the database at the same time.

Step 707: If the second ORM framework obtains a rollback statement, it instructs the database to roll back the execution results of all SQL statements in the target transaction.

Optionally, the middleware module in the ORM execution engine may receive a rollback statement sent by the first ORM framework, and then send the rollback statement to the second ORM framework.

In this case, the database rolls back the execution results of all SQL statements in the target transaction, that is, cancels the operations performed on the data in the database by all SQL statements in the target transaction. In some embodiments, the operation information recorded in the database that performs multiple operations on the objects in the database is deleted.

The following example illustrates the beneficial effects of multiple accesses to data in a database within one transaction.

Suppose a user purchases a product in an application system. When purchasing a product, payment is required and order information is generated after the purchase. At this time, it is necessary to reduce the user's account balance and add a new order information to the user's order list.

If these two operations are not performed in the same transaction, the application system first sends an operation request to modify the balance to the ORM execution engine. The ORM execution engine parses the operation request to obtain a SQL statement to modify the balance, then executes the SQL statement and submits the execution result to complete the modification of the user's account balance. The application system then sends an operation request to add order information to the ORM execution engine. The ORM execution engine parses the operation request to obtain a SQL statement to add order information. However, a network failure occurs when the ORM execution engine executes the SQL statement. At this time, the operation of adding a new order information to the user's order list cannot be completed. In this case, the user can find that his account balance has decreased, but cannot find the order information for the purchased goods.

If these two operations are executed in one transaction, the application system first sends a start transaction statement to the ORM execution engine, and then the ORM execution engine creates a target transaction. The application system then sends an operation request to modify the balance and an operation request to add order information to the ORM execution engine. After receiving the operation request to modify the balance, the ORM execution engine parses the operation request to obtain an SQL statement to modify the balance, executes the SQL statement but does not submit the execution result. Afterwards, after receiving the operation request to add order information, the ORM execution engine parses the operation request to obtain an SQL statement to add order information, executes the SQL statement but does not submit the execution result. In some embodiments, the application system sends a commit statement to the ORM execution engine, and the ORM execution engine instructs the database to submit the execution results of the two SQL statements in the target transaction to truly modify the user account balance and add order information to the order list. At this time, the user can query that the balance of his account has decreased and there is order information for purchasing goods in the order list. In other embodiments, even if a network failure occurs, the ORM execution engine will not instruct the database to submit the execution results of the two SQL statements in the target transaction before receiving the commit statement, so that the data in the database will not change. At this time, the user will find that the balance of his account has not decreased, and no new order information will be added to the order list. In this way, executing multiple operations in one transaction can ensure the consistency of multiple operations during execution.

In an embodiment of the present application, the first ORM framework sends a start transaction statement to the ORM execution engine to instruct the second ORM framework to create a target transaction, so that multiple SQL statements obtained by parsing multiple operation requests subsequently sent by the first ORM framework can be executed in the target transaction. After that, the first ORM framework sends a commit statement or a rollback statement to the ORM execution engine so that the second ORM framework instructs the database to simultaneously commit or roll back the execution results of all SQL statements in the target transaction. In this way, it can be ensured that multiple operations with associations can be submitted in the database at the same time, ensuring the consistency of these multiple operations during execution, thereby ensuring the consistency of the database.

The database access system provided in the embodiment of the present application is explained below.

FIG9 is a schematic diagram of the structure of a database access system provided in an embodiment of the present application. Referring to FIG9, the database access system includes The ORM execution engine cluster includes multiple application systems 101 and an ORM execution engine cluster. The ORM execution engine cluster can be composed of multiple ORM execution engines 102.

Any application system 101 among the multiple application systems 101 can communicate with any ORM execution engine 102 in the ORM execution engine cluster.

The application system 101 is explained below:

Each of the multiple application systems 101 includes a first ORM framework. The first ORM framework can generate an operation request according to a business statement and send the operation request to the ORM execution engine 102.

The operation request is used to request to operate the data in the database 103. The first ORM framework sends the operation request to the ORM execution engine 102 to send the operation request to any one of the ORM execution engines 102 in the ORM execution engine cluster.

The first ORM framework generates an operation request according to the business statement, and the relevant content of sending the operation request to the ORM execution engine 102 has been described in detail in steps 201 and 202 in the embodiment of FIG. 2 , and will not be repeated in the embodiment of the present application.

In this case, the application system 101 only needs to generate an operation request according to the business statement written by the technician using the object-oriented language, and send the operation request to the ORM execution engine 102. There is no need to parse the business statement written by the technician using the object-oriented language. In this way, the business pressure of the application system 101 can be reduced, thereby improving the performance of the application system 101.

The ORM execution engine 102 is explained below:

Each of the multiple ORM execution engines 102 in the ORM execution engine cluster is in communication connection with the database 103. In some embodiments, the multiple ORM execution engines 102 in the ORM execution engine cluster can communicate with each other to achieve data sharing.

Each of the multiple ORM execution engines 102 in the ORM execution engine cluster includes a second ORM framework. The second ORM framework can execute steps 203 to 205 in the embodiment of FIG. 2 , that is, to obtain the operation request sent by the first ORM framework, parse the operation request, obtain an SQL statement, execute the SQL statement, access the data in the database 103, and obtain the execution result of the SQL statement.

In this case, the ORM execution engine 102 acts as a bridge between the application system 101 and the database 103, so that the application system 101 does not need to directly connect to the database 103, but the ORM execution engine 102 communicates with the database 103 to access the database 103. Therefore, there is no need to configure the account password of the database 103 in the application system 101, which improves the security of the database 103.

Optionally, the application system 101 and the ORM execution engine 102 can communicate via the GRPC protocol. In this way, it can be ensured that multiple operation requests sent by the first ORM framework in an application system 101 are all sent to the same ORM execution engine 102, thereby ensuring that the SQL statements obtained by parsing the multiple operation requests can be executed in one transaction. The above-mentioned embodiment of Figure 7 explains the process of executing multiple SQL statements obtained by parsing multiple operation requests in one transaction, and the embodiment of this application will not be repeated here.

In one possible case, referring to FIG. 10 , the database access system may further include a middleware module 1001 , and the middleware module 1001 is in communication connection with the application system 101 , that is, the middleware module 1001 may directly communicate with the first ORM framework.

After receiving the operation request sent by the application system 101 , the middleware module 1001 may send the operation request to the second ORM framework 1002 if the database access condition is met.

For example, Fig. 11 is a schematic diagram of the middleware module 1001. Referring to Fig. 11, Fig. 11 includes an application system 101, a middleware module 1001, and a second ORM framework 1002. For example, the following database access conditions can be set in the middleware module 1001:

The number of accesses to the database 103 is less than a first number threshold (flow control).

The application system 101 has access rights (table authority control) to the object to be accessed by the operation request.

The application system 101 has access rights to the database 103 (account system authentication).

The operation type in the operation request is the type of operation that the database 103 allows to perform on the object to be accessed by the operation request (controlled by ORM syntax).

After receiving the operation request, the middleware module 1001 first determines whether the operation request satisfies the set database access condition. Only when the operation request satisfies the database access condition does the middleware module 1001 send the operation request to the second ORM framework 1002.

The relevant contents about the database access conditions have been explained in step 203 of the embodiment of FIG. 2 , and will not be described in detail in the embodiment of the present application.

In this case, by setting the database access conditions in the middleware module 1001, the ORM execution engine 102 can well coordinate and manage the access to the entire database 103, while meeting all business requirements and supporting more advanced, special, and customized management. Control configuration.

In one possible case, referring to FIG. 12 , the database access system may further include a cache module 1201, which is in communication connection with the ORM execution engine 102. The cache module 1201 stores a plurality of key-value pairs, and each of the plurality of key-value pairs stores a request result of an operation request of a query type. That is, the key value in each of the plurality of key-value pairs is a hash value obtained by performing a hash operation on the operation request of a query type, and the value value in each of the plurality of key-value pairs is a request result of an operation request of a query type. That is, for any key-value pair stored in the cache module 1201, the key value in the key-value pair is a hash value of an operation request of a query type, and the value value in the key-value pair is a request result of the operation request, that is, the data queried from the database 103 by the operation request.

In this case, when the operation type in the operation request is other types except the query type, the second ORM framework 1002 can directly execute the above steps 204 to 205 to obtain the request result of the operation request.

In the case where the operation type in the operation request is a query type, the second ORM framework may first perform a hash operation on the operation request to obtain a hash value; and query the cache module 1201 for a key value identical to the hash value. If a key value identical to the hash value is queried from the cache module 1201, the value in the key-value pair of the key value identical to the hash value in the cache module 1201 is determined as the request result of the operation request. If a key value identical to the hash value is not queried from the cache module 1201, the second ORM framework executes the above steps 204-205, that is, parses the operation request to obtain the SQL statement, executes the SQL statement to access the data in the database, and obtains the execution result of the SQL statement as the request result of the operation request. In this case, a target key-value pair may also be generated and stored in the cache module 1201.

In the case where the operation type in the operation request is an update type, the second ORM framework may delete all key-value pairs stored in the cache module 1201 in association with the object identifier in the operation request.

The interaction process between the ORM execution engine 102 and the cache module 1201 has been explained in step 205 of the embodiment of FIG. 2 , and will not be described in detail in the embodiment of the present application.

In the case where the database access system includes the cache module 1201, if the application system 101 needs to frequently and massively query data, the access pressure of the database 103 can be reduced through the cache module 1201. And for the user of the application system 101, the existence of the cache module 1201 will not be perceived when accessing the database 103. In addition, since the speed of the ORM execution engine 102 accessing the cache module 1201 is much faster than the speed of accessing the database 103, when the cache module 1201 contains the data to be queried, the data stored in the cache module 1201 is directly returned to the application system, which can improve the data query efficiency, which is equivalent to improving the database access efficiency for the application system 101.

It is worth noting that the application system 101 in the database access system provided in the embodiment of the present application does not need to be directly connected to the database 103, but accesses the database 103 by setting an ORM execution engine 102 between the application system 101 and the database 103. Specifically, the application system 101 sends an operation request to the ORM execution engine 102 to request access to the data in the database 103, and then the ORM execution engine 102 communicates with the database 103 to achieve access to the database 103. In this way, there is no need to configure the account password of the database 103 in the application system 101, which reduces the configuration complexity of the application system 101, protects privacy data, reduces data security risks, and thus ensures the security of the database 103.

Another point worth noting is that since the application system 101 does not need to directly connect to the database 103, the number of TCP connections of the database 103 is no longer consumed, which makes the overall number of TCP connections controllable and manageable for the database 103. At the same time, since the application system 101 and the ORM execution engine 102 in the database access system provided in the embodiment of the present application communicate through the GRPC protocol, which is an efficient multiplexing technology, the difficulty of connection pool management of the application system 101 is reduced.

In an embodiment of the present application, the application system includes a first ORM framework, the ORM execution engine includes a second ORM framework, and the ORM execution engine is connected to the database for communication. The first ORM framework generates an operation request based on the business statement, and then sends the operation request to the ORM execution engine, that is, the application system sends an operation request to the ORM execution engine when it needs to access the database. After that, after the second ORM framework in the ORM execution engine receives the operation request, it parses the operation request to obtain an SQL statement, which is a statement that the database can recognize. The second ORM framework then executes the SQL statement to access the data in the database. In this way, the application system does not need to directly connect to the database, so there is no need to configure the database password in the application system, and only the ORM execution engine needs to interact with the database to access the database, thereby ensuring the security of the database.

FIG13 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. As shown in FIG13 , the computer device 13 includes: a processor 130, a memory 131, and a computer program 132 stored in the memory 131 and executable on the processor 130. When executing the computer program 132, 130 implements the steps executed by the ORM execution engine in the database access method in the above embodiment.

The computer device 13 may be a general-purpose computer device or a special-purpose computer device. In a specific implementation, the computer device 13 may be a network server. Those skilled in the art will appreciate that FIG. 13 is merely an example of the computer device 13 and does not constitute a limitation on the computer device 13. The computer device 13 may include more or fewer components than shown in the figure, or may combine certain components, or different components, such as input and output devices, network access devices, etc.

The processor 130 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

In some embodiments, the memory 131 may be an internal storage unit of the computer device 13, such as a hard disk or memory of the computer device 13. In other embodiments, the memory 131 may also be an external storage device of the computer device 13, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card (Flash Card), etc. equipped on the computer device 13. Further, the memory 131 may also include both an internal storage unit of the computer device 13 and an external storage device. The memory 131 is used to store an operating system, an application program, a boot loader (Boot Loader), data, and other programs. The memory 131 may also be used to temporarily store data that has been output or is to be output.

An embodiment of the present application also provides a computer device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, and when the processor executes the computer program, the steps in any of the above-mentioned method embodiments are implemented.

An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

An embodiment of the present application provides a computer program product, which, when executed on a computer, enables the computer to execute the steps in the above-mentioned method embodiments.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above method embodiments, which can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of each of the above method embodiments can be implemented. Among them, the computer program includes computer program code, which can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may at least include: any entity or device that can carry the computer program code to the camera/terminal device, recording medium, computer memory, ROM (Read-Only Memory), RAM (Random Access Memory), CD-ROM (Compact Disc Read-Only Memory), magnetic tape, floppy disk and optical data storage device. The computer-readable storage medium mentioned in the present application can be a non-volatile storage medium, in other words, a non-transient storage medium.

It should be understood that all or part of the steps to implement the above embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The computer instructions can be stored in the above-mentioned computer readable storage medium.

In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

In the embodiments provided in the present application, it should be understood that the disclosed devices/computer equipment and methods can be implemented in other ways. For example, the device/computer equipment embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

The embodiments described above are only used to illustrate the technical solutions of the present application, rather than to limit them; although the present application is described in detail with reference to the aforementioned embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present application, and should all be included in the protection scope of the present application. The above are only optional embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included in the scope of the claims of the present application.

Claims

A database access system, characterized in that the database access system comprises an application system and an object relation mapping (ORM) execution engine, the application system comprises a first ORM framework, the ORM execution engine comprises a second ORM framework, and the ORM execution engine is in communication connection with a database;

The first ORM framework is used to generate an operation request according to the business statement, and send the operation request to the ORM execution engine, wherein the operation request is used to request to operate the data in the database;

The second ORM framework is used to parse the operation request after obtaining the operation request to obtain a structured query language SQL statement; execute the SQL statement to access the data in the database to obtain the execution result of the SQL statement.
The database access system according to claim 1, characterized in that:

The first ORM framework is used to send a start transaction statement to the ORM execution engine;

The second ORM framework is used to create a target transaction after obtaining the start transaction statement;

The first ORM framework is used to send multiple operation requests to the ORM execution engine after sending the start transaction statement to the ORM execution engine;

The second ORM framework is used for, after creating the target transaction, parsing each operation request to obtain an SQL statement belonging to the target transaction and executing the latest obtained SQL statement belonging to the target transaction;

The first ORM framework is used to send a commit statement or a rollback statement to the ORM execution engine;

The second ORM framework is used to instruct the database to commit the execution results of all SQL statements in the target transaction if the commit statement is obtained; and to instruct the database to roll back the execution results of all SQL statements in the target transaction if the rollback statement is obtained.
The database access system according to claim 1 is characterized in that the application system communicates with the ORM execution engine through a remote procedure call GRPC protocol.
The database access system according to any one of claims 1 to 3, characterized in that the ORM execution engine further comprises a middleware module, and the middleware module is in communication connection with the application system;

The middleware module is used for, after receiving the operation request sent by the first ORM framework, sending the operation request to the second ORM framework if a database access condition is met.
The database access system according to claim 4, characterized in that the operation request carries an object identifier and an operation type, and the object identifier is used to identify the object to be accessed by the operation request;

The database access condition includes at least one of the following:

The number of accesses to the database is less than a first number threshold;

The access count of the object to be accessed by the operation request is less than the second count threshold;

The application system has access rights to the object to be accessed by the operation request;

The application system has access rights to the database;

The operation type in the operation request is an operation type that the database allows to be performed on the object to be accessed by the operation request.
The database access system according to any one of claims 1 to 3, characterized in that the operation request carries an object identifier and an operation type, and the database access system further comprises a cache module;

The second ORM framework is used to perform a hash operation on the operation request to obtain a hash value when the operation type in the operation request is a query type; query the key value that is the same as the hash value from the cache module, and determine the request result of the operation request based on the query result.
The database access system according to claim 6 is characterized in that if the query result is a key value identical to the hash value queried from the cache module, the value value in the key-value pair in the cache module where the key value identical to the hash value is located is determined as the request result of the operation request.
The database access system according to claim 6 is characterized in that if the query result is that the key value identical to the hash value is not found in the cache module, the operation request is parsed to obtain the SQL statement, and the SQL statement is executed. statement to access the data in the database, and obtain the execution result of the SQL statement as the request result of the operation request.
The database access system according to claim 8 is characterized in that the second ORM framework is also used to generate a target key-value pair, store the target key-value pair in the cache module, the key value in the target key-value pair is the hash value, and the value value in the target key-value pair is the execution result of the SQL statement.
The database access system according to claim 7, characterized in that the cache module is used to associate and store the key-value pair with the object identifier of the object to which the value in the key-value pair belongs;

The second ORM framework is used to delete all key-value pairs stored in the cache module in association with the object identifier in the operation request when the operation type in the operation request is an update type.
A database access method, characterized in that it is applied to a relational object mapping (ORM) execution engine, the ORM execution engine includes a second ORM framework, the ORM execution engine is communicatively connected to an application system, the ORM execution engine is communicatively connected to a database, the application system includes a first ORM framework, and the method includes:

The second ORM framework obtains an operation request sent by the first ORM framework, where the operation request is generated by the first ORM framework according to a business statement, and is used to request an operation to be performed on the data in the database;

The second ORM framework parses the operation request to obtain a structured query language SQL statement;

The second ORM framework executes the SQL statement to access the data in the database and obtains the execution result of the SQL statement.
The method according to claim 11, characterized in that the ORM execution engine further comprises a middleware module, and the middleware module is in communication connection with the application system;

The second ORM framework obtains the operation request sent by the first ORM framework, including:

The middleware module receives the operation request sent by the first ORM framework, and sends the operation request to the second ORM framework when a database access condition is met.
The method according to claim 12, characterized in that the operation request carries an object identifier and an operation type, and the object identifier is used to identify the object to be accessed by the operation request;

The database access condition includes at least one of the following:

The number of accesses to the database is less than a first number threshold;

The access count of the object to be accessed by the operation request is less than the second count threshold;

The application system has access rights to the object to be accessed by the operation request;

The application system has access rights to the database;

The operation type in the operation request is an operation type that the database allows to be performed on the object to be accessed by the operation request.
A computer device, characterized in that the computer device comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the method according to any one of claims 11 to 13 when executed by the processor.
A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the method according to any one of claims 11 to 13.