Learning Objectives

By the end of this chapter, you will be able to:

  • Understand the concept of Database System Architecture.
  • Differentiate between 1-tier, 2-tier, and 3-tier database architectures.
  • Explain the advantages of a 3-tier architecture.

What is Database Architecture?

Database architecture describes the design, structure, and operation of a Database Management System (DBMS). It defines how users, software applications, and the database itself interact with one another. The most common way to classify database architectures is by the number of “tiers” or layers between the user and the database.

1-Tier Architecture

In a 1-tier architecture, the database and the application both exist on the same machine. The user interacts directly with the database.

  • Use Case: Local application development, single-user desktop applications.
  • Pros: Extremely fast and simple to set up.
  • Cons: Not scalable, poor security, and no network access.

2-Tier Architecture (Client-Server)

In a 2-tier architecture, the user interface (client) runs on the user’s machine, while the database runs on a separate server. The client application connects directly to the database server.

  • Use Case: Internal company networks (LAN), simple desktop applications connecting to a central database.
  • Pros: Faster development, direct communication.
  • Cons: Hard to scale to thousands of users, less secure (direct database access), and heavy burden on the client application.

3-Tier Architecture

In a 3-tier architecture, an intermediate layer—the application server—is placed between the client and the database server.

  1. Presentation Tier (Client): The user interface (e.g., a web browser).
  2. Application Tier (Business Logic): The server-side code (e.g., PHP, Node.js) that processes rules and data requests.
  3. Database Tier: The DBMS (e.g., MySQL) where the data is stored.
  • Use Case: Almost all modern web applications.
  • Pros: High security (clients never touch the database), highly scalable, and easy to maintain.
  • Cons: More complex to design and implement.

Summary

The evolution from 1-tier to 3-tier architectures reflects the growing need for security, scalability, and distributed access in modern business computing. Understanding these layers is crucial for designing robust enterprise applications.