Madhav

Institute
of
Technology

Database Management System &

Science
Gwalior (M.P.)
(Deemed
University)

By

Prof. Ramnaresh Sharma

Assistant Professor
Centre for Artificial Intelligence
DBMS Architecture:
• The design of a DBMS depends on its architecture. It can be centralised or
decentralised or hierarchical. The architecture of a DBMS be either single tier or
multi-tier. An n-tier architecture divides the entire system into related but
independent n modules, which can be independently modified, altered, changed,
or replaced.
• 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 usually prefer to use single-tier
architecture.
• If the architecture of DBMS is 2-tier, then it must have an application through
which the DBMS can be accessed. Programmers use a 2-tier architecture where
they access the DBMS using an application. Here the application tier is entirely
independent of the database regarding operation, design, and programming.
• .
3-Tier Architecture

• Database (Data) Tier - At this tier, the database resides along with its query processing
languages. We also have the relations that define the data and their constraints at this level.
• Application (Middle) Tier - At this tier reside the application server ad the programs that
access the database. 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. Hence, the application layer sits in the middle and acts as a mediator between the end-
user and the database.
• User (Presentation) Tier - End-users operate on this tier, and they know nothing about any
existence of the database beyond this layer. At this layer, multiple views of the database
can be provided by the application. All views are generated by applications that reside in
the application tier
Application Architecture of DBMS:
• A Database Management System (DBMS) typically follows a
layered architecture, which helps in managing, storing, and Madhav
Institute
retrieving data efficiently. The architecture can vary of
Technology
depending on the DBMS type (e.g., relational, NoSQL), but &
a common structure is outlined below: Science
Gwalior (M.P.)
• 1. Physical Layer (Storage Layer) (Deemed
University)

• Data Storage: The physical layer is responsible for storing

the data on the physical storage media like disks. It includes
details about file structures, indexes, and data organization
on the disk.
• Buffer Management: This component handles the data in
memory to reduce disk I/O operations. It ensures that
frequently accessed data is kept in memory to improve
performance.
• File Management: Manages the allocation and deallocation
Application Architecture of DBMS(Cont.):
2. Logical Layer (Conceptual Layer)
• Schema Management: Defines the database schema, including tables,
Madhav
relationships, constraints, and data types. The schema is a logical Institute
of
representation of the data. Technology
&
• Data Dictionary: Also known as metadata, this component stores Science
information about the database objects like tables, columns, data types, Gwalior (M.P.)
(Deemed
constraints, and indexes. University)

• Query Processor: This component interprets and executes SQL queries. It

includes:
– Parser: Checks syntax and transforms the query into an internal
format.
– Query Optimizer: Optimizes the query for efficient execution, choosing
the best plan based on available indexes and join operations.
– Execution Engine: Executes the optimized query plan by interacting
with the storage manager.
Application Architecture of DBMS(Cont.):
3. External Layer (User Interface Layer)
• User Interface: This layer provides the means through which end Madhav
Institute
users interact with the DBMS. It includes GUI tools, command-line of
Technology
interfaces, or APIs that allow users to query, modify, and manage &
the database. Science
Gwalior (M.P.)
• Application Programs: These are external programs that interact (Deemed
University)
with the DBMS to perform specific tasks, like data entry or report
generation.
• End User: The person or application that interacts with the DBMS to
access and manipulate the data.
Application Architecture of DBMS(Cont.):
4. Transaction Management Layer
Madhav
• Transaction Manager: Ensures the ACID (Atomicity, Consistency, Isolation, Institute
of
Durability) properties of transactions. It handles the execution of Technology
&
concurrent transactions, ensuring that the database remains consistent. Science
Gwalior (M.P.)
• Concurrency Control: Manages simultaneous operations without conflicts, (Deemed

using mechanisms like locking, timestamping, or multi-version concurrency University)

control (MVCC).
• Recovery Manager: Ensures that the database can recover to a consistent
state after a failure. It handles backups, logging, and restoring operations.
Application Architecture of DBMS(Cont.):
Madhav Institute
5. Security and Authorization Layer of
Technology
Access Control: Manages user permissions, ensuring that only &
authorized users can access or modify certain data. Science
Gwalior (M.P.)
Encryption: Protects sensitive data both at rest and in transit by (Deemed
University)
encrypting it.
Auditing: Tracks and logs database activities for security and
compliance purposes
Application Architecture of DBMS(Cont.):
6. Data Integrity Layer
• Integrity Constraints: Ensures that the data stored in the database
remains accurate and consistent. This includes enforcing primary
keys, foreign keys, unique constraints, and other business rules.
• Validation Rules: These are checks applied to data entry or
updates to ensure that the data adheres to predefined formats or
constraints.
Application Architecture of DBMS(Cont.):
7. Communication Layer
Madhav
• Network Communication: Facilitates communication between the DBMS Institute
and client applications over a network. This includes managing data transfer of
Technology
protocols and ensuring data consistency across distributed databases. &
Science
• Middleware: Provides additional services like load balancing, connection Gwalior (M.P.)
(Deemed
pooling, and distributed transaction management. University)
Application Architecture of DBMS(Cont.):

8. Backup and Recovery Layer

• Backup Management: Automates the backup process to ensure
Madhav
data is regularly backed up and can be restored in case of data loss. Institute
of
• Disaster Recovery: Provides strategies and tools to recover data Technology
and maintain continuity in case of major failures. &
Science
Gwalior (M.P.)
(Deemed
University)
Application Architecture of DBMS(Cont.):
9. Replication and Clustering (Optional)
• Replication: Involves copying and maintaining database objects in Madhav
Institute
multiple databases for high availability and fault tolerance. of
Technology
• Clustering: Involves using multiple servers to improve database &
Science
performance and reliability through load balancing and failover Gwalior (M.P.)
mechanisms. (Deemed
University)
Application Architecture of DBMS(Cont.):
• This architecture ensures that the DBMS is modular,
scalable, and capable of handling complex tasks efficiently.
Madhav
Different DBMS products might implement these layers in Institute
various ways, but the core concepts remain consistent. of
Technology
. &
Science
Gwalior (M.P.)
(Deemed
University)
 Madhav
Institute
of
Technology
&

Thank You
Science
Gwalior (M.P.)
(Deemed
University)