WO2016206405A1

WO2016206405A1 - Database accessing method and device

Info

Publication number: WO2016206405A1
Application number: PCT/CN2016/075801
Authority: WO
Inventors: 杨兆辉
Original assignee: 中兴通讯股份有限公司
Priority date: 2015-06-26
Filing date: 2016-03-07
Publication date: 2016-12-29
Also published as: CN106326256A

Abstract

Disclosed is a database accessing method, comprising: receiving an access request transmitted by an application program and for a target database in a database system; selecting, from access interfaces corresponding to various databases and preset in an interface layer, an access interface corresponding to the target database; and invoking, according to the access request, the selected access interface to access the target database. Also disclosed is a database accessing device. The method and the device simplify access of an application program, and ensure stability and integrality of a database system when being upgraded.

Description

Database access method and device

Technical field

The present application relates to the field of data processing technologies, for example, to a database access method and apparatus.

Background technique

In the fields of communication, Internet, computer, etc., with the increasing amount of data processed, big data databases have been widely used. From Oracle, SybaseIQ to Hive, Spark, more and more databases are being applied in the database system, becoming a very important part of the database system, providing storage, query, analysis and other access methods for various types of data.

When the database system needs to be upgraded, for example, to access a new database in the database system, or to replace the original database, ensuring the integrity and stability of the database system is a major challenge to the upgrade operation. In order to make the database system compatible with different kinds of databases, the current practice is to add a new interface to the database system when the database system is added to the database system, or to replace the interface with the new database. The database-adaptive interface is modified into an interface that is adapted to the replaced database, thereby completing the upgrade of the database system. Inevitably, large-scale changes will be made to the database system, thereby destroying the integrity of the original system and laying a hidden danger for the stability of the system.

For example, as shown in Figure 1, the database system originally only includes the database Sybase IQ, and the CPP (C++) application accesses Sybase IQ through the ODBC (Open Database Connectivity) interface. Sybase IQ is a centralized storage columnar database. As the amount of data increases, centralized storage cannot meet the storage requirements of massive data, and a large data database Hive needs to be accessed in the database system. However, accessing Hive using the ODBC interface is not stable, and accessing Hive using the JDBC (Java Data Base Connectivity) interface is relatively stable. Therefore, when the CPP application accesses the JDBC interface, it needs to add a CPP to call the transfer interface of the Java program. The CPP application needs to access both the ODBC interface and the CPP to JDBC interface. The calling methods of the two interfaces are inconsistent. Therefore, the CPP application needs to pay attention to some technical details of the interface layer, which makes the application layer access more and more complicated.

Summary of the invention

In view of the above, a database access method and device are provided, which can access each database in the database system independently of the interface layer of the database system, and shield the application from different accesses to different types of databases. When the database system is upgraded, the system can be guaranteed. Stability and integrity, and the application does not need to be aware, making application access simple.

A database access method includes: receiving an access request sent by an application to a target database in a database system; and selecting an access interface corresponding to the target database from an access interface corresponding to each type of database preset in the interface layer; The access request is invoked, and the selected access interface is invoked to perform an access operation on the target database.

A database accessing device, comprising: a receiving module configured to receive an access request sent by an application to a target database in a database system; and a selecting module configured to be in an access interface corresponding to each type of database preset in the interface layer Selecting an access interface corresponding to the target database; the access module is configured to invoke the selected access interface to perform an access operation on the target database according to the access request.

The beneficial effects of the foregoing technical solution are: the database access method and device, when receiving an access request sent by the application to the target database in the database system, selecting the target from the access interfaces corresponding to the various types of databases preset in the interface layer An access interface corresponding to the database, and then invoking the selected access interface to perform an access operation on the target database according to the access request, so that each database in the database system can be accessed through an interface layer independent of the database system, and the application is shielded from different types of databases. The difference in access, when the database system is upgraded, can ensure the stability and integrity of the system, and the application does not need to be aware, thus simplifying the access of the application and reducing the workload of application development.

BRIEF abstract

FIG. 1 is a diagram showing an example of accessing a database after a database system is upgraded in the related art;

2 is a flowchart of a database access method according to a first embodiment of the present invention;

FIG. 3 is a diagram showing an application example of a database access method according to a first embodiment of the present invention; FIG.

4 is a flowchart of a database access method according to a third embodiment of the present invention;

FIG. 5 is a diagram showing an application example of a database access method according to a third embodiment of the present invention; FIG.

FIG. 6 is a block diagram of a database access apparatus according to a fourth embodiment of the present invention.

Embodiments of the invention

In order to explain the technical solutions and technical effects of the present invention, the embodiments, structures, features and technical effects according to the present invention will be described in detail below with reference to the accompanying drawings and embodiments.

First embodiment

Referring to FIG. 2, it is a flowchart of a database access method according to a first embodiment of the present invention. In this embodiment, the method includes:

S1, receiving an access request sent by the application to the target database in the database system;

S2, selecting an access interface corresponding to the target database from an access interface corresponding to each type of database preset in the interface layer;

S3. In response to the access request, invoke the selected access interface to perform an access operation on the target database.

