View RSS Feed

JDBC

Type 3: Net-protocol/all-Java driver

Rate this Entry
by , 04-27-2012 at 07:00 PM (1354 Views)
JDBC driver type 3 -- the net-protocol/all-Java driver -- follows a three-tiered approach whereby the JDBC database requests are passed through the network to the middle-tier server. The middle-tier server then translates the request (directly or indirectly) to the database-specific native-connectivity interface to further the request to the database server. If the middle-tier server is written in Java, it can use a type 1 or type 2 JDBC driver to do this.

Pros
The net-protocol/all-Java driver is server-based, so there is no need for any vendor database library to be present on client machines. Further, there are many opportunities to optimize portability, performance, and scalability. Moreover, the net protocol can be designed to make the client JDBC driver very small and fast to load. Additionally, a type 3 driver typically provides support for features such as caching (connections, query results, and so on), load balancing, and advanced system administration such as logging and auditing.

Cons
Type 3 drivers require database-specific coding to be done in the middle tier. Additionally, traversing the recordset may take longer, since the data comes through the backend server.

Submit "Type 3: Net-protocol/all-Java driver" to Facebook Submit "Type 3: Net-protocol/all-Java driver" to Digg Submit "Type 3: Net-protocol/all-Java driver" to del.icio.us Submit "Type 3: Net-protocol/all-Java driver" to StumbleUpon Submit "Type 3: Net-protocol/all-Java driver" to Google

Categories
Driver

Comments