Commit 969e1e16e2a878f61b1955976fa3f61e943e8e9a
more scaling notes
Stephen Whitmore committed on 1/6/2018, 4:06:03 AMParent: 7fd3b2ac0ceae794069fbb7cb732af04ae29197b
Files changed
| README.md | changed |
| README.md | |||
|---|---|---|---|
| @@ -6,10 +6,17 @@ | |||
| 6 | 6 … | systems by design, and most distributed systems are meant to scale. You could | |
| 7 | 7 … | say, then, that many distributed systems take cues from p2p systems in order to | |
| 8 | 8 … | scale properly. As a good example, Skype was built by the same engineers who | |
| 9 | 9 … | built Kazaa, and Skype internally used p2p distribution in order to alleviate | |
| 10 | -the load from any single node, and to save costs. | ||
| 10 … | +the load from any single node, and to save costs. Bittorrent also thrives in | ||
| 11 … | +situations where there are a high number of peers. | ||
| 11 | 12 … | ||
| 13 … | +Like centralized systems, performance will suffer if the load is not | ||
| 14 … | +distributed. A torrent file with only one seed and thousands of leechers would | ||
| 15 … | +struggle to initially share to the first wave of peers. Unlike a centralized | ||
| 16 … | +system though, once that first wave of peers downloads a copy, the bandwidth for | ||
| 17 … | +that torrent data to be served grows exponentially. | ||
| 18 … | + | ||
| 12 | 19 … | ## If websites are hosted on p2p, what happens when no peers are online? | |
| 13 | 20 … | ||
| 14 | 21 … | ... | |
| 15 | 22 … | ||
Built with git-ssb-web