1 of 10

DBMS ARCHITECTURE

Prof.manoj kumar padhi

2 of 10

DBMS ARCHITECTURE

A DBMS architecture defines how users interact with the database to read, write, or update information. A well-designed architecture and schema (a blueprint detailing tables, fields and relationships) ensure data consistency, improve performance and keep data secure.

Types of DBMS Architecture

There are several types of DBMS Architecture that we use according to the usage requirements.

  • 1-Tier Architecture
  • 2-Tier Architecture
  • 3-Tier Architecture

​

3 of 10

1-TIER ARCHITECTURE

  • In 1-Tier Architecture, the user works directly with the database on the same system.
  • This means the client, server and database are all in one application.
  • The user can open the application, interact with the data and perform tasks without needing a separate server or network connection.
  • Any changes done here will directly be done on the database itself. It doesn't provide a handy tool for end users.
  • The 1-Tier architecture is used for development of the local application, where programmers can directly communicate with the database for the quick response.

​

4 of 10

2-TIER ARCHITECTURE

  • The 2-Tier architecture is same as basic client-server. In the two-tier architecture, applications on the client end can directly communicate with the database at the server side. For this interaction, API's like: ODBC, JDBC are used.
  • The user interfaces and application programs are run on the client-side.
  • The server side is responsible to provide the functionalities like: query processing and transaction management.
  • To communicate with the DBMS, client-side application establishes a connection with the server side.

​

5 of 10

  • Client Layer (Tier 1): This is the user interface that library staff or users interact with. For example they might use a desktop application to search for books, issue them, or check due dates.
  • Database Layer (Tier 2): The database server stores all the library records such as book details, user information and transaction logs.

​

6 of 10

3-TIER ARCHITECTURE

  • The 3-Tier architecture contains another layer between the client and server. In this architecture, client can't directly communicate with the server.
  • The application on the client-end interacts with an application server which further communicates with the database system.
  • End user has no idea about the existence of the database beyond the application server. The database also has no idea about any other user beyond the application.
  • The 3-Tier architecture is used in case of large web application.

​

7 of 10

8 of 10

PRESENTATION OR CLINT LAYER

  • The presentation tier is the user interface or client layer of the application.
  • It is responsible for presenting data to the user and receiving input from the user.
  • This layer communicates with the Application layer to process user requests and display relevant information.
  • This layer can be a web browser, mobile app, or desktop application.

9 of 10

APPLICATION LAYER

  • The application tier is the middle layer of the 3-tier architecture. It acts as the intermediary between the Presentation Tier and the Data Management Tier.
  • It is responsible for processing and managing the business logic of the application.
  • This tier communicates with the presentation tier to receive user input and communicates with the data management tier to retrieve or store data.
  • This tier may include application servers, web servers, or APIs.

10 of 10

DATABASE LAYER

  • The Data Management tier is the bottom layer of the 3-tier architecture.
  • It is responsible for managing and storing data.
  • This tier can include databases, data warehouses, or any other persistent data storage solution.
  • The data management tier communicates with the application tier save, retrieve, or manipulate data according to the business logic.