Test yourself on Client-Server & Peer-to-Peer with exam style questions, marked instantly.
Flashcards that come back just before you would forget them.
A revision plan that remembers what you know and shows what to do next.
See which topics you have nailed and which need another look.
Quiz yourself on Client-Server & Peer-to-PeerGet your flashcardsBuild my revision planTrack my progressThe Two Ways to Organize Networks
Client-Server vs Peer-to-Peer
Client-server is good for central security, backups and management, but the server costs money and is a single point of failure. Peer-to-peer is cheap and simple to set up, but has no central security or backups. Both models are in the OCR specification only.
Client-Server Architecture
What is Client-Server?
A network model where a powerful central server provides services (files, applications, authentication) to multiple client computers. Clients request, server provides.
Key Characteristics:
- Central server: One or more powerful servers provide services
- Many clients: Computers/devices that request services from server
- Request-response: Client requests → Server responds
- Centralized control: Server manages everything (security, backups, access)
- Client dependency: Clients depend on server for services
Server Roles:
- File server: Stores all user files centrally - access from any client
- Application server: Hosts software - clients run applications remotely
- Authentication server: Manages user accounts, logins, permissions
- Email server: Handles all email for organization
- Web server: Serves web pages to clients (browsers)
- Print server: Manages shared printers
Client-Server Examples:
- School network: Student computers (clients) access files from school server
- Office network: Employee computers connect to company server for documents
- Web browsing: Your browser (client) requests pages from web servers
- Email: Outlook/Gmail client connects to email server
- Online banking: Your computer (client) connects to bank's server
Client-Server Advantages:
- Central security: User accounts and permissions managed in one place
- Central backups: All data backed up from server (automatic, reliable)
- Easy management: IT staff manage everything from server
- Access anywhere: Log in from any client computer, access your files
- Powerful resources: Server has high-spec hardware (fast CPU, lots of RAM)
- Shared resources: Printers, applications available to all clients
- Centralized updates: Software updates applied on server, affect all clients
Client-Server Disadvantages:
- Single point of failure: If server fails, clients can't access services
- Expensive: Powerful server hardware is costly (£5000-£50000+)
- Requires expertise: Need skilled IT staff to manage server
- Network dependency: Clients must have network connection to server
- Bottleneck risk: Too many clients can overwhelm server
Peer-to-Peer (P2P) Architecture
What is Peer-to-Peer?
A network model where all computers are equal (peers). Each computer can BOTH request AND provide resources. No central server - computers share directly with each other.
Key Characteristics:
- All equal: Every computer is a peer (no server/client distinction)
- Direct sharing: Computers share resources directly with each other
- Decentralized: No central control point
- Dual role: Each computer is BOTH client (requests) AND server (provides)
- Independent: Each computer manages its own resources
P2P Examples:
- Home network: Two laptops sharing files directly (no server)
- BitTorrent: File sharing - download pieces from many peers simultaneously
- Skype (original): Direct voice/video calls between users
- Bitcoin: Cryptocurrency with no central authority
- LAN gaming: Multiplayer game hosted on player's computer
P2P Advantages:
- No single point of failure: Network continues if one peer fails
- Cheap: No expensive server needed - use existing computers
- Easy setup: Just connect computers, no server configuration
- Scalable: More peers = more resources (each adds capacity)
- No server maintenance: No dedicated hardware to maintain
P2P Disadvantages:
- No central security: Each computer manages own security (inconsistent)
- No central backups: Users must backup their own files
- Hard to manage: Each computer configured separately
- Access issues: Files on User A's computer only available when User A is online
- Performance varies: Depends on individual computer specs
- No central control: Can't enforce policies across network
Client-Server vs Peer-to-Peer - Direct Comparison
| Aspect | Client-Server | Peer-to-Peer (P2P) |
|---|---|---|
| Structure | Central server provides services to clients | All computers equal - share directly |
| Central Server? | YES - one or more powerful servers | NO - no dedicated server |
| Role | Clients request, server provides | Each computer is BOTH client AND server |
| Security | Central - managed on server | Decentralized - each computer manages own |
| Backups | Central - all data backed up from server | No central backups - users responsible |
| Management | Easy - centralized control from server | Hard - each computer managed separately |
| Single Point of Failure? | YES - server failure = all services down | NO - network continues if one peer fails |
| Cost | Expensive - powerful server hardware needed | Cheap - no dedicated server required |
| Setup | Complex - requires expertise | Simple - easy to set up |
| Performance | Consistent - powerful server | Variable - depends on peer computers |
| Scalability | Server can become bottleneck | More peers = more capacity |
| Best For | Schools, offices, large organizations | Small networks, file sharing, home use |
| Examples | School network, web browsing, email | Home file sharing, BitTorrent, LAN gaming |
Real-World Scenario: Why Schools Use Client-Server
Imagine a school with 1000 students and 50 teachers - why client-server?
Central User Accounts:
- Student logs in with username/password from ANY school computer
- Server authenticates: "Yes, this is StudentA, allow access"
- Student's files appear - stored on central file server
- Works in Lab 1 Monday, Lab 2 Tuesday - same files available!
- P2P problem: Files stuck on specific computer - can't access from other machines
Central Security:
- IT staff manage all permissions from server: "Year 7 can't access Year 11 files"
- Block inappropriate websites centrally
- Install security updates on server - affects all 1000 computers
- P2P problem: Must configure security on EACH of 1000 computers separately!
Central Backups:
- School's file server automatically backed up every night
- Student accidentally deletes coursework? IT restores from backup
- All 1000 students' work safe on central server
- P2P problem: Students must remember to back up own files (they won't!)
The Cost Trade-off:
School pays £20,000 for powerful server. But the benefits (security, backups, management) are worth it for 1000 users. P2P would be chaos!
Real-World Scenario: Why BitTorrent Uses P2P
Imagine downloading a large file (Linux ISO - 4GB) - why P2P?
Client-Server Problem:
- If 1000 people download 4GB file from one server: server sends 4000GB!
- Server bandwidth costs thousands per month
- Server becomes bottleneck - downloads slow to crawl
- If server fails - NO ONE can download
P2P Solution (BitTorrent):
- File split into 1000 pieces
- You download piece 1 from User A, piece 2 from User B, piece 3 from User C...
- As soon as you have piece 1, you share it with others
- More downloaders = MORE sources = FASTER downloads (opposite of client-server!)
- If User A goes offline - get piece 1 from someone else
- No single point of failure
Why P2P Wins Here:
Distributing bandwidth load across thousands of peers = cheap, fast, resilient. Client-server would cost fortune and be slower!
Exam Tips - Client-Server vs P2P
Most common exam questions:
- "What is client-server?" → Central server provides services to client computers
- "Advantage of client-server?" → Central security/backups/management
- "Disadvantage of client-server?" → Server = single point of failure / expensive
- "What is P2P?" → All computers equal - share resources directly (no server)
- "Advantage of P2P?" → No single point of failure / cheap (no server needed)
- "Disadvantage of P2P?" → No central security/backups / hard to manage
- "Why do schools use client-server?" → Central accounts (login anywhere) / central backups / easy management
Key facts to memorize:
| Aspect | Client-Server | P2P |
|---|---|---|
| Structure | Central server + clients | All equal (peers) |
| Security | Centralized (easy) | Decentralized (hard) |
| Cost | Expensive (server) | Cheap (no server) |
| Failure | Server = single point | No single point |
Common mistakes to avoid:
- Forgetting "central" when explaining client-server benefits (central security, central backups)
- Not mentioning server = single point of failure (KEY disadvantage!)
- Thinking P2P means "no server at all anywhere" - P2P means no DEDICATED server
- Missing that P2P computers are BOTH client AND server
Perfect exam answer:
"Explain why a school should use client-server networking" (4 marks):
Central user accounts - students can log in from any computer (1 mark).
Central security - access controls managed in one place (1 mark).
Central backups - all student work backed up to server (1 mark).
Easy management - IT staff can manage from server (1 mark).
Quick Reference - Client-Server vs P2P
Client-Server:
- Structure: Central server provides services to clients
- Advantages: Central security/backups/management, access anywhere
- Disadvantages: Server = single point of failure, expensive
- Use: Schools, offices, large organizations
Peer-to-Peer (P2P):
- Structure: All computers equal, share directly (no server)
- Advantages: No single point of failure, cheap, easy setup
- Disadvantages: No central security/backups, hard to manage
- Use: Small networks, file sharing (BitTorrent), home use
Remember: Client-Server = centralized (security, backups, management) but server = single point of failure. P2P = decentralized (no single failure) but no central control!
Make this stick
Signing in gives access to all PrepWise features.