When considering peer-to peer architecture, it is important to take into account the traditional model on which most network communications and applications are based; that is client-server architecture.
In contrast to the peer-to-peer model where each network hosts both the client and server parts, Gallo and Hancock (1) describe the client-sever model as a “divided network transaction” whereby
1. The client side (or front end) provides a user with an interface for requesting services from the network, and
2. The server side (or back end) is responsible for accepting user requests for services and providing these servers transparent to the user
Gallo and Hancock (1)
According to Irving (2) the main difference between both architectures is that “client/server architectures require a dedicated server whereas, with peer-to-peer networks, there is no separate server and the work of the server is shared between the connected computers”.
Client-server architecture is supported by various network operating systems such as Novell, Microsoft in Windows NT and 2000 whilst peer-to-peer architecture uses any operating systems which support p2p including Windows 3.11, 95, 98, 2000 and XP.
Although peer-to-peer networking provides organisations with low-cost network solutions, Tannebaum (3) believes that client-server networking still provides organisations with almost all its network requirements.
Bibliography
(1) Gallo, M., and Hancock, W. Networking Explained. Woburn, Digital Press. 1999.
(2) Irving, P. Computer Networks. Exeter, Learning Matters Ltd. 2003.
(3) Tannebaum, A. Computer Networks. 4th edition. New Jersey, Prentice-Hall. 2003.





