In client/server systems, there are several types of configurations. This article will get into detail of the client server architecture and more precisely, 2-tier architecture and 3-tier architecture. We also explain the differences and the similarities of the two systems.
2-tier architecture is used to describe client/server systems in which the client requests resources and the server responds directly to the request, using its own resources. This means that the server does not call on another application in order to provide part of the service:
In 3-tier architecture, there is <bold>an intermediary level, meaning that the architecture is generally split up between:
|The widespread use of the term 3-tier architecture also denotes the following architectures:
2-tier architecture is a client-server architecture where the server is versatile, meaning it is capable of directly responding to all of the client's resource requests. In 3-tier architecture, however, the server-level applications are remote from one another, meaning each server is specialized with a certain task (for example: web server/database server).
3-tier architecture provides:
In 3-tier architecture, each server (tier 2 and 3) performs a specialized task or service. A server can, therefore, use services from other servers in order to provide its own service. As a result, 3-tier architecture is potentially an n-tiered architecture: