eWebProgrammer eweb

JDBC   «Prev 

JDBC Architectural Models and the N-tier Model

N-tier model

1) Client GUI: This is the first tier in the three-tier-model. Requests are sent to the second tier where commands are sent to the second tier where commands are issued to the third tier for data
2) Application Server: The application server, with JDBC server technology, controls data source access from the middle tier, processes data server requests/results, and sends the data to the client HTML browser
3) Database: The data source processes commands from JDBC, sending the results back to the second tier application server.

As we will observe by examining questions and answers, JDBC provides a powerful, comprehensive interface for accessing databases from Java programs and servlets. The JDBC API allows any Java program, even an applet and servlet, to connect to a relational database management system (RDBMS) and perform queries and transactions. Servlets and JDBC are ideal for creating dynamic contents. Using JDBC from a Java servlet involves a three-tier distributed application, consisting of a user interface (the web browser), business logic (a series of Java servlets), and database access. The user interface is an HTML file in a browser. The middle tier is a Java servlet that handles requests from the client web browser and provides access to the third tier, a database accessed via JDBC.