Client-Server vs Peer-to-Peer - GCSE Computer Science

The Idea

How Are Networks Organised?

Once you have devices connected together in a network, a crucial question arises: how do those devices interact with each other? Who is in charge? Does one powerful computer run everything, or does every device share the workload equally?

The answer to this question defines the network model — the fundamental architecture that determines how devices communicate, share resources, and are managed. There are two main models you need to know for GCSE Computer Science:

Client-Server — one or more dedicated, powerful computers (servers) provide services, and all other devices (clients) request those services.
Peer-to-Peer (P2P) — all devices are equal. There is no dedicated server. Every device can both provide and request resources from any other device on the network.

These two models lead to very different networks with different strengths, weaknesses, and use cases. Understanding the differences between them — and knowing when each model is appropriate — is a key exam topic.

Did You Know? The original internet (ARPANET) in the 1960s was designed with a peer-to-peer philosophy — every connected computer was equal and could communicate directly with every other. As the internet grew, the client-server model became dominant for most services. However, P2P made a dramatic comeback in the early 2000s with file-sharing applications like Napster and BitTorrent, and more recently with blockchain technologies like Bitcoin, which relies entirely on a P2P network with no central server.

Explore

The Client-Server Model

In a client-server network, there is a clear division of roles. One or more powerful, dedicated computers called servers sit at the centre of the network, providing services and resources. All other devices on the network are called clients. Clients send requests to the server, and the server processes those requests and sends back a response.

Think of it like a restaurant. The server is the kitchen — it prepares and delivers everything. The clients are the customers — they place orders and receive their food. Customers do not cook for themselves or serve each other; everything goes through the kitchen.

What Does the Server Do?

A server is a powerful, dedicated computer designed to handle many requests simultaneously. It typically has:

High RAM (e.g. 64 GB, 128 GB, or more) — to handle many simultaneous connections and processes
Fast, multi-core CPU (e.g. Intel Xeon or AMD EPYC processors) — to process requests quickly
Large storage capacity (often multiple hard drives in a RAID configuration) — to store all shared files, databases, and user data
Redundant power supplies and cooling — to ensure the server runs 24/7 without downtime

A server can provide many different types of services:

File server: Stores and manages shared files. Users save their work to the server rather than their local computer. Example: a school file server where students access their coursework from any PC in the building.
Print server: Manages print jobs from multiple clients and sends them to shared printers. Users on any client computer can send documents to a network printer.
Email server: Sends, receives, and stores email messages. When you send an email, your client (e.g. Outlook or Gmail) communicates with an email server that routes the message to the recipient.
Web server: Hosts websites and web applications. When you type a URL into your browser, your computer (the client) sends a request to a web server, which sends back the web page.
Database server: Stores and manages large databases. Applications on client computers query the database server to retrieve or update data. Example: a hospital patient records system.
Authentication server: Manages user accounts, passwords, and access permissions. When you log in to a school computer, the authentication server checks your username and password.

How the Client-Server Model Works (Step by Step)

Here is what happens when a student at school opens a file from the shared drive:

The student (client) double-clicks a file on the network drive.
The client computer sends a request to the file server: “Please send me the file called homework.docx.”
The server receives the request, checks the student has permission to access the file, locates it on its hard drive, and sends the file data back to the client as a response.
The client computer receives the data and opens the file for the student to view and edit.
When the student saves the file, the client sends the updated data back to the server for storage.

Real-World Examples of Client-Server Networks

School network: A dedicated file server stores student work, an authentication server manages logins, and a print server manages printing. Student computers are clients that access these services.
Email (Gmail, Outlook): Google and Microsoft run massive email servers. Your phone or browser is the client that connects to these servers to send and receive email.
Web browsing: Every website you visit is hosted on a web server. Your browser is the client. When you visit google.com, your browser sends a request to Google’s web server, which responds with the search page.
Online banking: Your banking app or browser (client) connects to the bank’s secure servers, which store your account details and process transactions.
Online gaming (e.g. Fortnite, Minecraft multiplayer servers): A central game server manages the game world and communicates with all player clients.
Streaming services (Netflix, Spotify): Content is stored on media servers and streamed to your device (the client) on demand.

Advantages of Client-Server

