2. INTERNALP2P POSITIONS
1. Still running even without server
2. A peer is directly communicate with other peer
3. All those peer can get the IP address depending on the underlying architecture supported the p2p
system
3. INTERNALHOW DOES IT WORK
1. Still running even without server
2. A peer is directly communicate with other peer
3. All those peer can get the IP address depending on the underlying architecture supported the p2p
system
4. INTERNAL
P2P ARCHITECTURE
1. Centrilized Directory
• Now whenever a requesting peer comes in, it sends its query to the
server.
• Since the server has all the information of its peers, so it returns the IP
addresses of all the peers having the requested file to the peer.
• Now the file transfer takes place between these two peers.
E.G Napster
5. INTERNAL
P2P ARCHITECTURE
2. Query Flooding
• Now when one peer requests for some file, this request is sent to all its
neighboring nodes i.e. to all nodes which are connected to this node. If those
nodes don’t have the required file, they pass on the query to their neighbors
and so on. This is called as query flooding.
• When the peer with requested file is found (referred to as query hit), the
query flooding stops and it sends back the file name and file size to the client,
thus following the reverse path.
• If there are multiple query hits, the client selects from one of these peers.
E.G Gnutella
6. INTERNAL
P2P ARCHITECTURE
3. Exploiting heterogeneity
• This structure can process the queries in two ways.
• The first one is that the super nodes could contact other super nodes and merge their
databases with its own database. Thus, this super node now has information of a large
number of peers.
• Another approach is that when a query comes in, it is forwarded to the neighboring
super nodes until a match is found, just like in Gnutella. Thus query flooding exists but
with limited scope as each super node has many child peers. Hence, such a system
exploits the heterogeneity of the peers by designating some of them as group
leaders/super nodes and others as their child peers.
• .
E.G KaZaA
7. INTERNAL
VERSUS OF CS AND P2P
CS P2P
Client dan server dibedakan, berdasarkan spesifik
server dan client
Client dan server tidak berbeda
Client server berfokus pada pembagian informasi Berfokus pada konektivitas
Server yang tersentral di gunakan untuk menyimpan
data
Setiap peer memiliki masing masing data
Server merespon service yang di request client Setiap node bisa melakukan request dan respond
Lebih mahal secara biaya Tidak semahal biaya client server
Lebih stabil Jika jumlah peer meningkat tingkat kestabilan
rendah
9. INTERNAL
ADVANTAGES
OS IS NO NEEDED
EXPENSIVE SERVER IS NO NEED
EXPENSIVE SERVER IS NO NEED
EASIER TO SET UP
ONE COMPUTER FAILS IT WON’T
DISTRUPTING THE NEWTORK
DISADVANTAGED
EASY TO SLOW DOWN WHILE
COMPUTERS BEING ACCESS BY OTHER
FILE AND FOLDER CAN NOT BE
CENTRALLY BACK UP
FILE AND RESOURCE NOT CENTRELIZED
IN SPECIFIC AREA
REGARDING THE SECURITY IT’S A LITLE
OR EVEN NO SECURITY
WHY P2P IS USEFULL
10. INTERNAL
References
• P2P(Peer To Peer) File Sharing. Accessed on October 16th 2019.
• https://www.geeksforgeeks.org/p2ppeer-to-peer-file-sharing/
• A Brief History of P2P Content Distribution, in 10 Major Steps. Accessed on October 16th 2019.
https://medium.com/paratii/a-brief-history-of-p2p-content-distribution-in-10-major-steps-6d6733d25122
• Peer-to-peer file sharing. Accessed on October 16th 2019.
• https://en.wikipedia.org/wiki/Peer-to-peer_file_sharing
• Pure P2P architecture P2P: centralized directory no. Accessed on 16th 2019 . https://studylib.net/doc/13347485/pure-p2p-
architecture-p2p--centralized-directory-no
• Difference between Client-Server and Peer-to-Peer Network. Accessed on October 16th. 2019
https://www.geeksforgeeks.org/difference-between-client-server-and-peer-to-peer-network/
• Slides from Werner Nutt Slides (lecturer of University Bozen Balzano. Accessed on October 15th 2019
• http://www.inf.unibz.it/~nutt/Teaching/DSs1011/dss-slides.html
