Client–Server and Peer-to-Peer
Do all computers on a network have equal roles?
- Explain client–server architecture
- Explain peer-to-peer architecture
- Compare their strengths and weaknesses
Overview
Two computers can share files as equals, or one can act as the 'library' while others borrow from it. That choice — peer-to-peer vs client–server — shapes how a network is managed, secured, and paid for.
Client–server
One or more powerful computers (servers) provide services — file storage, printing, email, web pages — to many less-powerful computers (clients). The school portal, Google Drive, YouTube: all client–server. It centralises control and security but needs someone to run the server.
Peer-to-peer (P2P)
Every device is both a client and a server, sharing resources directly. Two phones exchanging a photo over Wi-Fi Direct, or file sharing in a small home network. Cheap and simple for a few users; unmanageable at scale.
Comparison
Client–server wins on security, backups, and central management. P2P wins on cost, simplicity, and no single point of failure. Real networks often mix both — the school lab is client–server for grades but peer-to-peer for sharing a printer.
Two-Room Demo
- Set up a shared folder on one lab PC (server). Access it from two other PCs (clients).
- Then, using Wi-Fi Direct or Bluetooth, share a small file phone-to-phone (P2P).
- Write two sentences comparing what you observed.
- Which architecture centralises security and backups?
Reveal answer
Client–server.
- Give one weakness of P2P.
Reveal answer
Hard to manage, secure or scale as the network grows.
- Is Google Drive client–server or P2P?
Reveal answer
Client–server (Google owns the servers).
Read up on 'BitTorrent'. Is it pure P2P, pure client–server, or a mix? Justify with one sentence.