P2P Computing: Difference between revisions
| Line 37: | Line 37: | ||
==Examples== | ==Examples== | ||
#Kontiki, Qtrax, and RawFlow "exploit p2p characteristics for secure content distribution | |||
[[Bittorrent]] | #[[Bittorrent]] | ||
#[[Tribler]] | |||
[[Tribler]] | #[[Skype]] | ||
#[[Groove]] | |||
[[Skype]] | #[[Bitvault]] | ||
#[[Windows Collaboration]] | |||
[[Groove]] | #[[PeerDB]] | ||
[[Bitvault]] | |||
[[Windows Collaboration]] | |||
[[PeerDB]] | |||
==P2P for Business== | ==P2P for Business== | ||
Revision as of 03:23, 5 September 2007
Definition
From http://thothzone.blogspot.com/2006/07/p2p-buzz-to-biz.html:
"Peer-to-peer (P2P) computing has been envisaged to solve computing scenarios which require requiring spatial distribution of computation, spatial distribution of content, real-time collaboration, ad-hoc networking, scalability or fault-tolerance at reduced costs. P2P systems provide higher storage and access capacity via distribution of resources across peers, improved reliability due to the availability of multiple peer machines and distributed security achieved by distributing partial secrets across peers. Unlike the client-server computing paradigm, where all the computation cycles and data are to be had from a single source, in P2P the participating peers contribute CPU cycles and storage space." (http://thothzone.blogspot.com/2006/07/p2p-buzz-to-biz.html)
Jorn de Boever writes that:
"There is still no generally acknowledged unambiguous definition of the concept of peer to peer which causes a discussion about what can, or not, be accepted as peer to peer"
In client/server systems, centralized servers manage and control the network, provide services and resources whereas the clients consume these resources. This model suffers from inefficient allocation of resources and limited scalability. Additional users stand for additional costs as they consume more bandwidth from the system.
Nodes in peer to peer networks do not only act as clients, but they exhibit server functions as well. They have been described as servents (= SERVer plus cliENTS)."
Aspects
From http://thothzone.blogspot.com/2006/07/p2p-buzz-to-biz.html:
• Availability: In a federated environment, peers provided no uptime or downtime guarantee. It might so happen that the peer hosting some resource goes offline during use. As every peer can act as a server, the client peer should theoretically be able to switch over to another peer and get the resource, if available elsewhere.
• Authenticity: Remote content and behavior have to be verified since files were found not to be what they claimed and at times peers behaved maliciously. Since trust was not usually woven into the software or often ill implemented, users ran the risk of having their solitary home PC being compromised.
• Digital Piracy: The ease with which digital content could be shared in a P2P network meant that users threw caution to the winds and went about creating libraries with thousands of pirated files. In the absence of enforcement, copyright regulations were openly flouted by P2P networks like Napster. Technology was lacking and on top of it, rather than being a taboo, studies indicate that being able to a hyper-rich online media collection – pirated or purchased - became a matter of pride in user circles.
• Load Balancing: Not all content is widely available in the network. In such cases the then P2P networks degenerated to a client-server network with all traffic for the scarcer content being directed to a small number of hosts, usually with little server type resources at their disposal.
• Hardware Reliability: P2P networks usually comprise of cheaper PC hardware. Therefore, in larger networks there would be quite many failures to be dealt with. Even though data loss due to hardware failures can be avoided easily by storing data and backup on different peers, malicious peers might tamper the backup data on their local storage. • Software Reliability: Early clients were either poorly written and were overtly insecure. So it was easy to make the network disreputable among the by poisoning the network with junk files or even viruses."
(http://thothzone.blogspot.com/2006/07/p2p-buzz-to-biz.html)
Examples
- Kontiki, Qtrax, and RawFlow "exploit p2p characteristics for secure content distribution
P2P for Business
"The emergence of the Distributed Hash Table (DHT) and the Bittorrent protocol can be taken as the beginning of the “Biz" era in P2P computing. Along with advancements in Digital Rights Management, storage technology, network bandwidth and software security, many niche applications of P2P have been identified and implemented, adding to the momentum. Moreover, studies conducted over the past few years, indicate business models for P2P systems are economically viable" (http://thothzone.blogspot.com/2006/07/p2p-buzz-to-biz.html)
More Information
The P2P Filesharing Networks are listed here: Bittorrent, Ares, eDonkey2000, Fast Track, Gnutella
See also the arguments in Peer to Peer - Advantages
DP2P Net monitors decentrazized P2P computing developments and programs.
Key Books to Read
Four are listed here