Where should the 'thinking' happen — on the server, or on the client device? This subtopic covers the spectrum of client types.
| Client type | Processing done locally | Typical use case |
|---|---|---|
| Thin client | Very little — mostly relies on the server for processing and storage | Call centres, kiosks — cheap, easy to manage centrally, but useless without network access |
| Fat client | Most/all processing done locally, server mainly used for shared data/storage | Traditional desktop applications — works well offline, but harder to manage/update across many devices |
| Smart client | A balance — some local processing/caching plus server connectivity for shared data and updates | Modern business applications wanting both offline capability and centralised data |
Example
A call centre using thin clients means all agent software runs on a central server — if that server goes down, every workstation is unusable, but IT only has to update software in one place.
💡 Exam Tip
Link your choice of client type to specific business needs: cost and central management favour thin clients; reliability without network dependence favours fat clients; a balance of both favours smart clients.