Choosing a Network Model

A network model is either client-server or peer-to-peer. Recommending one for a scenario means matching its benefits and drawbacks to that scenario's needs: how many users there are, whether central management is needed, cost and ease of setup.

Client-server suits a large organisation with many users that needs central management, central storage, central backup and central security. Servers provide shared services and files, so backups and security can be handled in one place. The drawbacks are expensive server hardware and specialist setup and maintenance, which are worth paying for when many users depend on those services.

Peer-to-peer suits a small network with few devices that does not need central management and values low cost and simple setup. Each computer shares its own resources and uses resources shared by others, so no server has to be bought or managed. The drawbacks are that files and backups are spread across the computers and security is set up on each one, which becomes harder as more users join.

Justify the choice

A recommendation must be justified with reasons from the roles of the computers and the advantages or disadvantages of the chosen model, not just a statement that one model is better. Point to who provides the resource and who uses it: the server stores the files and controls access, or each peer shares its own files.

For example, a five-a-side football club with four laptops and a tiny budget wants to swap training videos between them. Peer-to-peer fits: each laptop can share its own videos and no server or specialist is needed, so the cost stays low. A charity's fundraising office with 250 staff who must all work from the same donor records needs client-server: a central server can store the records, back them up and limit who sees donation amounts, all in one place.

Choosing the model is a separate decision from the network's physical topology.