Database Architecture: Types, Components, and Examples

This PowerPoint presentation provides a comprehensive overview of Database Architecture, explaining the structure, components, and types of database systems, including 1-Tier, 2-Tier, 3-Tier, and N-Tier architectures. Designed for MBA students and data management learners, it highlights how databases interact with users and applications, explores logical and physical architectures, and connects theoretical concepts to real-world business, cloud, and AI applications.

Prepared by Dr. Sasidharan M, this lecture emphasizes the importance of layered architectures in enterprise systems and digital transformation.

1. Database Architecture Lecture – II © 2025 Dr. Sasidharan M. All Rights Reserved.

2. Learning Objectives After completing this lecture, students should be able to: Understand what is meant by database architecture. Explain the different types of database architectures (1-tier, 2-tier, 3-tier, and N-tier). Understand how a DBMS interacts with users and applications. Identify the components of a database system. Relate database architecture to real-world business and AI applications. © 2025 Dr. Sasidharan M. All Rights Reserved.

3. Introduction Database architecture defines the structure and interaction of the database components — how users, applications, and storage systems communicate through the DBMS. In simple terms, database architecture explains how data flows from the user (front-end) to the database (back-end) and back again. © 2025 Dr. Sasidharan M. All Rights Reserved.

4. Organizational Database Systems © 2025 Dr. Sasidharan M. All Rights Reserved.

5. Components of Database System Hardware: The physical devices such as servers, storage drives, and networking systems where data is stored and processed. Software: The DBMS software and related programs that control data storage, retrieval, and manipulation. Examples: Oracle, MySQL, PostgreSQL, SQL Server, MongoDB. Data: The most crucial part — it includes all the stored information (customer details, transactions, product data, etc.). Users Database Administrators (DBA): Manage the database and ensure performance and security. Developers: Design and build database-driven applications. End Users: Use applications to interact with data (e.g., entering or retrieving data). Procedures: The rules and instructions that control how data is managed, accessed, and maintained. © 2025 Dr. Sasidharan M. All Rights Reserved.

6. Types of Database Architecture There are different architectural models that define how the database system is organized. Single – Tier Architecture Two – Tier Architecture Three – Tier Architecture N – Tier (Multi – Tier) Architecture © 2025 Dr. Sasidharan M. All Rights Reserved.

7. Single – Tier Architecture The database and the user interface exist on the same machine. The user directly interacts with the DBMS without any intermediary. Mostly used for learning, testing, or local applications. Eg. MS Access © 2025 Dr. Sasidharan M. All Rights Reserved.

8. Advantages & Disadvantages Advantages Simple and easy to set up. No need for network communication. Disadvantages Not suitable for multi-user or large-scale systems. Limited scalability and security. © 2025 Dr. Sasidharan M. All Rights Reserved.

9. Two – Tier Architecture In this model, the application (client) communicates directly with the database (server). The client handles the user interface and some business logic. The server manages data storage and queries. Eg. A bank’s teller application that connects directly to a central database server. © 2025 Dr. Sasidharan M. All Rights Reserved.

10. Advantages & Disadvantages Advantages Faster communication between client and server. Easy to develop and maintain small systems. Disadvantages High network load when many clients are connected. Limited scalability; performance drops with increasing users. © 2025 Dr. Sasidharan M. All Rights Reserved.

11. Three – Tier Architecture This is the most commonly used model in enterprise and cloud environments. It separates the system into three layers: Presentation Layer (User Interface Application Layer (Business Logic) Database Layer (Data Storage) © 2025 Dr. Sasidharan M. All Rights Reserved.

12. Advantages & Example Advantages High scalability and security. Easier maintenance and upgrades. Suitable for distributed systems and cloud environments. Example in business Amazon or Flipkart — user interface (app), business logic (server-side program), and database (AWS or Oracle backend). © 2025 Dr. Sasidharan M. All Rights Reserved.

13. N-Tier (Multi-Tier) Architecture Extends the 3-tier model by adding specialized layers for analytics, reporting, or caching. Used in large enterprises and cloud-based AI systems. © 2025 Dr. Sasidharan M. All Rights Reserved.

14. Advantages & Disadvantages Advantages Highly scalable and modular. Enables integration with external services (like ML models, APIs, etc.). Disadvantages Complex to design and manage. Requires high infrastructure costs. © 2025 Dr. Sasidharan M. All Rights Reserved.

15. Logical and Physical Database Architecture Logical Architecture: Describes how data is organized and managed at a conceptual level — includes entities, attributes, and relationships. Example: How “Customers,” “Products,” and “Orders” are related. Physical Architecture: Describes how data is actually stored in files, disks, and servers. Example: File systems, indexes, partitions, and clusters. © 2025 Dr. Sasidharan M. All Rights Reserved.

16. Centralized vs Distributed Database Architecture Type Description Example Centralized Database All data is stored in one central location (one server). University admin system on a central server Distributed Database Data is stored across multiple systems connected by a network. Cloud-based applications, multinational companies © 2025 Dr. Sasidharan M. All Rights Reserved.

17. Client-Server Architecture in Databases The client sends requests (queries) to the server. The server processes these requests, accesses the database, and returns the results. This separation improves performance, especially when many users are connected simultaneously. Example: In a retail analytics dashboard, multiple managers query sales data from their laptops (clients) while the main data resides in a central warehouse server. © 2025 Dr. Sasidharan M. All Rights Reserved.

18. Applications of Database Architectures Banking Sector 3-tier architecture for secure transactions and data retrieval. Ensures data integrity across branches and ATMs. E-Commerce Multi-tier system for shopping, inventory, and payment processing. Enables personalization and recommendation systems. Healthcare Distributed databases for patient records across hospitals. Ensures privacy and real-time data access. Airline Management Real-time seat booking, route management, and customer databases. Uses client-server model integrated with global systems. © 2025 Dr. Sasidharan M. All Rights Reserved.

19. Advantages of Layered Database Architecture Simplifies maintenance and development. Improves data security through controlled access. Enhances scalability — each layer can be upgraded independently. Promotes modular design and flexibility. Suitable for cloud computing and large-scale data processing. © 2025 Dr. Sasidharan M. All Rights Reserved.

20. Challenges in Database Architecture Complexity in integrating multiple tiers. Network latency between layers. Higher cost for infrastructure and maintenance. Ensuring data consistency in distributed environments. Balancing security, performance, and accessibility. © 2025 Dr. Sasidharan M. All Rights Reserved.