Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
86 views

Java DataBase Connectivity

JDBC is a Java API that allows Java programs to execute SQL statements. There are four types of JDBC drivers: 1) Bridge drivers that use ODBC, 2) Native drivers that use native database APIs, 3) Middleware drivers that communicate through a middle tier server, and 4) Pure Java drivers that communicate directly using Java networking libraries. Pure Java drivers are fully written in Java, platform independent, and most suitable for web applications, while bridge and native drivers require additional software but can provide better performance.

Uploaded by

api-3866644
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
86 views

Java DataBase Connectivity

JDBC is a Java API that allows Java programs to execute SQL statements. There are four types of JDBC drivers: 1) Bridge drivers that use ODBC, 2) Native drivers that use native database APIs, 3) Middleware drivers that communicate through a middle tier server, and 4) Pure Java drivers that communicate directly using Java networking libraries. Pure Java drivers are fully written in Java, platform independent, and most suitable for web applications, while bridge and native drivers require additional software but can provide better performance.

Uploaded by

api-3866644
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 24

Java DataBase

Connectivity
(JDBC)
What is JDBC?
 JDBC is a Java API for executing SQL
statements.
 It consists of a set of classes and
interfaces written in the Java
programming language.
 JDBC provides a standard API for
tool/database developers and makes
it possible to write database
applications using a pure Java API.
what are JDBC Driver?
 JDBC Drivers are set of classes that
enables the Java application to
communicate with databases.
 Java.sql that ships with JDK contains
various classes for using relational
databases. But these classes do not
provide any implementation, only the
behaviours are defined.
 The actual implementaions are done in
third-party drivers. Third party vendors
implements the java.sql.Driver interface in
their database driver.
Types of JDBC Drivers
There are four types of JDBC drivers:

Type 1: JDBC-ODBC Bridge driver (Bridge)


Type 2: Native-API/partly Java driver
(Native)
Type 3: AllJava/Net-protocol driver
(Middleware)
Type 4: All Java/Native-protocol driver
(Pure)
Type 1: JDBC-ODBC Bridge driver
(Bridge)
This driver is automatically installed
when J2SDK is installed on the
machine.
The Type 1 driver translates all JDBC calls
into ODBC calls and sends them to the
ODBC driver. ODBC is a generic API. The
JDBC-ODBC Bridge driver is recommended
only for experimental use or when no
other alternative is available.
Type 1:JDBC-ODBC Bridge
Advantages
 TheJDBC-ODBC Bridge allows access to
almost any database, since the database's
ODBC drivers are already available
Disadvantages
 Since the Bridge driver is not written fully
in Java, Type 1 drivers are not portable.
 A performance issue is seen as a JDBC call
goes through the bridge to the ODBC
driver, then to the database, and this
applies even in the reverse process. They
are the slowest of all driver types.
 The client system requires the ODBC
Installation to use the driver.
 Not good for the Web as it is limited
running locally.
Type 2: Native-API/partly Java driver
(Native)
The distinctive characteristic of type 2 jdbc
drivers are that Type 2 drivers convert
JDBC calls into database-specific calls i.e.
this driver is specific to a particular
database. Some distinctive characteristic
of type 2 jdbc drivers are shown below.
Example: Oracle will have oracle native
api.
Type 2: Native api/ Partly
Java Driver
Advantages
 The distinctive characteristic of type 2 jdbc
drivers are that they are typically offer
better performance than the JDBC-ODBC
Bridge as the layers of communication
(tiers) are less than that of Type
1 and also it uses Native api which is
Database specific
Disadvantages

 Native API must be installed in the Client


System and hence type 2 drivers cannot
be used for the Internet.
 Like Type 1 drivers, it’s not written in Java
Language which forms a portability issue.
 If we change the Database we have to
change the native api as it is specific to a
database
 Usually not thread safe.
 Generally can’t run inside an applet
because of Native Method calls
Type 3: AllJava/Net-protocol driver
(Middleware)
Type 3 database requests are passed
through the network to the middle-tier
server. The middle-tier then translates the
request to the database. If the middle-tier
server can in turn use Type1, Type 2 or
Type 4 drivers.
Type 3: All Java/ Net-Protocol
Driver
Advantages
 This driver is server-based, so there is no
need for any vendor database library to be
present on client machines.
 This driver is fully written in Java and
hence Portable. It is suitable for the web.
 There are many opportunities to optimize
portability, performance, and scalability.
 The net protocol can be designed to make
the client JDBC driver very small and fast
to load.
 The 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.
 This driver is very flexible allows
access to multiple databases using
one driver.
 They are the most efficient amongst
all driver types.
Disadvantage
 Itrequires another server application to
install and maintain. Traversing the
recordset may take longer, since the data
comes through the backend server.
Type 4: All Java/Native-protocol driver
(Pure)

 The Type 4 uses java networking


libraries to communicate directly
with the database server.
Type 4: Native-protocol/all-Java
driver
Advantages
 The major benefit of using a type 4 jdbc
drivers are that they are completely
written in Java to achieve platform
independence and eliminate deployment
administration issues. It is most suitable
for the web.
 Number of translation layers is very less
i.e. type 4 JDBC drivers don't have to
translate database requests to ODBC or a
native connectivity interface or to pass the
request on to another server, performance
is typically quite good.
 You don’t need to install special software
on the client or server. Further, these
drivers can be downloaded dynamically.
Disadvantage
 With type 4 drivers, the user needs a
different driver for each database.
JDBC Driver Type Comparison

Category Type 1 Type 2 Type 3 Type 4

JDBC to ODBC JDBC using Native Middleware Pure Java


Basic Description
Bridge Methods JDBC Drivers Driver

Requires native install on


Yes Yes No No
client

Cross platform No Mostly Yes Yes

Requires additional server No No Yes No


Thank You

You might also like