DBMS Chapter 1
DBMS Chapter 1
2-Tier Architecture
• In 2-Tier Architecture, the application and database are separate but
communicate directly.
• The client sends requests to the database server, which processes and
returns results.
• Common in client-server applications (e.g., applications using MySQL
with a frontend tool like Java or Python).
• Advantages: Faster than 3-tier, better security than 1-tier, suitable for
small-scale applications.
• Disadvantages: Performance issues in large systems, direct dependency
between client and database.
Example: A banking system where a frontend (Java-based) application
connects to a MySQL database.
3-Tier Architecture
• In 3-Tier Architecture, there are three layers:
1. Presentation Layer (User Interface) – Web or desktop application.
2. Application Layer (Business Logic) – Processes requests and
interacts with the database.
3. Database Layer – Stores and manages data.
• Provides better security, scalability, and performance compared to 2-
Tier.
• Common in large enterprise applications and web applications.
• Advantages: High security (as database is not exposed directly), scalable,
supports multiple clients.
• Disadvantages: More complex, requires additional infrastructure and
maintenance.
Example: E-commerce platforms like Amazon, where the website (frontend),
application logic (backend), and database are separate.
Different types of users in database administrator: