DATABASE MANAGEMENT SYSTEM

DBMS ARCHITECTURE 

Database Management System (DBMS) architecture is designed to provide a systematic way of managing data efficiently. The architecture of a DBMS can vary depending on the design and the complexity of the database system. 

1. Single-Tier Architecture

In a single-tier architecture, the database is directly available to the user. Any changes or modifications in the database are made directly by the user. This type of architecture is rarely used in real-world applications because it doesn’t provide data abstraction or data independence.

2. Two-Tier Architecture

In a two-tier architecture, the DBMS is divided into two parts:

• Client Tier: The user interface is provided on the client side, where the user can send requests for data and receive results.
• Server Tier: The server handles the database operations such as query processing and transaction management.

In this architecture, the client application directly communicates with the database system. It’s often used in small-scale applications where the network load is minimal.

3. Three-Tier Architecture

The three-tier architecture adds another layer to the two-tier architecture, which is more scalable and supports a large number of users.

• Presentation Tier: This is the topmost layer where the user interface resides. It includes the applications and user interfaces that users interact with.
• Application Tier: Also known as the middle tier or logic tier, this layer contains the business logic and application programs that process data. It acts as a mediator between the presentation tier and the database tier.
• Database Tier: The bottom layer where the actual database resides. This layer is responsible for storing and retrieving data as requested by the application tier.