Fat Client vs Fat Server Architecture

A fat client performs substantial application processing on the client machine. A fat server performs most application processing centrally; the client mainly handles the user interface.

Basis	Fat client	Fat server
Processing	Mostly client-side	Mostly server-side
Client hardware	Usually needs more resources	Can be relatively lightweight
Data management	May process/cache data locally; synchronization may be needed	Centralized data and business logic are easier to manage
Deployment	Client applications must be installed/updated on multiple devices	Server-side updates can apply centrally
Network	Some tasks may work offline or need fewer requests	Often relies more on network availability
Control	More logic resides on user devices	Easier to enforce central policies
Example	Rich desktop application	Browser-based banking application

Conclusion: Fat clients can be responsive and support offline work; fat-server systems simplify centralized deployment and control. Most real applications distribute work between both.