Centralised security: The server controls who can access what. User permissions, passwords, and access levels are all managed in one place. This makes it much easier to enforce security policies.
Centralised backups: Because all data is stored on the server, it can be backed up automatically and regularly. If a client computer breaks, no data is lost — everything is safe on the server.
Centralised management: Software updates, security patches, and settings can be pushed out from the server to all clients. The network administrator can manage everything from one location.
User accounts: Each user has their own account with a username and password, stored on the server. Users can log in to any client computer on the network and access their own files and settings.
Performance: Servers are powerful machines designed to handle large workloads efficiently. They can process requests from hundreds or thousands of clients simultaneously.
Scalability: New client devices can be added to the network easily without reconfiguring every other device. The server handles the complexity.

Disadvantages of Client-Server

Expensive hardware: Servers are costly to purchase. A dedicated server with high-end components can cost thousands of pounds. Enterprise-grade servers can cost tens of thousands.
Specialist staff: Someone needs to set up, configure, maintain, and troubleshoot the server. This typically requires a trained network administrator or IT technician, which is an ongoing cost.
Single point of failure: If the server goes down, all clients lose access to the services it provides. No server means no shared files, no printing, no email — potentially bringing the entire organisation to a halt until the server is repaired or replaced.
Software licences: Server operating systems and management software often require expensive licences (e.g. Windows Server, Microsoft Exchange).

Key Concept: Client-Server In a client-server network, one or more dedicated servers provide services (files, print, email, web, database, authentication) and clients request those services. Servers are powerful machines with high RAM, fast CPUs, and large storage. This model offers centralised security, backups, and management, but the server is expensive, requires specialist staff, and is a single point of failure.

Common Mistake: Students sometimes write that a client-server network has “one server.” In reality, many client-server networks have multiple servers — one for files, one for email, one for the database, and so on. Some organisations even have backup servers to avoid a single point of failure. In your exam, say “one or more dedicated servers” for accuracy.

Explore

The Peer-to-Peer (P2P) Model

In a peer-to-peer network, there is no dedicated server. All devices on the network are equal — each one is called a peer (or sometimes a node). Every peer can act as both a client and a server. This means any device can share its own files and resources with others, and also access files and resources shared by other peers.

Think of it like a group of friends sharing food at a picnic. There is no waiter and no kitchen. Everyone brings their own food and shares it directly with each other. Anyone can offer food, and anyone can take food from the shared spread.

How P2P Works

In a P2P network:

Each device stores its own files locally.
If Device A wants a file that Device B has, it requests it directly from Device B — not from a central server.
Any device can share resources (files, printers, an internet connection) with any other device on the network.
There is no central point of control, no central file storage, and no central management.

Real-World Examples of P2P Networks

Small home network: If you share a folder from your laptop so that your family’s desktop computer can access it, you have set up a simple P2P arrangement. Neither computer is a dedicated server — they are equals sharing resources.
BitTorrent (file sharing): When you download a file using BitTorrent, you are not downloading from one central server. Instead, you download small pieces of the file from many different peers simultaneously. Each peer that has part of the file shares it with others. This is why torrents can be very fast — the more peers sharing, the faster the download.
Bitcoin and cryptocurrency: The Bitcoin network is a massive P2P network. Every node in the network has a copy of the blockchain (a record of all transactions). There is no central bank or server controlling Bitcoin — transactions are verified and recorded by the network of peers collectively.
Skype (original architecture): The early versions of Skype used P2P technology for voice and video calls. Your call was routed through other Skype users’ computers rather than a central server.
Ad-hoc wireless networks: Two phones sharing files directly via Wi-Fi Direct or AirDrop operate in a P2P fashion — neither device acts as a dedicated server.

Advantages of Peer-to-Peer

Cheap to set up: No expensive, dedicated server hardware is required. You just connect ordinary computers together. This makes P2P ideal for small networks where budget is limited.
Easy to set up: P2P networks require minimal technical knowledge. Most operating systems (Windows, macOS) have built-in file sharing that allows you to create a P2P network in minutes without specialist staff.
No single point of failure: Because there is no central server, the failure of one device does not bring down the whole network. Other peers can continue communicating and sharing resources. If one peer goes offline, you can still access files stored on other peers.
No dependency on a server: Peers can function independently. If one device breaks, the others are unaffected (apart from losing access to whatever that specific device was sharing).
Scalable for sharing: In P2P file-sharing systems like BitTorrent, performance can actually improve as more peers join, because there are more sources to download from.

