Java Database Connectivity (JDBC) architecture is an API specifying interfaces for accessing relational databases. JDBC helps to connect to a database, send queries and updates to the database, and retrieve and process the results obtained from the database for queries.
The JDBC architecture supports two-tier and three-tier processing models for accessing a database.
In the two-tier model, a Java applet or application communicates directly to the data source. The JDBC driver enables communication between the application and the data source. When a user sends a query to the data source, the answers for those queries are sent back to the user in the form of results. The data source may not always be a single machine located at a single place. It can be located on a different machine on a network to which a user is connected. This is known as a client/server configuration, where the user’s machine acts as a client and the machine having the data source running acts as the server. The network connection can be intranet or Internet.
In the three-tier model, the user’s commands or queries are sent to middle-tier services, from which the commands are again sent to the data source. The results are sent back to the middle tier, and from there to the user. This type of model is found very useful by management information system directors, as it makes it simple to maintain access control and make updates to corporate data. Application deployment also becomes easy and provides performance benefits.
Java Database Connectivity (JDBC) architecture is an API specifying interfaces for accessing relational databases. JDBC helps to connect to a database, send queries and updates to the database, and retrieve and process the results obtained from the database for queries.
The JDBC architecture supports two-tier and three-tier processing models for accessing a database.
In the two-tier model, a Java applet or application communicates directly to the data source. The JDBC driver enables communication between the application and the data source. When a user sends a query to the data source, the answers for those queries are sent back to the user in the form of results. The data source may not always be a single machine located at a single place. It can be located on a different machine on a network to which a user is connected. This is known as a client/server configuration, where the user’s machine acts as a client and the machine having the data source running acts as the server. The network connection can be intranet or Internet.
In the three-tier model, the user’s commands or queries are sent to middle-tier services, from which the commands are again sent to the data source. The results are sent back to the middle tier, and from there to the user. This type of model is found very useful by management information system directors, as it makes it simple to maintain access control and make updates to corporate data. Application deployment also becomes easy and provides performance benefits.