DBMS Architecture (1, 2, 3-Tier & Three-Schema)
In this lesson: Learn DBMS architecture — 1, 2 and 3-tier and three-schema (internal, conceptual, external) — with diagrams and examples.
What is database architecture
Database architecture describes how the parts of a database system — the user, the application, and the database — are arranged and how they talk to each other. The main models are 1-tier, 2-tier and 3-tier, differing in how many layers separate the user from the data. A separate idea, the three-schema architecture, describes the levels inside the database itself.
1-tier architecture
In 1-tier, the user, application and database all live on one machine, with no network in between. You interact directly with the database on your own computer.
User + Application + Database → all on one computer
It is simple and fast for local use or learning, but not suitable for many users at once.
2-tier architecture
In 2-tier, a client application talks directly to a database server over a network.
Client app ⇄ Database server
This is the classic client-server model. It works well for small setups, but the client is tied closely to the database, which limits security and scalability.
3-tier architecture
In 3-tier, a middle application server sits between the client and the database.
Client ⇄ Application server ⇄ Database server
The middle layer handles business logic and security, and hides the database from users. This is what web applications use, because it is secure, scalable, and lets many clients connect through one logic layer.
Three-schema architecture
Separate from tiers, the three-schema architecture describes levels inside the database:
- External — how each user sees the data (views).
- Conceptual — the overall logical structure of all tables.
- Internal — how data is physically stored on disk.
This separation gives data independence: one level can change without disturbing the others.
Which to use
| Architecture | Best for |
|---|---|
| 1-tier | Local tools, learning |
| 2-tier | Small client-server apps |
| 3-tier | Web and enterprise apps |
Most modern applications, especially on the web, use 3-tier for security and scalability.
Common mistakes
- Confusing tiers with the three-schema architecture. Tiers are about layers between user and data; schemas are internal levels.
- Using 2-tier for large web apps. They need the middle layer of 3-tier.
- Thinking 1-tier scales. It is for a single machine only.
- Ignoring the middle layer's role. It provides logic and security in 3-tier.
Summary
- Database architecture arranges user, application and database.
- 1-tier: all on one machine; 2-tier: client to database directly.
- 3-tier: a middle application server for logic and security (used by web apps).
- The three-schema architecture describes external, conceptual and internal levels.
- Most modern systems use 3-tier.
Next, learn the internal levels in schema vs instance, or how they stay independent in data independence.