Disadvantages of Peer-to-Peer

Less secure: There is no centralised security management. Each user is responsible for the security of their own device. There are no centrally enforced passwords, access controls, or security policies. This makes P2P networks more vulnerable to unauthorised access and malware.
Harder to back up: Data is spread across many different devices rather than stored centrally. There is no automatic, centralised backup system. If a peer’s hard drive fails, any files stored only on that device are lost.
Harder to manage: With no central administration point, managing the network is difficult. Software updates, security patches, and user accounts must be configured on each individual device.
Slower as the network grows: As more peers join a basic P2P network, devices that are sharing files must handle more and more requests. Since these are ordinary computers (not powerful servers), they can become overloaded. Performance degrades because each device is both using resources and providing resources to others.
No central user accounts: Users cannot log in from any device and access their files. Files and settings are tied to individual machines.
Availability depends on peers being online: If the only peer that has a particular file switches off, that file becomes unavailable to everyone else.

Key Concept: Peer-to-Peer In a P2P network, all devices are equal — there is no dedicated server. Every peer can share and access resources. P2P is cheap, easy to set up, and has no single point of failure. However, it is less secure, harder to manage and back up, and can become slower as the network grows. Common examples include home file sharing, BitTorrent, and Bitcoin.

Common Mistake: Students sometimes think P2P networks are always illegal or only used for piracy. This is incorrect. P2P is a perfectly legal network architecture. BitTorrent is used legally to distribute Linux operating systems, game updates, and open-source software. Bitcoin’s entire financial system runs on P2P. It is the content being shared that may or may not be legal, not the technology itself.

Understand

Comparing Client-Server and Peer-to-Peer

Side-by-Side Comparison Table

This table is essential for your GCSE exam. You may be asked to compare the two models across several features. Memorise the key differences.

Feature	Client-Server	Peer-to-Peer (P2P)
Cost	Expensive — requires dedicated server hardware and software licences	Cheap — no dedicated server needed; uses ordinary computers
Security	Strong — centralised user accounts, passwords, permissions, and security policies managed from the server	Weak — no centralised security; each user manages their own device’s security independently
Management	Easy to manage centrally — software updates, backups, and user accounts can be pushed from the server	Difficult — each device must be configured individually; no central administration
Backups	Centralised — all data is on the server and can be backed up automatically	Difficult — data is spread across many devices; no automatic central backup
Reliability	Server is a single point of failure — if it crashes, all clients lose access to services	No single point of failure — if one peer goes down, others continue working
Performance	Good — dedicated servers are powerful and designed to handle many requests	Can degrade as the network grows — ordinary computers must handle both their own work and serve requests from other peers
Setup difficulty	Complex — requires specialist knowledge to configure servers, user accounts, and permissions	Simple — most operating systems support P2P file sharing out of the box with minimal configuration
Specialist staff	Needed — a network administrator is required to manage the server and network	Not needed — ordinary users can set up and maintain a P2P network
Best suited for	Large organisations: schools, businesses, banks, hospitals	Small networks: homes, small offices, file sharing, cryptocurrency
Examples	School network, email (Gmail), web browsing, online banking, Netflix	Home file sharing, BitTorrent, Bitcoin, ad-hoc wireless sharing

When to Use Each Model

The right model depends on the size of the network, the budget, the security requirements, and the management needs of the organisation.

Use Client-Server when:

The network has many users (e.g. more than 10–15 devices)
Security is important (sensitive data, user accounts, access control)
Centralised management and backups are needed
Users need to access their files from any computer on the network
The organisation can afford server hardware and specialist staff
Services like email, databases, or web hosting are required

Use Peer-to-Peer when:

The network is small (e.g. fewer than 10 devices)
Budget is limited and a server cannot be justified
Security is not a major concern
Users only need to share occasional files or a printer
There is no IT staff available to manage a server
Decentralisation is needed (e.g. cryptocurrency, distributed file sharing)

