1 2 3 Tier Architecture
1 2 3 Tier Architecture
Hence it is
important to select a correct Architecture for efficient data management.
1- Tier Architecture
2- Tier Architecture
3- Tier Architecture
In One-Tier Architecture the database is directly available to the user, the user can directly sit on the
DBMS and use it i.e.; the client, server, and the Database are all present on the same machine. For
Example- To learn SQL we set up an SQL server and the database on the local system. This enables us
to directly interact with the relational database and execute operations. The industry won’t use this
architecture they logically go for 2-Tier and 3-Tier Architecture.
Two-Tier architecture:
The two-tier architecture is similar to a basic client-server model. The application at the client end
directly communicates with the database at the server side. APIs like ODBC and JDBC are used for
this interaction. The server side is responsible for providing query processing and transaction
management functionalities. On the client side, the user interfaces and application programs are
run. The application on the client side establishes a connection with the server side in order to
communicate with the DBMS.
An advantage of this type is that maintenance and understanding are easier, and compatible with
existing systems. However, this model gives poor performance when there are a large number of
users.
Three-Tier architecture:
In this type, there is another layer between the client and the server. The client does not directly
communicate with the server. Instead, it interacts with an application server which further
communicates with the database system and then the query processing and transaction
management takes place. This intermediate layer acts as a medium for the exchange of partially
processed data between server and client. This type of architecture is used in the case of large web
applications.
Advantages:
Data Integrity is maintained. Since there is a middle layer between the client and the server, data
corruption can be avoided/removed.
Security is improved. This type of model prevents direct interaction of the client with the server
thereby reducing access to unauthorized data.
Disadvantages:
Increased complexity of implementation and communication. It becomes difficult for this sort of
interaction to take place due to the presence of middle layers.