Oracle Unified Access Agent tier scenario

Goal

The

provides a oracle database unification Access agent layer, Unified management of connection pooling for all Oracle database user names, allowing multiple application systems to have the same database user common connection pool to save oracle The total number of connections to the server, and provides unified management of Oracle capabilities.   Maintained backend oracle connection pool for different users, applied through jdbc sql . Achieve the same user name connection multiplexing effect. For example, user2&sql incoming access layer, access layer engine Navigate to the first oracle user2 username connection pool, and take out a connection execution.

Function

Routing: Provides navigation to the appropriate database connection pool through the database user name.

SQL statement pass through: that is, do not change the application of incoming SQL , through a simple user name to navigate to the corresponding oracle execution, the execution results back to the application side.

Supports multiple Oracle Libraries: You can proxy multiple Oracle databases at the same time , and all connection pools that access the database are managed by the agent layer.

Basic function of construction program

The overall scenario is to embed a jar package (mysql driver package) into the application, which is like using JDBC to operate the database normally.

With the LVS load Balancer, the receiver uses the MySQL protocol to communicate with the application, and the front end uses the NIO Network mode to receive the request.

The backend uses the Oracle JDBC driver to connect to several databases, and uses the BIO network mode to provide good horizontal scaling capabilities, Production can be very convenient by increasing the machine link to make the processing capacity near linear growth.

The core module is SQL Engine, which provides the application of incoming SQL database connection pool Routing and database execution operations.

In addition, it realizes the functions of thread management, heartbeat management, session management, user authentication,Hint function module and so on.

Supporting functions

Functional test: Provides the script tool to run the function test automatically.

Performance test: Provides the script tool to run the performance test automatically.

Key parameter monitoring: Provide a background to observe the agent layer front-end network reception, and the various states of the backend database connection pool.

Configuration release: currently only manual modification of configuration files and manual publishing are available.

Technology stack

L Front-end NIO mode:

The front-end uses non-blocking network mode to receive messages, improve the system's receiving and processing ability, and improve the system's multi-concurrency capability.

L Back-end BIO mode:

The backend uses blocking network mode to interact with the database, because connection pooling connections are generally limited in number, and Oracle The database will also have a connection limit, so here BIO The mode is suitable, the operation of the connection is easy to maintain and easy to use BIO patterns do not affect the performance of backend interactions with databases, while providing friendly support for system-level scaling.

L Reactor Mode

Adopt Reactor Mode to Network IO optimization of performance.

L dom4j Components

This component is primarily used to XML the parsing of the file works.

L Oracledriver Drive

as a Oracle database Connection driver.

L Tomcat JDBC Connection pool:

Use Tomcat JDBC connection pool to back end Oracle connection for Management, Tomcat team on the original DBCP When the connection pool is optimized, it is a relatively mature component with a reliable connection management capability and is TOMCAT7 later the default database connection management component, which belongs to Apache under open source projects.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Oracle Unified Access Agent tier scenario