Exam Tip: Scenario Questions In the exam, you may be given a scenario describing an organisation and asked to recommend a network model. Look for clues: large number of users, security requirements, and centralised management point to client-server. Small number of devices, limited budget, and simple sharing needs point to peer-to-peer. Always justify your recommendation by explaining why it is appropriate.

Exam Tip: Use the Correct Terminology When writing about client-server, use terms like “dedicated server,” “centralised,” “user accounts,” and “single point of failure.” When writing about P2P, use terms like “equal peers,” “no dedicated server,” “decentralised,” and “share and access resources.” Precise technical language earns marks.

Common Mistake: Students sometimes write that P2P “has no network” or “devices are not connected.” This is wrong. A P2P network is still a network — the devices are connected and communicate with each other. The difference is that there is no dedicated server, not that there is no connection. Peers are connected and actively share resources with each other.

Common Mistake: Another frequent error is saying that client-server networks “never fail” because they have a powerful server. In fact, the server being a single point of failure is one of the biggest disadvantages of client-server. If the server goes down, the entire network may be unusable. This is a critical point to remember.

Interactive

Test Your Knowledge

Try these interactive exercises to check your understanding of client-server and peer-to-peer networks. Read each scenario or statement carefully and select the correct answer.

Exercise 1: Client-Server or P2P?

Read the scenario below and decide whether it describes a Client-Server or Peer-to-Peer network.

Score: 0 / 0

Exercise 2: Advantages & Disadvantages Sorter

Read the advantage or disadvantage below and decide whether it applies to Client-Server or Peer-to-Peer.

Score: 0 / 0

Practice

Practice Questions

Click on each question to reveal the answer. Try to answer in your head or on paper first before checking!

Q1: What is the difference between a client-server and a peer-to-peer network?

Answer: In a client-server network, one or more dedicated servers provide services (such as file storage, email, printing, and authentication) and client devices request those services. The server is a powerful, centralised machine that manages security, backups, and user accounts. In a peer-to-peer (P2P) network, there is no dedicated server. All devices are equal and can both share and access resources from each other. Each peer acts as both a client and a server. Client-server is typically used in large organisations where centralised management and security are important, while P2P is suited to small, informal networks where cost and simplicity are priorities.

Q2: Give two advantages and two disadvantages of the client-server model.

Answer: Advantages: (1) Centralised security — the server controls user accounts, passwords, and access permissions centrally, making it easier to enforce security policies across the whole network. (2) Centralised backups — because all data is stored on the server, it can be backed up automatically; if a client computer fails, no data is lost. Disadvantages: (1) Expensive — dedicated server hardware costs thousands of pounds, and server operating systems and software often require expensive licences. (2) Single point of failure — if the server crashes or goes offline, all client devices lose access to the services it provides, which can bring the entire organisation to a halt.

Q3: Explain why a peer-to-peer network might be suitable for a small home network but not for a large school.

Answer: A P2P network is suitable for a small home network because: there are only a few devices (perhaps 3–5), so there is no need for a powerful dedicated server; the family likely cannot justify the expense of server hardware and an IT technician; and basic file and printer sharing between a few devices is all that is needed. However, a P2P network would not be suitable for a large school because: (1) a school has hundreds of computers and users, requiring centralised user accounts so students can log in to any machine; (2) student work must be backed up centrally to prevent data loss; (3) the school needs strong, centrally managed security to protect sensitive data and control internet access; (4) without a dedicated server, performance would degrade badly with hundreds of devices all making requests of each other. A client-server model is far more appropriate for a school.

Q4: A small start-up company has 5 employees and a limited budget. They need to share files and a printer. Would you recommend a client-server or peer-to-peer network? Justify your answer.

Answer: I would recommend a peer-to-peer network. With only 5 employees, the network is small enough that a dedicated server is not necessary. A P2P network would be much cheaper because no expensive server hardware or server software licences are needed. It is also easy to set up — modern operating systems like Windows and macOS have built-in file and printer sharing, so the company does not need to hire specialist IT staff. Each employee can share their files and access the shared printer directly. The main trade-off is that security is not centralised and backups would need to be done individually, but for 5 users with a limited budget, P2P is the most cost-effective and practical choice.

