JDBC and JDBC Driver Connectivity

The JDBC or Java database connectivity is a unique technology that empowers applications to be written once but run anywhere. JDBC enabled devise driver could access corporate data even if the environment is not homogeneous. This unique feature is very much Java specific for Java itself is platform independent and Java API which is actually a short term of JDBC enables the easy execution of SQL statements.

JDBC is an application program to the core used to access database in tubular format encrypted by Java and driven by standard interfaces. RDBMS like SQL and Oracle are quarried and updated by JDBC with its niche in using and allowing heterogeneous implementation with the same application.

Since SQL is supported by all Relational Database Management System any corporate database could be accessed, quarried or updated via this single Java written JDBC program. In order to interact with database Java interface is used by programmers but it is the job of a JDBC driver to implement the interface according to the data base management system. Though Java Database Connectivity Driver categorically implements connection some are better suited for specific applications over the other types.

Four types of JDBC driver connectivity are common with Type 1 driver heading the list. It’s a popular, platform independent driver that uses ODBC to connect to database. Type 2 Native API driver is not coded by Java in its entirety making it more versatile in interpreting client libraries of database into recognizable native calls.

Application server, namely middle tier technology is used by Type 3 drivers and therefore client software is not required and database access could be gained through internet.

A type 4 driver also known as Native Protocol Driver and is a complete Java written program, which displays superior performance over the other two types and is completely platform independent. Communication with client application is speedy and easy as direct conversion of JDBC into vendor database protocol is enabled excluding middleware function; however a separate client side driver is required for a different database which poses the only challenge at times.