Scribd
Upload
9 views

Document 1

The document discusses different database management system (DBMS) architectures including 1-tier, 2-tier, and 3-tier. 1-tier architecture has direct access to the DBMS but is not suitable for large systems. 2-tier uses a client-server model but has poor performance for many users. 3-tier uses an intermediate layer for applications with many users.

Uploaded by

Inderjeet Maan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
9 views

Document 1

The document discusses different database management system (DBMS) architectures including 1-tier, 2-tier, and 3-tier. 1-tier architecture has direct access to the DBMS but is not suitable for large systems. 2-tier uses a client-server model but has poor performance for many users. 3-tier uses an intermediate layer for applications with many users.

Uploaded by

Inderjeet Maan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

A Database stores a lot of critical information to access data quickly and securely.

Hence it is
important to select the correct architecture for efficient data management. DBMS Architecture
helps users to get their requests done while connecting to the database. We choose database
architecture depending on several factors like the size of the database, number of users, and
relationships between the users. There are two types of database models that we generally use,
logical model and physical model. Several types of architecture are there in the database which
we will deal with in the next section.

Types of DBMS Architecture:

1-Tier Architecture In 1-Tier Architecture the database is directly available to the user, the user
can directly sit on the DBMS and use it that is, the client, server, and Database are all present on
the same machine. For Example: to learn SQL we set up an SQL server and the database on the
local system. This enables us to directly interact with the relational database and execute
operations. The industry won’t use this architecture they logically go for 2-tier and 3-tier
Architecture.

The 2-tier architecture is similar to a basic client-server model. The application at the client end
directly communicates with the database on the server side. APIs like ODBC and JDBC are used
for this interaction. The server side is responsible for providing query processing and transaction
management functionalities. On the client side, the user interfaces and application programs
are run. The application on the client side establishes a connection with the server side to
communicate with the DBMS. An advantage of this type is that maintenance and understanding
are easier, and compatible with existing systems. However, this model gives poor performance
when there are a large number of users.

In 3-Tier Architecture, there is another layer between the client and the server. The client does
not directly communicate with the server. Instead, it interacts with an application server which
further communicates with the database system and then the query processing and transaction
management takes place. This intermediate layer acts as a medium for the exchange of partially
processed data between the server and the client. This type of architecture is used in the case of
large web applications.

| 1-Tier | Direct access to DBMS, easy to learn, good for SQL learning | Not suitable for large
systems, all components on same machine |

| 2-Tier | Easy maintenance, compatible with existing systems, good for small to medium
applications | Poor performance with large number of users, client-server model |
x
| 3-Tier | Scalable for large web applications, data exchange through intermediate layer | More
complex, requires more resources |

You might also like