Q5: Explain how BitTorrent demonstrates the peer-to-peer model in action.

Answer: BitTorrent is a P2P file-sharing protocol. When a file is shared via BitTorrent, it is split into many small pieces. Instead of downloading the entire file from one central server, a user (peer) downloads different pieces from many different peers simultaneously. Each peer that has already downloaded some pieces also uploads (shares) those pieces with other peers who need them. This means every device acts as both a client (downloading pieces it needs) and a server (uploading pieces it has). There is no single central server hosting the file. This demonstrates the P2P model because: all devices are equal; there is no dedicated server; resources (file pieces) are shared directly between peers; and the more peers that join, the more sources there are to download from, which can actually make downloads faster.

Q6: A hospital needs a network to store patient records, manage appointments, and allow staff to access information from any workstation. Explain why a client-server network is essential for this scenario.

Answer: A client-server network is essential for a hospital because: (1) Centralised security — patient records contain extremely sensitive personal data protected by law (e.g. the Data Protection Act). A server can enforce strict access controls, ensuring only authorised staff (doctors, nurses) can view specific records. This level of security is impossible to achieve with P2P. (2) Centralised backups — losing patient data could be life-threatening. A server ensures all records are backed up automatically and regularly. (3) Central data storage — doctors and nurses need to access up-to-date patient records from any workstation in the hospital. A central database server makes this possible. (4) Reliability and performance — a hospital has many workstations used by many staff. A powerful dedicated server can handle this demand efficiently. (5) User accounts — staff need individual logins with different access levels (e.g. a receptionist should see appointment data but not detailed medical notes). A client-server setup is the only model that provides the security, reliability, and centralised management a hospital requires.

Q7: State what is meant by a “single point of failure” in the context of client-server networks.

Answer: A single point of failure is a component in a system whose failure causes the entire system to stop working. In a client-server network, the server is the single point of failure. If the server crashes, loses power, or is damaged, all client devices lose access to the services it provides — files cannot be accessed, emails cannot be sent or received, printing may stop, and users may not be able to log in. The entire network effectively becomes unusable until the server is repaired or replaced. This is a significant disadvantage of the client-server model. Some organisations mitigate this risk by using redundant (backup) servers that can take over if the main server fails.

Q8: Compare client-server and peer-to-peer networks in terms of cost, security, and management. [6-mark style question]

Answer: Cost: Client-server networks are more expensive because they require dedicated server hardware (high RAM, fast CPU, large storage), server operating system licences, and ongoing costs for specialist IT staff to manage the server. Peer-to-peer networks are much cheaper because they use ordinary computers with no dedicated server — there are no server hardware costs and no specialist staff costs. Security: Client-server networks provide stronger security because user accounts, passwords, and access permissions are managed centrally on the server. The administrator can enforce security policies across the entire network from one location. In a P2P network, there is no centralised security — each user is responsible for their own device’s security, making it much harder to enforce consistent policies and more vulnerable to unauthorised access. Management: Client-server networks are easier to manage centrally. Software updates, security patches, backups, and user accounts can all be managed from the server, saving time. In a P2P network, each device must be configured, updated, and backed up individually because there is no central administration point — this becomes increasingly impractical as the network grows. In summary, client-server offers superior security and management at higher cost, while P2P offers simplicity and low cost at the expense of security and central control.

Reference

Key Vocabulary

This table summarises the essential terms for this topic. Use it for revision and to check your understanding.

Term	Definition
Client	A device on a network that requests services or resources from a server (e.g. a student’s workstation, a web browser, a phone running an email app)
Server	A powerful, dedicated computer that provides services (files, email, web pages, database access, printing, authentication) to client devices on a network
Client-Server network	A network model where dedicated servers provide centralised services and clients request those services
Peer-to-Peer (P2P) network	A network model where all devices are equal (peers) with no dedicated server; each device can both share and access resources
Peer / Node	An individual device in a P2P network that can act as both a client and a server
Centralised	Managed or controlled from a single, central point (e.g. a server managing all user accounts and backups)
Decentralised	Distributed across many points with no single central authority (e.g. a P2P network where data is spread across all peers)
Single point of failure	A component whose failure causes the entire system to stop working; in client-server, the server is the single point of failure
File server	A server that stores and manages shared files, allowing users to save and access documents from any client on the network
Web server	A server that hosts websites and responds to requests from web browsers (clients)
Database server	A server that stores and manages databases, responding to queries from client applications
Authentication	The process of verifying a user’s identity, typically by checking a username and password against records stored on a server
BitTorrent	A P2P file-sharing protocol where files are split into pieces and downloaded from many peers simultaneously
Blockchain	A decentralised, distributed ledger used in P2P cryptocurrency networks like Bitcoin to record transactions across many peers
Redundancy	Having backup systems or components (e.g. a backup server) so that if one fails, another can take over

