Client Server
Client Server
Communication between clients and servers is usually achieved through a network, such as the
internet or an intranet.
CLIENT :
Server :
1 Tier Architecture
2 tier architecture
3 tier architecture
I-tier architecture :-
In a 1-tier architecture, also known as a monolithic clear architecture, there is no
separation between the client, server, and data layers.
In I-Tier Architecture, everything related to the application is grouped and used as a
single package to deliver the application.
This approach is typically used for small applications or prototypes where simplicity and
ease of development take precedence over scalability and maintainability.
A I-tier architecture offers various services that make it a reliable source, but it is
complex to manage. The data variance is the primary problem.
These systems keep their data in a shared driver or a local file. The MS Office files are
example of I-tier apps.
2 Tier Architecture
The whole application logic is divided into 2 layers. At server side, database acts
as a separate entity in this architecture.
In comparison to 1-tier architectures, 2-tier architectures are faster since there is_no
intermediary between the client and the server. The 2-tier architecture helps avoid
client confusion.
A two-tier architecture is suitable for small to moderately complex applications
where simplicity and quick development are essential.
However, for larger and more scalable applications, a three-tier or multi-tier
architecture might be more appropriate.
The online reservation system is a popular example of a 2-tier architecture.