eBay is a P2P application.
client-server
with the Web, a browser is a client process and a Web server is a server process. With p2p file sharing, the peer that is downloading the file is labeled as the client, and the peer that is uploading the file is labeled as the server .
Distinguish between Peer-to-Peer and server based networks
In a peer to peer network, all nodes are the same. In a client-server network, conversely, the server node maintains control over other nodes.
The client-server topology.
False - a peer-to-peer network is simpler.
The use of one or more servers distinguishes a client/server network from a peer-to-peer network.
In Peer to peer the machines work as a workgroup machines and can access each other and they process themselves but in client server model all the requests of clients are sent to server it processes the request and send the result to client
client server n peer to peer
Media is always required to connect one device to another on a network. It doesn't matter if it is a client server network or a peer to peer network.
Peer to Peer networking has no central "hub" to store the data to be downloaded. When a Client needs information, they connect to other clients on a network to download that information. An example of Peer-to-Peer networking is BitTorrent. Client-Server Networks use a central computer as a hub to store information. So when a client needs to access information, they need to access the Server for that data. An example of a Client-Server Network is any website.
Network architectures are sometimes classified into two broad categories:· client-server architectures,· peer-to-peer architectures.In the client-server architectural model, a system is decomposed into client and server processors or processes. Servers provide computational resources (or services), which clients consume. Typically a server provides services to many clients. It is also common for clients to consume services from multiple services. Stated otherwise, there is generally a 1:M relationship between a server and its clients, and it is sometimes the case that there is a 1:M relationship between a client and the servers that it uses. The client-server architectural model supports the separation of functionality based on the service concept.Client-server architectures are commonly organized into layers referred to as "tiers".Tiered Architectures· Two-tier architectures. The system architecture consists of a data server layer and an application client layer. Data access computation is associated with the data server layer, and the user interface is associated with the client application layer. If most of the application logic is associated with the client application logic, it is sometimes referred to as a "fat client." If it is associated with the data access server, the application client layer is sometimes referred to as a "thin client." · Three-tier architecture. The system architecture consists of data server layer, an application server layer and a client application layer. The application server layer facilitates the separation of application logic from presentation, and promotes distributed processing.· Multi-tier architecture. The system architecture is a superset of a three-tier architecture, and includes additional layers for data and/or application servers.Peer-to-Peer ArchitecturesIn a peer-to-peer architecture model, a system is decomposed into computational nodes that have equivalent capabilities and responsibilities. This division is in contrast to a client-server architectural model, where client and server nodes are divided into server and client roles. An example of a peer-to-peer architecture is a system of intelligent agents that collaborate to collect, filter, and correlate information.Sometimes layered ("tiered") and peer-to-peer architectures are combined, where the nodes in particular layers are in peer-to-peer relationships. For example, a multi-tiered architecture might include an enterprise management layer, consisting of peer nodes for such things as network management, event management, database management, Web sever management, and workload balancing.