According to the database access method described above, each database in the database system can be accessed through an interface layer independent of the database system, and the application layer can be shielded from different types of databases. When the database system is upgraded, the stability and integrity of the system can be ensured. And the application doesn't need to be aware, which simplifies application access and reduces the amount of application development effort.

In some instances, the implementation details of the above method are as follows:

The application described in S1 is, for example, a CPP program, a Java application, or the like. The app is one of the applications in the application layer. One or more applications included in the application layer can access each of the same kind or different kinds of databases in the database system through the interface layer. The architecture of the application layer, interface layer and database system is shown in Figure 3.

The interface layer is set independently of the database system. The interface layer is pre-configured with access interfaces corresponding to various types of databases. The access interfaces corresponding to the various types of databases are preset and optimized according to the access characteristics of various databases, and can be flexibly updated according to requirements, for example, adding a certain type of database correspondingly. Access interface, or modify the access interface corresponding to a certain type of database. In some examples, as shown in FIG. 3, the database system may include five types of databases: Hive, Impala, Spark SQL, Oracle, and Sybase IQ. According to the access characteristics of the five types of databases, the corresponding access interfaces may be preset as follows: :

The default Hive access interface is Hive JDBC.

The default Impala access interface is Impala JDBC;

The default access interface of Spark SQL is Hive Context;

The default Oracle access interface is Oracle ODBC; and

The default Sybase IQ access interface is Sybase IQ ODBC.

The access request described in S1 may be, for example, a request for querying, saving, or analyzing data in the target database. The access request may be sent to the interface layer when one or more programs in the application layer need to query or analyze data in the target database, or when data needs to be saved to the target database.

In S2, according to the access request, the target database to be accessed is obtained, so that the preset access interface corresponding to the target database is found out from the interface layer. The identifier of the target database, such as an ID number, may be obtained according to the access request, and the identifier is compared with the identifier of each database in the database system to find the target database.

In S3, according to the access request, the selected access interface is invoked to perform an access operation on the target database. In addition, the selected access interface may be invoked in S3 to obtain an access result to the target database, and the access result is sent to the application. For example, if the access request saves the data to the target database for the request, the selected access interface is called to save the database to the target database, and the access result may be information that the data is saved successfully. If the access request is to query the data in the target database, the selected access interface is invoked to query the data in the target database, and the data obtained by the query is used as the access result, and then the access result is obtained through the selected access interface. And send the result of the visit to the application. If the access request is to request analysis of data in the target database, the selected access interface is called to analyze the data in the target database, and the analysis result is used as an access result, and then the access result is obtained through the selected access interface, and The result of the visit is sent to the application, and so on.

In summary, the database access method provided by the embodiment of the present invention, the application layer and the database system interact indirectly through the interface layer independent of the database system, and can block the access difference of the application layer to different types of databases. When the database system is upgraded, for example, replacing Hive in Figure 3 with Impala, Spark SQL, or replacing Sybase IQ with Oracle, the application layer code does not need to be modified, so the application layer does not need to be aware, which not only makes the application layer access simple. It also ensures the stability and integrity of the system.

Second embodiment

The second embodiment of the present invention provides a database access method, which is compared with the database access method provided by the first embodiment.

The access request sent by the receiving application to the target database in the database system in S1 can be implemented by a data exchange protocol independent of the programming language. The programming language-independent data exchange protocol may be a Simple Object Access Protocol (SOAP) based on the HyperText Transfer Protocol (HTTP). Similarly, the access result sent to the application through the selected access interface can also be implemented by the programming language independent data exchange protocol.

Since the application layer and the general interface layer implement interaction through the programming language-independent data exchange protocol, such as SOAP, the application layer application can be an application developed for any mainstream programming language, in accordance with an agreed-upon programming language. SOAP accesses the database system, thus traversing the firewall across programming languages.

Third embodiment

Referring to FIG. 4, it is a flowchart of a database access method according to a third embodiment of the present invention. In this embodiment, the database access methods described in the first embodiment and the second embodiment are applied to an application scenario in which a big data database (for example, Hive) is integrated with a legacy database (for example, Sybase IQ). The application in the application layer can send a data analysis request to the Hive through the interface layer. After receiving the data analysis request, the Hive returns the analysis result to the application layer. After receiving the analysis result, the application sends a data save request to Sybase IQ through the interface layer. After receiving the data save request, Sybase IQ saves the analysis result. In addition, if the application has the same data analysis request, you can directly access Sybase IQ and obtain the analysis result from Sybase IQ. An example of the application layer, interface layer, and Hive and Sybase IQ architecture is shown in Figure 5.

The database access method provided in this embodiment may include:

S11, receiving, by the SOAP, the data analysis request sent by the application to the Hive in the database system; at this time, the application functions as a SOAP client, and the interface layer functions as a SOAP server;

S12: Select a Hive JDBC interface corresponding to the Hive from the access interfaces corresponding to the various types of databases preset in the interface layer.

S13. Perform data analysis on the Hive through the Hive JDBC interface according to the data analysis request. The analysis result is obtained through the Hive JDBC interface, and the analysis result is returned to the application;

