Database Architecture: Instructor: SAMIA ARSHAD
Database Architecture: Instructor: SAMIA ARSHAD
In 1-tier architecture, the DBMS is the only entity where the user directly sits
on the DBMS and uses it. Any changes done here will directly be done on the
DBMS itself. It does not provide handy tools for end-users. Database designers
and programmers normally prefer to use single-tier architecture.
Two tier architecture:
the client machine acts as merely a front end and does not contain any direct
database calls. Instead, the client end communicates with an application server,
usually through a forms interface.
The application server in turn communicates with a database system to access data.
For a user, this application tier presents an abstracted view of the database. End-
users are unaware of any existence of the database beyond the application. At the
other end, the database tier is not aware of any other user beyond the application
tier.
Independent modules and can be changed easily.
Three-tier applications are more appropriate for large applications, and for
applications that run on the WorldWideWeb.
Database tier, application tier, user tier