Cambridge A-Level Computer Science 9618 – Networks: Thin‑client vs Thick‑client
2.1 Networks – The Internet
Thin‑client and Thick‑client Concepts
A thin client is a lightweight computing device that relies heavily on a central server for processing, storage, and application execution. The client’s hardware and software are minimal, typically handling only input/output and display functions.
A thick client (also called a fat client or rich client) performs most of the processing locally. It runs full‑featured operating systems and applications, storing data and executing code on the device itself, while still being able to communicate with servers when needed.
Typical Architecture
Thin client:
Input devices (keyboard, mouse)
Display unit
Network interface (wired or wireless)
Minimal OS (often a thin‑client OS or firmware)
Thick client:
Full CPU, RAM, and storage
Complete operating system (Windows, macOS, Linux, etc.)
Installed applications
Network interface for optional server communication
Advantages and Disadvantages
Thin client
Lower hardware cost
Easier maintenance – updates are applied centrally
Improved security – data resides on the server
Reduced power consumption
Potential latency issues if network performance is poor
Limited offline capability
Thick client
Rich user experience with high‑performance graphics and processing
Works offline; can run applications without network access
Greater flexibility for installing custom software
Higher purchase and maintenance costs
More complex security management (data stored locally)
Increased power usage
Comparison Table
Aspect
Thin Client
Thick Client
Processing location
Primarily on server
Primarily on local device
Storage
Server‑side (centralised)
Local hard drive / SSD
Hardware requirements
Minimal CPU, RAM, no large storage
Full‑spec CPU, ample RAM, substantial storage
Software installation
Managed centrally on server
Installed individually on each device
Network dependency
High – requires constant connectivity
Low – can operate offline
Security model
Data never leaves server; easier to enforce policies
Data stored locally; requires endpoint protection
Cost (initial & ongoing)
Lower hardware cost; higher server & bandwidth cost
Design studios, gaming, scientific computing, mobile workstations
When to Choose Which?
Use a thin client when:
Centralised control and security are priorities.
Applications are web‑based or can run on virtual machines.
Budget constraints limit hardware upgrades.
Users work in a stable, high‑speed network environment.
Use a thick client when:
High performance, graphics‑intensive, or specialised software is required.
Users need to work offline or in environments with unreliable connectivity.
Customization of the operating system or applications is essential.
Suggested diagram: A side‑by‑side schematic showing a thin client connected to a central server versus a thick client operating independently, with arrows indicating data flow and processing locations.