Scribd
Upload
17 views2 pages

Module 2

The document discusses client-server architecture and its key components. A client-server model partitions tasks between service providers (servers) and service requesters (clients). The client sends a request to the server via the internet, and the server processes the request and returns the requested data to the client. The document also describes the layers of an application, including the presentation, application, and data management layers, and provides examples. Finally, it discusses two-tier client-server architecture and the thin-client and fat-client models.

Uploaded by

Cinnamon Pop
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
17 views2 pages

Module 2

The document discusses client-server architecture and its key components. A client-server model partitions tasks between service providers (servers) and service requesters (clients). The client sends a request to the server via the internet, and the server processes the request and returns the requested data to the client. The document also describes the layers of an application, including the presentation, application, and data management layers, and provides examples. Finally, it discusses two-tier client-server architecture and the thin-client and fat-client models.

Uploaded by

Cinnamon Pop
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Demi Anne B.

Cahiles SE 2 - Software Engineering


BSCS 3 Distributed Systems

CLIENT-SERVER ARCHITECTURE
A Client-Server Architecture. also known as the Client-Server Model, is a distributed
application structure that partitions task or workload between the providers of a resource or
service, called servers, and service requester called clients. A Client is a computer (Host) i.e.
capable of receiving information or using a particular service from the service providers
(Servers). On the other hand, a Server is a remote computer which provides information (data)
or access to particular services

The client computer sends a request for data to the server through the internet, the
server accepts the requested process and deliver the data packets requested back to the client.

LAYERS OF AN APPLICATION

The design of client–server systems should match how the different parts of the
application function and interact with each other logically.
1. Presentation Layer - the front end of an application; responsible for showing
information to users and handling any interactions they have with the application.
EXAMPLE: when you use a website or an app, the buttons you click, the forms you fill out, and the screens
you see are all part of the presentation layer
2. Appliaction Layer - the brains of the application; responsible for figuring out what needs
to be done based on your inputs and the application's rules.
EXAMPLE: if you're using a shopping app, the processing layer would handle tasks like adding items to your
cart, calculating totals, and processing payments
3. Management Layer - all about handling the application's data; responsible for storing
and retrieving all the data needed to make the application work.
EXAMPLE: in a social media app, the data management layer would handle tasks like storing user profiles,
posts, comments, and photos

(CONTINUED ON THE NEXT PAGE. . .)


Demi Anne B. Cahiles SE 2 - Software Engineering
BSCS 3 Distributed Systems

TWO-TIER CLIENT-SERVER ARCHITECTURE

A Two-Tier Client-Server Architecture is known to be the simplest type of client–


server architecture, where an application is organized as a server (or multiple identical
servers) and a set of clients. It is also known as a client-server architecture with two layers,
hence its name. This type of architecture can take two forms:
1. Thin-Client Model
In a thin-client model, the server takes on the bulk of the workload, handling
both application processing and data management. Clients, or "thin clients," are
responsible for running presentation software only. This means they handle the user
interface and display the information received from the server. Thin clients typically
have limited processing power and resources because they rely heavily on the server for
computational tasks.
EXAMPLES: These include web browsers accessing web-based applications, where most of the processing
happens on the server, and the browser mainly renders the interface and displays data.
2. Fat-Client Model
In a fat-client model, the server's role is primarily focused on data management.
It stores and manages the application's data but doesn't handle application processing.
Clients, or "fat clients," are responsible for both running presentation software and
performing application processing. Fat clients have more processing power and
resources compared to thin clients because they handle a significant portion of the
application logic locally.
EXAMPLES: These include desktop applications or mobile apps that perform substantial processing locally,
interacting with the server primarily for data retrieval and storage.

EXAMPLE OF A SYSTEM ARCHITECTURE DESIGN

You might also like