Every time you type a web address and a page appears on your screen, a remarkable sequence of events takes place behind the scenes. Computers thousands of kilometres apart exchange messages, locate the right file, and deliver it to you in less than a second. The World Wide Web makes this look effortless, but it rests on a clear and logical structure. Understanding the architecture of the Web means looking at the parts that make it work and the rules that let them cooperate. Let us break down this framework piece by piece.

Table of Contents

What the World Wide Web actually is

People often use “the Internet” and “the World Wide Web” as if they mean the same thing, but they are different. The Internet is the global network of physical infrastructure that connects billions of devices. The Web is a service that runs on top of the Internet. More precisely, the Web is a system of interlinked hypertext documents accessed through browsers using standard protocols. So the Internet is the road network, and the Web is one of the many kinds of traffic that travel on it.

The entire Web is built on three foundational technologies working together: an addressing system to locate resources, a protocol to communicate, and a markup language to represent documents. The original design at CERN combined URLs for addressing, HTTP for communication, and HTML for displaying formatted pages consistently across different machines. These three pillars still hold up the Web today.

Components of the Web

Before looking at how the Web behaves, it helps to know the physical and software pieces involved. Each one plays a specific role in moving a web page from a distant computer to your screen.

Personal computers and devices

This is the device in your hands or on your desk: a laptop, a smartphone, or a tablet. It is the starting point of every web interaction. You use it to enter a request and to view whatever comes back. Without an end-user device, there is no one to make a request and nothing to display the result.

Web browsers

A web browser is the software that turns raw web data into a readable page. Chrome, Firefox, Safari, and Edge are common examples. The browser does several jobs at once. It sends your request out to the Internet, receives the response, interprets the code inside it, and arranges everything into the text, images, and buttons you see. In technical terms, the browser is the client, the part that asks for content.

Internet connections

None of this works without a connection that links your device to the wider network. Internet connections, whether wired or wireless, connect personal devices to the broader internet infrastructure and allow data to travel in both directions. A broadband line, mobile data, or a Wi-Fi network all serve this purpose. The quality of this connection affects how quickly pages load.

Servers

A server is a powerful computer that stores websites and waits for requests. When your browser asks for a page, the server finds the right file and sends it back. Servers run continuously so that content is available at any time of day. A single server can handle requests from thousands of users, and large websites use many servers working together.

Routers

Data does not travel from a server to your device in a straight line. It passes through many points along the way. Routers act as traffic controllers, ensuring that data packets reach their correct destination. Each router reads the address attached to a packet of data and forwards it one step closer to where it needs to go. This is how information finds its path across a network that spans the entire planet.

Client-server architecture

The way these components interact follows a model called client-server architecture. This is the organising principle of the whole Web. The work is split between two roles, and each role has clear responsibilities.

How the two roles divide the work

In this model, the client is the device or application that requests resources, and the server is the machine that stores and delivers them. The client initiates communication, sends requests, provides the user interface, and displays the results. The server, in turn, processes requests, manages data, executes the necessary logic, and sends back an appropriate response. Neither side does the other’s job. This separation keeps the system organised and lets a small device like a phone access content stored on enormous server farms.

The request and display cycle

When you enter a web address, your browser acts as the client and sends a request to the server for specific content, such as a page, image, or video. The server receives this request, finds the resource, and returns it. Your browser then reads the response and renders it into the page you see. One important detail is that this exchange is usually based on a stateless connection between the client requesting the resource and the server handling it. Stateless means the server does not remember previous requests on its own. Each request is treated as fresh and independent, which is part of why the Web scales so well to billions of users.

Information representation

Once a server sends content to your browser, that content needs to be in a format the browser understands. This is where markup languages come in. A markup language uses tags to describe the structure and meaning of a document, separating content from instructions about how to handle it.

HTML, the language of web pages

HTML stands for Hypertext Markup Language, and it is the standard for building web pages. It is a standard implemented by different browsers so that formatted pages of text and graphics appear in approximately the same way across different hardware and software platforms. This consistency is essential. It means a page written once can be viewed correctly whether the reader is on a Windows laptop, a Mac, or an Android phone. HTML tags mark up headings, paragraphs, links, images, and other elements, telling the browser what each part of the content is.

XML and structured data

XML, or Extensible Markup Language, serves a related but distinct purpose. While HTML focuses on displaying content to people, XML focuses on storing and carrying data in a structured form. HTML has a fixed set of tags, but XML lets you define your own tags to describe whatever kind of data you are working with. This makes XML useful for exchanging information between different systems and applications. In a library context, structured data formats based on XML help systems share catalogue records and other information reliably. Together, HTML and XML cover two needs: presenting documents and structuring data.

Communication protocols

For a client and server to exchange anything, they must follow the same set of rules. A protocol is exactly that, an agreed-upon language for communication. The protocol at the heart of the Web is HTTP.

What HTTP does

