Different Types Of Jdbc Driver

By Author: individual
Total Articles: 6
Comment this article

What is a driver and JDBC Driver Types?
There are two different software components called Java and database (Oracle). For the development of software, Java programming language is used and Oracle is a database used for storing the data. The companies which developed both of them are not the same and this is where the driver called JDBC comes into the picture.
Here are 4 types of JDBC drivers in Java:
Type1: JDBC-ODBC Bridge, Plus ODBC Driver
With the help of JDBCODBCDriver class from sun.jdbc.odbc package this first type of bridge driver is supported. For connecting to a database this driver bridge connects with another driver called ODBC driver. Database client code and ODBC driver must be installed on every client in an office and this is the main disadvantage of using this driver. At the time the systems are spread apart this will be very difficult whereas it will be safe when the systems are confined to a small area. Thus it is considered poorest among the JDBC drivers.
Type 2: Native-API Driver, partly-Java driver
The JDBC commands are converted into DBMS-specific native calls by the ...
... native-API driver. The Type 1 drivers restriction is also followed over here. On the machine, the client must have binary code loaded. The only advantage they have over type 1 drivers is that they interface directly with the database.
Type 3: JDBC- Net, pure Java Driver
This is considered as a three-tier solution. JDBC calls are translated by this type of driver into an independent database network protocol that is sent to a middleware server. The DBMS specific protocol is then translated by this server which is forwarded to a particular database. The middleware server is used for routing back the results and then it is sent back to the client. Without affecting the client it also helps in swapping the databases. The most flexible JDBC solution is only this option.
Type 4: Native Protocol, pure Java Driver
This one is most preferred in the real times especially for its performance. The reason behind the performance efficiency is because of its direct conversion of JDBC queries into database-specific network protocol and extra transformation of middle layers is used for elimination. Database dependency of native protocol driver is generally provided by the database vendors itself. Java language is used to write and program this entire driver and is called as a thin driver.