CN104166699A - Data access method based on REST framework - Google Patents

Abstract

The invention relates to the field of computer application technology, in particular to a data access method based on the REST architecture. The present invention uses the RESTful JDBC protocol to interact with data sources, and each data source is connected to the cloud database through the RESTful JDBC protocol; the RESTful JDBC protocol encapsulates the traditional JDBC interface into a RESTful JDBC interface; the interface provided by the RESTful JDBC and The JDBC interface is basically the same, and the semantics of the interface are also consistent with JDBC. The invention provides an interaction mode based on the REST architecture between the data source and the cloud database; it can be used for the interaction between the cloud database and the heterogeneous data source.

Description

A Data Access Method Based on REST Architecture

technical field

The invention relates to the field of computer application technology, in particular to a data access method based on the REST architecture.

Background technique

In the process of enterprise informatization construction, due to the phased, technical, and other economic and human factors in the construction of various business systems and the implementation of data management systems, enterprises have accumulated a large amount of business data in different storage methods during the development process. The data management systems used for these data are quite different, ranging from simple file databases to complex network databases, which constitute the heterogeneous data sources of enterprises. Although these scattered data management systems of different businesses can meet the requirements of business data storage and management, in many cases, to make a decision, business leaders often need to query multiple business systems based on various heterogeneous data sources and The external system can only make decisions after analyzing a large amount of data.

Therefore, the integration and integration of heterogeneous data sources is a practical problem often encountered in the process of enterprise informatization construction, and it is also an important factor that restricts the construction of various application information systems and data sharing in enterprises, as well as the repeated investment or heavy burden of informatization construction. factor.

Cloud database system is an important method for the integration and integration of heterogeneous data sources. However, how to realize the interaction between cloud database and heterogeneous data sources is very important.

Contents of the invention

The technical problem solved by the present invention is to provide a data access method based on the REST architecture, which can effectively solve the problem of interaction between cloud databases and heterogeneous data sources.

The technical scheme that the present invention solves the problems of the technologies described above is:

The RESTful JDBC protocol is used to interact with data sources, and each data source is connected to the cloud database through the RESTful JDBC protocol; the RESTful JDBC protocol encapsulates the traditional JDBC interface into a RESTful JDBC interface; the interface provided by RESTful JDBC and the JDBC interface Basically the same, the semantics of the interface are also consistent with JDBC.

The RESTful JDBC protocol has a key implementation component DS The DS It is the agent between Wrapper and database, and Wrapper passes DS Interact with the database; for Wrapper, DS Is a server, for the database, DS is a client; Wrapper and DS Using RESTful JDBC protocol, DS The JDBC protocol is adopted with the database.

The way to implement Wrapper to support RESTful JDBC protocol is:

Add a layer of protocol manager under the Wrapper for the selection and switching of the two protocols;

or,

Add a RESTful JDBC version to Wrapper.

The DS Support two deployment modes: dedicated mode and shared mode;

In the exclusive mode mentioned above, one database exclusively occupies one DS At this point, a database and a DS constitute a data source;

In the sharing mode mentioned above, multiple databases share one DS At this time, multiple databases and one DS constitute a data source.

The DS Use Jetty as the REST engine, and use Jetty to publish RESTful JDBC; support the management of database addresses and access credentials, the management of data source addresses and access credentials, the accurate mapping of data source addresses and database addresses, and the access credentials of data sources and databases Accurate mapping of access credentials; support thread pool, database connection pool operations; the aforementioned support functions are implemented by DS2DB Manager.

The method of the present invention effectively solves the problem of interaction between cloud databases and heterogeneous data sources; supports multiple database systems (MySQL, Oracle, SQL Server, DB2) and file systems (Excel files, KV files).

Description of drawings

Below in conjunction with accompanying drawing, the present invention is further described:

Fig. 1 is a logical architecture diagram of the present invention;

Fig. 2 is a deployment mode diagram of the present invention;

Fig. 3 is a system realization diagram of the present invention.

Detailed ways

The RESTfulization of the data source is essentially the RESTfulization of the data source access protocol, providing a RESTful access interface for the data source.

At present, commonly used data sources are various relational databases, which provide JDBC access interfaces, and the interaction with data sources uses the JDBC protocol. After REST, we will use the "RESTful JDBC protocol" to interact with data sources, and each data source is connected to the cloud database through the RESTful JDBC protocol.

As shown in the figure, the RESTful JDBC protocol encapsulates the traditional JDBC interface into a REST API, namely "RESTful JDBC interface". The interface provided by RESTfulJDBC is basically the same as the JDBC interface, and the semantics of the interface are also consistent with JDBC. For example, the query interface is provided in JDBC:

ResultSet executeQuery(String sql)

Then there should be the same interface in RESTful JDBC, with the same semantics. However, there are too many interface data provided in traditional JDBC, and these interfaces do not need to be implemented one by one in the RESTful JDBC protocol, only some core interfaces need to be implemented.

DS It is a key component to implement the RESTful JDBC protocol. DS It is the agent between Wrapper and database, and Wrapper passes DS Interact with the database. For Wrapper, DS Is a server, for the database, DS is a client. Wrapper and DS Using RESTful JDBC protocol, DS The JDBC protocol is adopted with the database.

