Introduction
Client/Server architecture is a style of computing involving servers and clients communicating & cooperating over the Internet to accomplish things.
There is a distribution of presentation services, application code, and data across clients and servers. A networking protocol is used for communication between clients and servers. In this model, the “client” requests or delegates business logic to the server. The server processes and responds to client’s responses as shown in the diagram.
Tiered Architecture
Client/Server is a tiered architecture. It has several layers and components, which can be visualized in either a conceptual or a physical manner. When you look at the client-server architecture conceptually, these layers are presentation, process, and database. Physically components in this model are the server, client, middleware, and network.
2-tier Architecture
In this model, all of the presentation logic and the business logic are implemented as processes on the client. 2-tiered architecture implements a “fat” client. Nearly all of the processing happens on the client, and the client accesses the database directly rather than through any middleware.
3-tier Architecture
In this model, the application is divided into a presentation tier, a middle tier, and a data tier. The middle tier comprises one or more application servers distributed across one or more physical machines.
In most cases, the client machine runs a piece of software known as the web browser. The browser sends the client request over the internet to the server. The server analyzes the request, processes it, and sends back the response to the client.
