Peer-to-Peer (P2P) Architecture
Part of Client-Server vs P2P — GCSE Computer Science
This key facts covers Peer-to-Peer (P2P) Architecture within Client-Server vs P2P for GCSE Computer Science. Revise Client-Server vs P2P in Networks for GCSE Computer Science with 15 exam-style questions and 18 flashcards. This topic appears less often, but it can still be a useful differentiator on mixed-topic papers. It is section 4 of 9 in this topic. Use this key facts to connect the idea to the wider topic before moving on to questions and flashcards.
Topic position
Section 4 of 9
Practice
15 questions
Recall
18 flashcards
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