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
- Components of the Web
- Personal computers and devices
- Web browsers
- Internet connections
- Servers
- Routers
- Client-server architecture
- How the two roles divide the work
- The request and display cycle
- Information representation
- HTML, the language of web pages
- XML and structured data
- Communication protocols
- What HTTP does
- The process of retrieving a web page
- HTTP and HTTPS
- Addressing the Web
- Understanding the URI
- Understanding the URL
- The parts of a URL
- How the pieces fit together
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?
References
- https://www.scribd.com/presentation/249409366/World-wide-web-Architecture
- http://www.cs.unc.edu/~jbs/projects/aw/book/chapters/background/www/
- https://www.scribd.com/document/956515504/BNS-Report
- https://www.w3.org/People/Frystyk/thesis/WWW.html
- https://www.w3.org/Protocols/HTTP/1.0/draft-ietf-http-spec.html
- https://www.scribd.com/doc/299679135/Http
- https://www.codecademy.com/article/http-requests
- https://www.scribd.com/presentation/51689182/HTTP
- https://www.guru99.com/url-vs-uri-difference.html
- https://www.techtarget.com/whatis/definition/URI-Uniform-Resource-Identifier
- https://www.ibm.com/docs/en/SSGMCP_5.3.0/com.ibm.cics.ts.internet.doc/topics/dfhtl_uricomp.html

Leave a Reply