HTTP stands for Hypertext Transfer Protocol. It is the protocol that defines how HTTP clients and servers interact to request and deliver resources. HTTP is a request-response protocol, which fits the client-server model precisely. The client sends a request, and the server returns a response. The standards for HTTP have long been coordinated by the Internet Engineering Task Force and the World Wide Web Consortium through a series of documents called RFCs, which keep the protocol consistent across the entire Web.

The process of retrieving a web page

The steps involved in fetching a page are worth following closely. First, your browser establishes a connection to the server, typically using the underlying TCP protocol. Then the client sends an HTTP GET request to retrieve the webpage it should display. The GET method is the most common request type, used simply to ask for a resource. The server processes the request, locates the file, and sends back a response. Each response carries a status code: 200 signals success, while 404 means the requested page was not found. Your browser reads the response and displays the result. If something has been requested before, the browser may use a cached copy to load it faster.

HTTP and HTTPS

You will often see HTTPS rather than plain HTTP at the start of a web address. HTTPS is the secure version, where the communication between client and server is encrypted. This protects sensitive information such as passwords and payment details from being read by anyone intercepting the traffic. Today most websites use HTTPS as the default, and browsers warn users when a site does not.

Addressing the Web

With billions of resources scattered across countless servers, the Web needs a precise way to identify and locate each one. This is handled by identifiers known as URIs and URLs. The two terms are closely related and often confused, so it helps to separate them clearly.

Understanding the URI

URI stands for Uniform Resource Identifier. It is the broad, general term. A URI is a string of characters that identifies a physical or logical resource. Think of it as an umbrella concept. Any string that names or points to a resource is a URI. Importantly, URIs can be used to identify and differentiate various types of files and resources, including HTML and XML documents, not just web pages. This is why URIs appear inside markup files as well as in browser address bars.

Understanding the URL

URL stands for Uniform Resource Locator, and it is a specific kind of URI. The key distinction is in the names themselves. A URI identifies a resource, while a URL identifies it and tells you how to retrieve it. A URL identifies a resource by its location or by the means used to access it, rather than by a name alone. A common analogy makes this clear: a URI is like a person’s name, which identifies them, while a URL is like their full address, which tells you where to find them. Every URL is a URI, but not every URI is a URL.

The parts of a URL

A URL is made up of several components, each carrying specific information. A URL contains components such as the protocol, domain, path, and query string. The scheme or protocol, such as https, comes first and tells the browser how to access the resource. The domain identifies the server hosting it. The path points to the specific file or page on that server. A query string, when present, passes extra information such as search terms. There is also an optional fragment, marked by a hash symbol, that points to a specific section within a document so the browser scrolls that part into view. When you read a long web address, each segment is doing a precise job.

How the pieces fit together

It is worth stepping back to see the full picture. You type a URL into your browser. The browser, acting as the client, uses HTTP to send a request across the Internet. Routers forward that request through the network until it reaches the correct server. The server processes the request and sends back an HTML document as a response. Your browser receives the HTML, interprets it, and displays a finished page. Every step depends on the others, and each technology, addressing, communication, and representation, plays its assigned part. This coordinated structure is what allows a global system of independent computers to behave as one seamless library of information.

What do you think? Now that you can see the separate roles of the client, the server, the protocol, and the addressing system, which part of this architecture do you think is the most critical single point of failure? And how might the stateless nature of HTTP both help and limit the way modern websites remember who you are?

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

References
  1. https://www.scribd.com/presentation/249409366/World-wide-web-Architecture
  2. http://www.cs.unc.edu/~jbs/projects/aw/book/chapters/background/www/
  3. https://www.scribd.com/document/956515504/BNS-Report
  4. https://www.w3.org/People/Frystyk/thesis/WWW.html
  5. https://www.w3.org/Protocols/HTTP/1.0/draft-ietf-http-spec.html
  6. https://www.scribd.com/doc/299679135/Http
  7. https://www.codecademy.com/article/http-requests
  8. https://www.scribd.com/presentation/51689182/HTTP
  9. https://www.guru99.com/url-vs-uri-difference.html
  10. https://www.techtarget.com/whatis/definition/URI-Uniform-Resource-Identifier
  11. https://www.ibm.com/docs/en/SSGMCP_5.3.0/com.ibm.cics.ts.internet.doc/topics/dfhtl_uricomp.html

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

ICT Fundamentals

1 Basics of Computer Technology

  1. Overview of Computer System
  2. Computer Peripherals and Hardware
  3. Computer Peripherals
  4. Computer Hardware
  5. Operating System
  6. Ubuntu Operating System
  7. Ubuntu File System
  8. Common Commands and Utilities

2 Basic of Communication Technology

  1. Analog and Digital Communication
  2. Data Communication Modes
  3. Communication Hardware
  4. Communication Protocols/Standard

3 Basic of Network Technology

  1. Network Concept and Classification
  2. Local Area Network (LAN) Overview
  3. Wide Area Network
  4. Wireless Technology

