There are 4 different JDBC drivers out there in the market.
Type I: JDBC – ODBC Bridge
Type II: Native API – Half Java Driver
Type III: Network Protocol– Totally Java Driver
Type IV: Thin Driver- Totally Java Driver
Type I: JDBC-ODBC Bridge
JDBC-ODBC bridge is going to behave as an interface between the client and the DB server. The client should put the JDBC-ODBC driver in it. The database ought to support the ODBC driver. If we are not concerned about the driver installation within the client system, we will use this driver.
Type II: Native API: Half Java Driver
It is almost like a JDBC-ODBC driver. Rather than an ODBC driver, we are using native API here. Libraries of the client-side database are used.
Type III: Network Protocol
It works like a 3-tier approach to access the database. An intermediate server will be used to connect to DB. JDBC method calls send data to an intermediate server then the server will communicate with DB.
Type IV: Thin Driver
It is absolutely written in Java. It explicitly converts JDBC method calls into the vendor-specific database protocol. Nowadays, Database merchant itself is providing this type of driver for their customers. So programmers don’t rely on other sources. It gives higher performance than the other drivers.
Posted Date:- 2021-09-03 21:27:26