S14, the data saving request sent by the SOAP receiving application to save the analysis result to Sybase IQ in the database system;

S15, selecting a Sybase IQ ODBC interface corresponding to Sybase IQ from an access interface corresponding to each type of database preset in the interface layer;

S16, according to the data save request, save the analysis result to Sybase IQ through the Sybase IQ ODBC interface, and then persist the analysis result to Sybase IQ.

In this embodiment, the Hive and Sybase IQ databases are integrated in the database system. The access interfaces of the two databases are different, namely the Hive JDBC interface and the Sybase IQ ODBC interface. However, by presetting the Hive JDBC interface and the Sybase IQ ODBC interface to a separate interface layer, the application can extract data from Hive and store it in Sybase IQ. The indirect interaction between the application and the database system through the interface layer can shield the application layer from different types of database access differences. For the application layer, a common database access channel is used.

Fourth embodiment

Referring to FIG. 6, a fourth embodiment of the present invention provides a database access apparatus 100, which includes a receiving module 101, a selecting module 102, and an access module 103. The database access device 100 can be embedded or peripheral to the interface layer. It will be understood that each of the above modules may refer to a computer program or program segment configured to perform one or more specific functions. Moreover, the distinction between the above modules does not mean that the actual program code is also separate.

The receiving module 101 is configured to receive an access request sent by the application to the target database in the database system. The receiving module 101 can implement an access request sent by the application to the target database in the database system through a data exchange protocol independent of the programming language. The programming language independent data exchange protocol may be a Simple Object Access Protocol (SOAP).

The selecting module 102 is configured to select an access interface corresponding to the target database from the access interfaces corresponding to the various types of databases preset in the interface layer.

The access module 103 is configured to invoke the selected access interface to perform an access operation on the target database according to the access request. The access module 103 can also send the access result to the application via the selected access interface.

For details of implementation of the above modules, reference may be made to the databases provided by the first embodiment and the second embodiment of the present invention. The description in the access method is not described here.

The database access device 100 provided in this embodiment can access the databases in the database system independently of the interface layer of the database system, and shield the application from different accesses to different types of databases. When the database system is upgraded, the stability of the system can be ensured. Integrity, and the application layer does not need to be aware, thus simplifying access at the application layer. In addition, since the application layer and the general interface layer pass the programming language-independent data exchange protocol, the application layer application can be an application developed for any mainstream programming language, and accesses the database according to an agreed protocol in any programming language. The system thus spans the programming language and traverses the firewall.

In addition, an embodiment of the present invention further provides a computer readable storage medium having stored therein computer executable instructions, such as a non-volatile memory such as an optical disk, a hard disk, or a flash memory. The above computer executable instructions may cause a computer or similar computing device to perform various operations in the database access method described above.

The above is only an embodiment of the present invention, and is not intended to limit the scope of the present invention. The present invention has been disclosed by the embodiments, but is not intended to limit the present invention, and any person skilled in the art In the scope of the technical solutions of the present invention, the equivalents of the embodiments of the present invention may be made without departing from the technical scope of the present invention. Any of the brief modifications, equivalent changes and modifications made by the above embodiments are still within the scope of the technical solutions of the present invention.

Industrial applicability

The present application discloses a database access method, which includes: receiving an access request sent by an application to a target database in a database system; and selecting an access interface corresponding to the target database from an access interface corresponding to each type of database preset in the interface layer. And invoking the selected access interface to perform an access operation on the target database according to the access request. The application also discloses a database access device. The method and apparatus can simplify application access and ensure stability and integrity of the database system upgrade.

Claims

A database access method, including:

Receiving an access request sent by the application to the target database in the database system;

Selecting an access interface corresponding to the target database from the access interfaces corresponding to the various types of databases preset in the interface layer;

According to the access request, the selected access interface is invoked to perform an access operation on the target database.
The method of claim 1 wherein said receiving application sends an access request to a target database in a database system via a data exchange protocol independent of a programming language.
The method of claim 2 wherein said programming language independent data exchange protocol is a simple object access protocol.
The method of claim 1 further comprising:

The selected access interface is invoked to obtain an access result to the target database, and the access result is sent to the application.
The method of claim 4 wherein said accessing results are sent to the application via the selected access interface by a data exchange protocol independent of the programming language.
A database access device comprising:

a receiving module configured to receive an access request sent by an application to a target database in a database system;

The selection module is configured to select an access interface corresponding to the target database from the access interfaces corresponding to the various types of databases preset in the interface layer;

The access module is configured to invoke the selected access interface to perform an access operation on the target database according to the access request.
The apparatus of claim 6, wherein the receiving module is configured to pass and program The language-independent data exchange protocol receives an access request from the application to the target database in the database system.
The apparatus of claim 7, wherein the programming language independent data exchange protocol is a simple object access protocol.
The apparatus of claim 6 wherein said access module is further configured to:

The selected access interface is invoked to obtain an access result to the target database, and the access result is sent to the application.
The apparatus of claim 9 wherein said access module is further configured to:

The access result is sent to the application via the selected access interface via a data exchange protocol independent of the programming language.