Database Management System [DBMS] Architecture

Database Management System (DBMS) Architecture is a way how a database accessed by us. There are many DBMS Architecture, from the simplest architecture until the most modern architecture. Some kinds of them are:

1. Teleprocessing
2. File-Server Architecture
3. Two-Tier Client-Server Architecture
4. Three-Tier Client-Server Architecture
5. N-Tier Architecture
6. Peer-to-Peer Architecture
7. Distributed DBMS
8. Service-Oriented Architecture
9. Cloud Architecture
10. And so on

We just review some of them. Here they are:

•  Teleprocessing 
 

Teleprocessing is a traditional multi-user system architecture that have single mainframe and multiple (dumb)terminals. 

This system can enables terminals to access DBMS and database directly, but it also makes very heavy load to the mainframe because it must do two kind of operations:
1. Runs application programs and DBMS
2. Formats data for to be presented on terminals
Because of that, came a idea for replace the mainframe with network of personal computer.

• File-Server Architecture
 

A file-server is a computer that is connected to a network and mainly serves as a shared storage. 

In the file-server architecture, the processing is distributed over the network. Workstation (application and DBMS) must request data before they can get database. Since the file-server is not SQL-aware, the customer and Order relation (files) have to be transfered to the client. 

Some of disadvantages
1. Heavy network traffic
2. High total costs of ownership: maintain a full instance of the DBMS on each client (workstation).
3. Complex integrity, concurrency, and recovery control: Multiple DBMSs may concurrently access the same shared file.

• Three Tier Client Server Architecture

Three Tier Client Server Architecture has three part:
1. Presentation Tier (first tier) Tasks
• Presentation of data
• Basic input validation
• Send request to server and visualize results
2. Logic Tier (second tier/middle tier) Tasks
• Business logic
• Data Processing Logic
3. Data Tier (third tier) tasks
• Basic Data Validation
• Manage (concurrent) database access (data services)

Advantages:

1. Reduced costs for thin clients due to lower resource requirements because application running in web browser
2. Application logic is centralized in a single application server
3. Increased modularity: easier to replace one tier without affecting the other tier
4. Load Balancing become easier with a clear separation between the core business logic and the database functionality

Between the DBMS architecture above, I think the most powerful is Three Tier Client Server Architecture because it offers quick access to the data from its specialized function from every server and we can replace one tier without affecting the other tier so it is so easy to make a maintenance.