Carnegie Mellon Peer-to-Peer 15-441
Peer-to-Peer 15-441
Carnegie Mellon Scaling problem ·Mi| ions of clients→ server and network meltdown 鸟血堂血
2 Scaling Problem • Millions of clients ⇒ server and network meltdown
Carnegie Mellon P2P System Leverage the resources of client machines(peers) Computation storage bandwidth
3 P2P System • Leverage the resources of client machines (peers) – Computation, storage, bandwidth
Carnegie Mellon Why p2p? Scaling: Create system whose capacity grows with of clients-automatically Self-managing This aspect attractive for corporate/datacenter needs e.g., Amazons 100,000-ish machines, google's 300k+ Harness lots of"spare" capacity at end-hosts Eliminate centralization Robust to failures etc Robust to censorship, politics legislation?? Create apps/services without having huge resources
4 Why p2p? • Scaling: Create system whose capacity grows with # of clients - automatically! • Self-managing – This aspect attractive for corporate/datacenter needs – e.g., Amazon’s 100,000-ish machines, google’s 300k+ • Harness lots of “spare” capacity at end-hosts • Eliminate centralization – Robust to failures, etc. – Robust to censorship, politics & legislation?? – Create apps/services without having huge resources
Carnegie Mellon Today's Goal p2p is hot There are tons and tons of instances But that's not the point Identify fundamental techniques useful in p2p settings Understand the challenges Look at the(current )boundaries of where 2p is particularly useful
5 Today’s Goal • p2p is hot. • There are tons and tons of instances • But that’s not the point • Identify fundamental techniques useful in p2p settings • Understand the challenges • Look at the (current!) boundaries of where 2p is particularly useful 5