U1T5 Data_base_Environment(DBMS Architecture)
U1T5 Data_base_Environment(DBMS Architecture)
ONE-TIER-ARCHITECTURE
In DBMS is the simplest architecture of database in which the client, server and
database all reside on the same machine.
One-tier architecture example would be anytime you install a database in your system
and access is to practice SQL queries but such architecture is rarely used in production.
This setup is simple and is often used in personal or standalone applications where the
user interacts directly with the database.
Two-Tier Architecture
The two-tier Architecture is similar to a basic client-server model.
The application at the client end directly communicated with the database at the
server side.
API’s like ODBS,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.
For Example: A Library Management System used in schools or small organizations is a classic
example of two-tier architecture.
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.
The client layer sends a request (like searching for a book) to the database layer which
processes it and sends back the result. This separation allows the client to focus on the user
interface, while the server handles data storage and retrieval.
THREE-TIER ARCHITECTURE
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.
User: You visit an online store, search for a product and add it to your cart.
Processing: The system checks if the product is in stock, calculates the total price and applies
any discounts.
Database: The product details, your cart and order history are stored in the database for future
reference