Database management in client/server, 3 tier internet architecture

Database management in client/server architecture: In a Client/Server architecture, computer systems are in a local area network with a database server. This database server is used to save shared database. In this architecture front end of DBMS like application programs run in computer systems. Back end of DBMS which is used to save and manage data is run on the server.

Working: A user creates a SQL request. This request is then sent to the database engine of the DBMS for processing. DBMS accesses database, computes the result and by the help of application programs, the result is displayed on the screen.

Advantage of Client/Server architecture: Since it uses front end and back end, network traffic is greatly reduced in this architecture.

Disadvantage of Client/Server architecture: Portability of application programs is a problem in client/server architecture. If a application program is updated, it has to be updated on all the client machines.

Database management in client/server architecture

Database management in 3 tier internet architecture: In 3 tier Internet architecture, first tier is the web browser running in a computer system. It is the front end of the database. In second tier, browser communicates with the web server. When a user wants to access a dynamic web page then the web server communicates with the application server. Application server is used to process an application request. After that, application server communicates with the mainframe and database server in tier 3 to process the request. This acts as a back end for the database. JDBC (Java Database Connectivity) is used as the standard API used by application servers to access database. Databases are accessed by the use of SQL.

Database management in 3 tier internet architecture

Leave a Reply