Exam Tips

How to Succeed in the Exam

Exam Tip: Know the Key Differences You must be able to clearly distinguish between client-server and peer-to-peer. The six most important comparison points are: cost, security, management, backups, reliability (single point of failure), and performance. If you can confidently discuss all six, you can answer virtually any comparison question on this topic.

Exam Tip: Always Give Examples When describing either model, include real-world examples. For client-server: school networks, email systems, web browsing, online banking. For P2P: home file sharing, BitTorrent, Bitcoin. Examples demonstrate understanding and earn additional marks.

Exam Tip: Recommend and Justify If asked to recommend a network model for a scenario, state your recommendation clearly and then give at least two reasons why. For example: “I recommend a client-server network because the organisation has 200 employees who need centralised user accounts, and the sensitive customer data requires strong, centrally managed security.”

Exam Tip: Do Not Confuse Models with Topologies Client-server and peer-to-peer are network models (how devices interact). Star, bus, and mesh are network topologies (how devices are physically or logically connected). A client-server network often uses a star topology, but they are different concepts. Do not mix them up.

Exam Practice

Past Paper Questions

Try these exam-style questions, then click to reveal the mark scheme answer.

Describe two differences between a client-server network and a peer-to-peer network. [4] marks

Mark scheme:

Any 2 developed differences for 4 marks (1 per difference, 1 per development):

Client-server has a dedicated server that manages resources / P2P has no central server and all devices are equal (1+1)
Client-server: data and files are stored centrally on the server / P2P: files are distributed across all devices (1+1)
Client-server: requires specialist IT staff to manage the server / P2P: no specialist staff needed (1+1)

Give one advantage and one disadvantage of a client-server network. [2] marks

Mark scheme:

Advantage: centralised data is easier to back up / manage / security can be managed centrally (1)
Disadvantage: if the server fails, the whole network may go down / server is a single point of failure / expensive to set up and maintain (1)

Reflect

Networks Around You

Now that you understand both network models, take a moment to think about how they appear in your daily life:

At school: When you log in to a school computer and access your files, you are using a client-server network. The school’s server authenticates your login, stores your files, and manages printing. Without that server, you would not be able to log in or access your work from different machines.
At home: If you share files between your phone and your laptop over Wi-Fi, or share a printer between family members’ devices, you are likely using a peer-to-peer arrangement — no dedicated server, just devices sharing directly.
Web browsing and email: Every website you visit and every email you send uses the client-server model. Your device (client) talks to web servers and email servers run by companies like Google, Microsoft, and Amazon.
Downloading and streaming: Some download services use P2P technology (like BitTorrent for distributing game updates), while others use client-server (like Netflix streaming from its servers to your TV).
Cryptocurrency: If you have ever used or heard about Bitcoin, you have encountered one of the world’s largest P2P networks — a decentralised system with no central authority.

Most real-world systems use a combination of both models. For example, a game might use client-server for matchmaking and account management, but P2P for actual gameplay between two players. Understanding both models — and their strengths and weaknesses — gives you the knowledge to evaluate and design networks for different situations.

Challenge yourself: Over the next week, every time you use a digital service, ask yourself: is this client-server or peer-to-peer? Think about where the data is stored, whether there is a central server involved, and who controls the system. You will start to see these models everywhere.

Final Thought Neither client-server nor peer-to-peer is inherently “better.” Each model has clear advantages and disadvantages. The best choice depends on the specific situation — the number of users, the budget, the security requirements, and the services needed. Being able to analyse a scenario and recommend the right model, with clear justification, is exactly what your GCSE exam is testing.