0% found this document useful (0 votes)
10 views17 pages

Web Architecture

Web architecture encompasses the design and structure of the World Wide Web, focusing on the interaction between clients and servers through the client-server model. Key components include clients, servers, networks, protocols, databases, and middleware, which work together to facilitate web functionality. While client-server architecture offers advantages like scalability and centralized management, it also presents challenges such as single points of failure and security risks.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views17 pages

Web Architecture

Web architecture encompasses the design and structure of the World Wide Web, focusing on the interaction between clients and servers through the client-server model. Key components include clients, servers, networks, protocols, databases, and middleware, which work together to facilitate web functionality. While client-server architecture offers advantages like scalability and centralized management, it also presents challenges such as single points of failure and security risks.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

WEB ARCHITECTURE

AND CLIENT-SERVER
MODEL
WEB ARCHITECTURE

Web architecture refers to the design and structure of the


World Wide Web, encompassing the technologies, protocols,
and systems that enable the web to function. The client-server
model is a fundamental concept in web architecture, defining
how clients (users) and servers (service providers) interact
over the internet.

Example:
When you type a URL into your browser, your browser (the
client) sends a request to a web server, which then sends
KEY COMPONENTS OF WEB ARCHITECTURE

- Devices or software (e.g., web browsers, mobile apps) that


1. CLIENTS
request and display content from servers.
- Examples: Chrome, Firefox, Safari, or mobile apps.

- Computers or systems that store, process, and deliver


2. SERVERS resources (e.g., web pages, data) to clients.
- Examples: Web servers (Apache, Nginx), application
servers, and database servers.

3. NETWORKS - The infrastructure (e.g., internet, routers, DNS) that


facilitates communication between clients and servers.
- Rules and standards for communication between clients
4. PROTOCOLS
and servers.
- Examples: HTTP/HTTPS (for web requests), TCP/IP (for
data transmission), and WebSocket (for real-time
communication).

5. DATABASES - Systems that store and manage data for web


applications.
- Examples: MySQL, MongoDB, PostgreSQL.

6. MIDDLEWARE - Software that connects different components of a web


application, such as APIs, authentication systems, and
load balancers..
CLIENT SERVER MODEL

The client-server model is a distributed


application structure that divides tasks between
service providers (servers) and service
requesters (clients).
HOW IT WORKS

CLIENT REQUEST - A client sends a request to a server for a specific


resource (e.g., a web page, image, or data).
- Example: Typing a URL in a browser sends an HTTP
request to a web server.

SERVER - The server receives the request, processes it, and


PROCESSING
retrieves or generates the requested resource.
- Example: A web server fetches an HTML file or queries
a database.
HOW IT WORKS

SERVER RESPONSE - The server sends the requested resource back to the client.
- Example: The server returns an HTML page, which the browser renders.

CLIENT RENDERING - The client receives the response and displays or processes the data.
- Example: The browser renders the HTML page and displays it to the
user.
TYPES OF CLIENT SERVER ARCHITECTURE
TWO-TIER ARCHITECTURE N-TIER ARCHITECTURE

- Adds a middle tier (e.g.,


- Involves a client and application server) - Divides the application
a server directly between the client and into multiple layers (e.g.,
communicating.
server. presentation, business logic,
- Example: A web
- Example: Browser → data storage).
browser (client)
interacting with a web Application Server → - Example: Modern web
server. Database Server. applications with separate

THREE-TIER ARCHITECTURE layers for UI, APIs, and


databases.
EXAMPLES OF CLIENT-SERVER
ARCHITECTURE

2. Email

1. Web Browsing: 3. File Sharing


Sending and receiving
emails, where your email
Accessing files on a network
Browsing the internet, where client is the client and the
server, where your computer
your browser is the client and email server is the server.
is the client and the file
the web server is the server.
server is the server.
ADVANTAGE OF CLIENT SERVER ARCHITECTURE
Clients offload
Servers can handle processing tasks to
multiple clients servers, reducing their
simultaneously. workload.

SCALABILITY EFFICIENCY
CENTRALIZED
MANAGEMENT SECURITY

Data and Servers can enforce


resources are security policies and
managed protect sensitive
centrally on data.
servers.
DISADVANTAGE OF CLIENT-SERVER ARCHITECTURE
Handling more clients can
If the server fails, all overwhelm the server,
clients lose access. making scaling costly and
complex.

Single Point of Failure Scalability Challenges

Network Security Risks


Dependency

Requires a stable Servers are prime


network; poor targets for attacks
connectivity (e.g., DDoS, data
disrupts service. breaches).
COMMON WEB ARCHITECTURE

2. Microservices
Architecture

1. Monolithic Architecture - Breaks the application into 3. Serverless Architecture


small, independent services
- A single, unified application that communicate over APIs.
- Uses cloud services to run
where all components (UI, - Example: Modern cloud-based
code without managing
logic, database) are tightly applications like Netflix or Amazon.
servers.
coupled.
- Example: AWS Lambda or
- Example: Traditional web
Google Cloud Functions.
applications built as a single
codebase.
KEY PROTOCOLS IN WEB ARCHITECTURE :

HTTP/HTTPS WEBSOCKET

- Hypertext Transfer - Enables real-time,


Protocol (Secure) for bidirectional
transferring web pages communication
and data. between clients and
servers.
TCP/IP DNS

- Hypertext Transfer - Domain Name

Protocol (Secure) for System for translating

transferring web pages domain names into IP

and data. addresses.


THANK YOU

You might also like