With the RESTful JDBC protocol, each data source supports two ways to interact with the cloud database. The existing Wrapper in the system only supports the JDBC protocol, which cannot meet the requirements. There are two options to solve this problem:

1. Add a layer of protocol manager under the Wrapper for the selection and switching of the two protocols. At present, the implementation of Wrapper in the system is tightly coupled with the JDBC protocol. This solution may cause relatively large modifications to the implementation of the existing Wrapper.

2. Add a RESTful JDBC version to the Wrapper. For example, for Oracle Wrapper, two versions are provided: JDBC version and RESTful JDBC version. The JDBC version interacts with the Oracle database through the JDBC protocol, and the RESTful JDBC version interacts with the Oracle database through the RESTful JDBC protocol. This solution will double the number of existing Wrappers in the system, and the advantage is that there is no need to modify the implementation of the existing Wrappers.

Based on the "Open and Close Design Principles" and comprehensively considering the development cost, the second solution is adopted to add a RESTful JDBC version to the Wrapper.

DS Two deployment modes are supported:

1. Proprietary mode: one database exclusively occupies one DS At this point, a database and a DS constitute a data source. The benefit of this model is that DS It will not become a performance bottleneck, but the disadvantage is that there may be a large number of DSs in the system Instances increase deployment and management costs.

2. Sharing mode: Multiple databases share one DS At this time, multiple databases and one DS constitute a data source. The advantage of this mode is that the DS in the system There are relatively few instances, and the disadvantage is that DS May become a performance bottleneck for access;

Which deployment mode to use in practice needs to be considered comprehensively according to the requirements of the application and the constraints of the deployment environment.

DS It is the core component to implement the data access protocol, and the DS is given in detail below specific implementation.

1. The implementation of Jetty is an open-source, standards-based, and rich-featured Http server and Web container implemented in Java. DS The implementation uses Jetty as the REST engine, and uses Jetty to publish RESTful JDBC.

2. Support the management of database addresses and access credentials, for example:

a) Database address: jdbc:oracle:thin:192.168.1.100:1521:orcl;

b) Database access credentials: user name and password for accessing the Oracle database;

The database address and access credentials are configured by the database users themselves, and the database address and access credentials are invisible to the cloud database. Database access credentials need to be stored encrypted to prevent multiple databases from sharing a DS In the mode, the user name and password of the database are leaked;

3. Support the management of data source addresses and access credentials,

a) Data source address: rest:oracle192.168.1.100:8080/orcl;

b) Access credentials of the data source: the user name and password for accessing the data source through the RESTful JDBC protocol are different from the user and password for accessing the database;

The address and access credentials of the data source are configured by the database user, and the address and access credentials of the data source are invisible to the cloud database. The access credentials of the data source need to be encrypted and stored to prevent multiple databases from sharing a DS In the case of the mode, the user name and password of the data source are leaked;

4. Support accurate mapping of data source address and database address, support accurate mapping of data source access credentials and database access credentials;

5. Support the operation of thread pool and database connection pool to prevent DS Become a performance bottleneck; DS2DB Manager is mainly responsible for realizing the above 2, 3, and 4 functions.

Claims (6)

1. A data access method based on the REST architecture, characterized in that: the RESTful JDBC protocol is used to interact with the data source, and each data source is connected to the cloud database through the RESTful JDBC protocol; the RESTful JDBC protocol combines the traditional The JDBC interface is encapsulated into a RESTful JDBC interface; the interface provided by RESTful JDBC is basically the same as the JDBC interface, and the semantics of the interface are also consistent with JDBC. 2. The data access method according to claim 1, characterized in that: the RESTful JDBC protocol has a key component DS for realization The DS It is the agent between Wrapper and database, and Wrapper passes DS Interact with the database; for Wrapper, DS Is a server, for the database, DS is a client; Wrapper and DS Using RESTful JDBC protocol, DS The JDBC protocol is adopted with the database. 3. The data access method according to claim 2, characterized in that: the method for realizing Wrapper to support the RESTful JDBC protocol is: Add a layer of protocol manager under the Wrapper for the selection and switching of the two protocols; or, Add a RESTful JDBC version to Wrapper. 4. The data access method according to claim 2, characterized in that: the DS Support two deployment modes: dedicated mode and shared mode; In the exclusive mode mentioned above, one database exclusively occupies one DS At this point, a database and a DS constitute a data source; In the sharing mode mentioned above, multiple databases share one DS At this time, multiple databases and one DS constitute a data source. 5. The data access method according to claim 3, characterized in that: the DS Support two deployment modes: dedicated mode and shared mode; In the exclusive mode mentioned above, one database exclusively occupies one DS At this point, a database and a DS constitute a data source; In the sharing mode mentioned above, multiple databases share one DS At this time, multiple databases and one DS constitute a data source. 6. The data access method according to any one of claims 2 to 5, characterized in that: the DS Use Jetty as the REST engine, and use Jetty to publish RESTful JDBC; support the management of database addresses and access credentials, the management of data source addresses and access credentials, the accurate mapping of data source addresses and database addresses, and the access credentials of data sources and databases Accurate mapping of access credentials; support thread pool, database connection pool operations; the aforementioned support functions are implemented by DS2DB Manager.