0% found this document useful (0 votes)
26 views6 pages

Database Architecture: Instructor: SAMIA ARSHAD

The document discusses different database architectures. A single-tier architecture has the user directly accessing the database management system (DBMS). A two-tier architecture separates the application and database tiers, with the application invoking database functionality through an interface. A three-tier architecture further separates the client, application server, and database tiers, with the client communicating only with the application server which then accesses the database.

Uploaded by

Ammar Siddiqi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
26 views6 pages

Database Architecture: Instructor: SAMIA ARSHAD

The document discusses different database architectures. A single-tier architecture has the user directly accessing the database management system (DBMS). A two-tier architecture separates the application and database tiers, with the application invoking database functionality through an interface. A three-tier architecture further separates the client, application server, and database tiers, with the client communicating only with the application server which then accesses the database.

Uploaded by

Ammar Siddiqi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 6

Database Architecture

Instructor: SAMIA ARSHAD


Database Architecture

 Single picture of Various components of a database system and the


connections among them.
 The architecture of a database system is greatly influenced by the underlying
computer system on which the database system runs.
 Centralized
 client-server (where one server machine executes work on behalf
of multiple client machines).
 Distributed
1 Tier Architecture

 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 application resides at the client machine, where it invokes database


system functionality at the server machine through query language
statements.
 Application program interface standards like ODBC and JDBC are used for
interaction between the client and the server.
 Here the application tier is entirely independent of the database in terms of
operation, design, and programming.
Three 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

You might also like