4 Technology Convergence

  1. What is Convergence?
  2. Goal and Objectives of Convergence
  3. Genesis of Convergence
  4. Convergence Focus
  5. Convergence Architecture
  6. Technology Convergence
  7. Bluetooth Technology
  8. 3G and WiMAX Technologies
  9. Protocol Convergence
  10. Access Convergence
  11. Service Convergence
  12. Convergent Applications

5 Office Tools- Word Processing, Presentation and Spreadsheets

  1. Getting Started with LibreOffice Suite
  2. Word Processing with Writer
  3. Presentations with LibreOffice Impress
  4. Spreadsheets with LibreOffice Calc

6 Database Management systems

  1. File Oriented Approach
  2. Database Approach
  3. Database and DBMS
  4. Levels of Abstraction in a DBMS
  5. Database Environment
  6. Various DBMS Architectures
  7. Types of DBMS Architectures
  8. Database Security
  9. Popular DBMS Packages
  10. Database Project Environment
  11. Database Administrator

7 Multimedia

  1. Multimedia
  2. Characteristics of Multimedia Systems
  3. Types of Media
  4. Print vs Multimedia
  5. Major Areas of Multimedia Use
  6. Advances in Technology
  7. Multimedia Design
  8. Software in Multimedia Systems
  9. Information Collection in Multimedia Systems
  10. Storyboard for Multimedia Systems
  11. Processing in Multimedia Systems
  12. Storing and Retrieving in Multimedia Systems
  13. Issues Related to Multimedia Systems
  14. Data Integrity in Multimedia Systems
  15. Career Path in Multimedia

8 Network Topology

  1. Physical and Logical Topologies
  2. Fully Connected Topology
  3. Star Topology
  4. Hubs and Switches
  5. Bus Topology
  6. Ring Topology
  7. Mesh Topology
  8. Tree Topology
  9. Hybrid Topology
  10. Media Access Control Protocols
  11. Address Resolution
  12. Routers
  13. Routing Algorithms

9 Communication Protocols and Network Addressing

  1. What are Protocols?
  2. Computing Protocols
  3. Communication Protocols: General Concepts
  4. Common Communication Protocols
  5. Basic Communication Protocols: IP, UDP, TCP
  6. Client-Server Architecture
  7. Application Level Communication Protocols: FTP, Telnet
  8. Switching Level Convergence Protocol: ATM
  9. Multi Protocol Label Switching: MPLS
  10. Telephone and Mobile Numbering
  11. Number Portability
  12. IP Addressing: IPv4, IPv6
  13. Web Communication Protocols: HTTP, WAP, LTP

10 Protocol Architecture

  1. Protocol Architecture and Protocol Stack
  2. Layered Architecture
  3. Principles of Layering
  4. ISO-OSI Reference Model
  5. Internet Protocol Architecture: TCP/IP Architecture
  6. Bluetooth Protocol Stack
  7. ISDN Reference Model
  8. ATM Protocol Stack
  9. SONET Hierarchy
  10. Mobile Network Protocol Architecture

11 Network Applications and Management

  1. Service and Application Types
  2. Electronic Text Messaging
  3. Multimedia Messaging
  4. Electronic Mail
  5. Interactive Television (ITV)
  6. Interactive Music (IM)
  7. Application Delivery
  8. Performance Issues
  9. Why Network Management?
  10. Simple Network Management Protocol (SNMP)

12 Network Security

  1. Why Information Security?
  2. Types of Attacks
  3. AAA Security
  4. Firewalls and Proxy Servers
  5. Web Security
  6. Malicious Software
  7. Viruses
  8. Spyware, Spam, Phishing and Cookies
  9. Encryption
  10. Digital Signature
  11. E-mail Security

13 E-Mail and E-Messaging

  1. Defining Email
  2. Need of Email
  3. Email Address
  4. Types of Email Services
  5. Types of Email Account
  6. Structure and Features of Email
  7. Functioning of Email Systems
  8. Messaging
  9. Issues with Messaging
  10. Widgets and Utilities

14 World Wide Web

  1. World Wide Web
  2. Conceptual Framework of WWW
  3. Communication Architecture
  4. Protocols
  5. Markup Languages
  6. Definition and Need (Markup Languages)
  7. Types of Markup Languages
  8. Web 2.0
  9. Features of Web 2.0 Applications
  10. Web 2.0 Applications
  11. Impact of Web 2.0 Tools Over WWW and Semantic Web

15 Search Engines

  1. Search Engines
  2. Types of Search Tools
  3. Features of Search Tools
  4. Architecture of Search Tools
  5. Challenges

16 Interactive and Distributive Services

  1. Web Directory
  2. Bulletin Board
  3. Mailing List and Discussion Lists
  4. Resource Sharing
  5. Online Document Repositories
  6. Web Portals
  7. E-mail
  8. Online Storage and Searching
  9. E-publishing
  10. Webcasting
  11. Interactive Learning
  12. Interactive Business and Trading
  13. Security and Privacy Issues