View RSS Feed


JDBC Architecture

Rate this Entry
by , 04-27-2012 at 07:11 PM (744 Views)
The JDBC API supports both two-tier and three-tier processing models for database access.

In the two-tier model, a Java application talks directly to the data source. This requires a JDBC driver that can communicate with the particular data source being accessed. A user's commands are delivered to the database or other data source, and the results of those statements are sent back to the user. The data source may be located on another machine to which the user is connected via a network. This is referred to as a client/server configuration, with the user's machine as the client, and the machine housing the data source as the server. The network can be an intranet, which, for example, connects employees within a corporation, or it can be the Internet.

Until recently, the middle tier has often been written in languages such as C or C++, which offer fast performance. However, with the introduction of optimizing compilers that translate Java bytecode into efficient machine-specific code and technologies such as Enterprise JavaBeans™, the Java platform is fast becoming the standard platform for middle-tier development. This is a big plus, making it possible to take advantage of Java's robustness, multithreading, and security features.

Submit "JDBC Architecture" to Facebook Submit "JDBC Architecture" to Digg Submit "JDBC Architecture" to Submit "JDBC Architecture" to StumbleUpon Submit "JDBC Architecture" to Google