Skip to topic
    ← Back to course topics

    Client server model — AQA A-Level Computer Science

    The client-server model is a distributed network architecture where client devices send requests for services, data, or processing to a centralised server, which processes these requests and returns responses. This fundamental paradigm underpins modern web services, enterprise databases, and email protocols, providing central control over security, backup management, and shared digital resources.

    Client server model explained

    The client server model is a network architecture in which a central server provides services or resources, and many client devices request and use them.

    Read the full explanation

    Clients initiate communication by sending a request, usually over a network such as the internet, and the server processes that request and returns a response. Typical examples include web browsers requesting pages from a web server, email clients retrieving messages from a mail server, and mobile apps fetching data from a back-end database. The server is usually always running and reachable at a known address, while clients may connect and disconnect as needed. This arrangement allows data and processing to be centralised, which simplifies updates, security and backup, though it creates dependence on the server's availability and capacity.

    Your focus

    1. Be familiar with the client server model.

    Which command word is this?

    Set out the operational sequence or reasons behind a mechanism using cause-and-effect language (e.g., 'Because the client sends a request to port 80, the web server initiates a thread...').

    Client server model exam tips

    Topic Overview

    The client-server model is an architectural pattern that divides workloads between service requesters (clients) and service providers (servers). It represents a fundamental building block of modern networked computing, governing protocols such as HTTP, DNS, FTP, and SMTP.

    Understanding this topic allows students to analyse how software systems interact across networks, evaluate security and performance trade-offs, and compare centralised network paradigms against decentralised models like peer-to-peer (P2P).

    Key Concepts
    • →Role delineation: Clients initiate requests for services or resources, while servers listen passively on specific ports, process requests concurrently, and return responses.
    • →Centralisation: Management of data integrity, user authentication, access permissions, and backups is concentrated on the server, simplifying governance.
    • →Single point of failure and bottlenecking: Because all traffic routes through the server, excessive traffic can cause denial of service or network degradation, and server downtime halts all client operations.
    • →Client-side vs server-side processing: Workloads can be partitioned; client-side processes handle presentation and input validation, while server-side scripts execute database access and business logic.
    • →Thin-client vs thick-client: Thin clients rely almost entirely on the server for storage and computational processing, whereas thick (fat) clients run applications locally and use the server primarily for storage.
    Marking Points
    • Identifies the server as the provider of a service or resource and the clients as requesters.
    • Explains that the client initiates the request and the server responds to it.
    • Describes typical examples such as web browsing, email or database access.
    • Notes the advantages of centralised data, management and security.
    • Notes the disadvantages such as a single point of failure and dependence on server capacity.
    Examiner Tips
    • 💡Use the terms client and server precisely and describe the direction of each request and response.
    • 💡Give a concrete example such as a web server answering browser requests to show understanding.
    • 💡When asked for advantages or disadvantages, link each point to centralisation of data or dependence on the server.
    • 💡Use precise technical terms such as 'request-response cycle', 'single point of failure', 'concurrency', and 'access control list' to secure full marks in descriptive questions.
    • 💡When asked to compare client-server with peer-to-peer, structure your response by contrasting specific attributes side-by-side: data storage, administration, network traffic, and fault tolerance.
    Common Mistakes
    • Describes the server as the device that always starts the communication; the client normally initiates requests. Correct this by stating that the client sends the request.
    • Confuses client server with peer-to-peer networking, where devices share resources equally. Correct this by stating that the roles are fixed in client server.
    • Treats the client as always a powerful machine; clients can be simple devices such as phones or thin terminals. Correct this by describing the client as any device that requests a service.
    • Believing that a server must always be a separate, dedicated physical machine: in reality, server refers to an application or process that listens on a port (a single physical computer can run both client and server software simultaneously, e.g., localhost).
    • Assuming client-server systems are inherently faster than peer-to-peer networks: while central servers often have superior hardware, high concurrent client requests create queueing delays, whereas P2P bandwidth scales with user participation.
    Revision Plan
    1. 1Step 1: Solidify basic definitions of client, server, request-response cycle, thin-client, and thick-client models.
    2. 2Step 2: Map out real-world application examples (web browsing, database access, online gaming) and distinguish between client-side and server-side operations.
    3. 3Step 3: Create a direct comparison matrix between client-server and peer-to-peer architectures across security, cost, administration, and scalability.
    4. 4Step 4: Practise past AQA 6-mark evaluate and compare questions under timed conditions, using explicit mark scheme keywords.
    Exam Question Types
    • 📋Short definition and distinction questions (e.g., distinguishing between thin-client and thick-client approaches or client vs server roles).
    • 📋Scenario-based structured questions evaluating whether a business should implement client-server or peer-to-peer architecture.
    • 📋Process tracing questions explaining the step-by-step exchange of messages between client and server (e.g., DNS lookup or HTTP request handling).
    Command Word Expectations (AQA)
    Explain

    Set out the operational sequence or reasons behind a mechanism using cause-and-effect language (e.g., 'Because the client sends a request to port 80, the web server initiates a thread...').

    Evaluate

    Weigh both the strengths and limitations of the architecture in context of a given scenario, culminating in a justified conclusion or recommendation.

    Compare

    Directly juxtapose client-server systems with alternative models (usually P2P), explicitly matching corresponding features like security, performance, and maintenance.

    How Students Lose Marks (Examiner Pitfalls)
    Pitfall: Confusing the role of a server as physical hardware rather than software providing a service across a network socket.
    ❌ Weak Answer (Loses Marks):A server is a big, powerful computer in a data centre that stores all the files, and clients are normal laptops that connect to it.
    Example improved answer:A server is a software process (or dedicated system) running on a host that manages shared resources and listens for incoming service requests from clients, while a client is a process that initiates communication by requesting services or data from the server across a network interface.
    Examiner Tip: Always define clients and servers primarily in terms of their roles in communication (initiator vs listener/provider) rather than their physical hardware specifications.
    Pitfall: Failing to evaluate the architectural trade-offs between client-server and peer-to-peer (P2P) systems, especially regarding bottlenecks and single points of failure.
    ❌ Weak Answer (Loses Marks):Client-server networks are better because they are more secure and easier to manage, whereas P2P is messy and used for illegal torrenting.
    Example improved answer:In a client-server network, centralisation allows for streamlined data backups, access control, and user authentication; however, the central server acts as a single point of failure and a potential performance bottleneck during periods of high demand. In contrast, P2P networks distribute traffic load across all participating nodes and maintain resilience if individual peers disconnect.
    Examiner Tip: In comparison questions, explicitly link architectural features (e.g., central repository vs distributed nodes) directly to performance, scalability, and security impacts.
    Step-by-Step Worked Solutions

    Question: A multinational retail company currently uses a peer-to-peer network across its regional sales offices. The company plans to migrate to a client-server architecture with a centralised database server at headquarters. Discuss the advantages and disadvantages of this migration for the company. (6 marks)

    1. 1.Step 1: Identify advantages of centralised management. Centralising data ensures data consistency, transactional integrity (ACID properties), and automated scheduled backups from a single location without relying on distributed user machines.
    2. 2.Step 2: Identify security and administrative benefits. Access control lists, user permissions, and auditing can be administered globally by IT staff rather than configured on individual endpoints.
    3. 3.Step 3: Identify operational disadvantages and risks. The central server becomes a single point of failure; if the server or wide-area network connection fails, offices cannot access records. Additionally, bandwidth bottlenecks may occur as concurrent client requests increase.
    4. 4.Step 4: Formulate a balanced conclusion based on the scenario requirements for retail inventory and transaction management.
    Final Answer: Advantages include simplified, centralised database backups, guaranteed data consistency for stock levels across all offices, and centralised security/access privileges. Disadvantages include the high cost of enterprise-grade server infrastructure and specialist staff, network bottlenecks when many remote clients query simultaneously, and complete operational paralysis if the central server or connection fails (single point of failure).

    Question: Explain the sequence of network operations when a web browser (client) retrieves an HTML page from a remote web server over HTTP. (4 marks)

    1. 1.Step 1: Describe the initial address resolution where the client queries a DNS server to resolve the Uniform Resource Locator (URL) domain name into an IP address.
    2. 2.Step 2: Describe the transport layer connection establishment (TCP three-way handshake: SYN, SYN-ACK, ACK) on port 80 or 443.
    3. 3.Step 3: Detail the application layer request, where the client sends an HTTP GET request message across the established socket.
    4. 4.Step 4: Detail the server processing and response, where the server parses the request, retrieves the requested file, and transmits an HTTP response containing a status code (e.g., 200 OK) and the HTML payload before closing or persisting the connection.
    Final Answer: 1. Client resolves the host domain name to an IP address using DNS. 2. Client initiates a TCP three-way handshake with the server on port 80/443. 3. Client issues an HTTP GET request for the specific resource. 4. Server processes the request and returns an HTTP response containing header metadata, status code (e.g., 200 OK), and the HTML body.
    Active Recall Memory Test
    What role does a client take in the client-server request-response lifecycle?
    Key Fact: The client acts as the initiating agent that sends a request for resources, computation, or data across the network to a listening server.
    Identify two distinct advantages of a client-server architecture over a peer-to-peer architecture.
    Key Fact: Centralised management of data backups and global implementation of user security permissions/access controls.
    What is the primary difference between a thin client and a thick (fat) client?
    Key Fact: A thin client relies on the server to execute applications and handle processing, whereas a thick client processes applications and business logic locally using its own CPU and memory.
    What major structural risk exists at the server node in a non-redundant client-server network?
    Key Fact: It represents a single point of failure; if the server hardware or network connection crashes, all dependent clients lose service access.
    Frequently Asked Questions
    Can a single computer be both a client and a server at the same time?
    Yes. Client and server are logical roles defined by software, not hardware types. A machine running a local web development environment (such as an Apache or Node.js server) can run a web browser client that connects to itself via the loopback address (127.0.0.1 or localhost).
    What is the difference between client-side and server-side processing?
    Client-side processing occurs on the user device (typically inside a browser using JavaScript) for tasks like user interface rendering, form validation, and animations. Server-side processing occurs on the remote server (using languages like Python, PHP, or Java) to handle database queries, business logic, sensitive authentication, and heavy computation.
    Why would an organisation choose a thin-client setup over thick clients?
    Organisations like schools or call centres choose thin clients because they drastically reduce hardware acquisition costs, lower power consumption, and eliminate the need to maintain software on individual workstations. Security is also enhanced because sensitive data cannot be stored locally on client endpoints.
    Is the internet a client-server network or a peer-to-peer network?
    The internet is a global network of interconnected networks that supports multiple models simultaneously. The vast majority of standard web services, such as websites (HTTP), email (IMAP/SMTP), and name resolution (DNS), operate strictly on the client-server model, though decentralized P2P protocols (such as BitTorrent) also run on top of the underlying internet protocol suite.
    How do modern high-traffic systems overcome the single point of failure in client-server architecture?
    Modern networks implement redundancy through load balancers, server clusters, and distributed content delivery networks (CDNs). A load balancer distributes incoming client requests across multiple physical or virtual servers, ensuring that if one server fails, other servers in the cluster handle the workload without service interruption.