Show understanding of thin-client and thick-client and the differences between them

Thin‑Client vs Thick‑Client

Think of a thin‑client as a remote control 🎮 – it sends commands to a powerful TV (the server) and receives only the picture. A thick‑client is like a full TV 📺 – it has its own screen, processor, and memory, and can work independently.

• Thin‑Client:
  • Minimal local resources (CPU, RAM, storage)
  • All heavy processing happens on the server
  • Requires constant network connection
  • Ideal for shared workstations in schools or offices
• Thick‑Client:
  • Runs applications locally on the user’s machine
  • Can function offline (limited features)
  • Requires more powerful hardware
  • Common in gaming, video editing, and standalone desktops

Exam Tip

When answering diagram questions, label the client and server clearly and state whether the client is thin or thick. Use the analogy of a remote control vs a TV to remember the key differences.

Key Technical Differences

Exam Tip

Use the table above to quickly recall the main differences. When a question asks for “advantages of a thin‑client”, think of centralised security and low maintenance cost.

Network Bandwidth Formula (Optional)

Bandwidth (B) can be estimated by the simple formula:

$B = \dfrac{S}{T}$

where S is the size of data in bits and T is the time in seconds. This helps you understand why thin‑clients need a stable, high‑bandwidth connection.

Quick Recap

1. Thin‑Client: Remote control – minimal local resources, server‑centric.
2. Thick‑Client: Full TV – local processing, can work offline.
3. Key differences: processing, storage, network dependency, security.
4. Exam strategy: label diagrams, use analogies, remember the table.