The client side focuses only on presentation issues, and is relieved of
computationally intensive tasks.
The server side carries out all the processing.
Presentation and processing are kept separate, the former on the client
tier the latter on the server tier.
Processing and persistence are kept separate, the former on the server
side, the latter on the data side.
This strict separation of concerns gives rise to several benefits. A lower
processing power is required on the client side; it has only to support the
graphical user inteface. All the processing is concentrated in the server
tier, allowing for a simpler design. The server design is further simplified
because it does not care about persistence, which is the data tier's
The user interface can be changed with a reduced impact on the
processing component. Different persistence solutions can be adopted
within the data tier which are transparent to the rest of the system.
Date, J. (2000) Design and Implementation of Database Systems , Addison-Wesley.
Huston, G. (2000), “TCP Performance”, The Internet Protocol Journal , Cisco
Systems, Vol. 3, No. 2, July, 2
Java POS Committee (2001) Java for Retail POS - Programming Guide , Version