Peer - A participant in a decentralized network. Peers are equally privileged, equipotent participants in the application. In IPFS, when you load up the IPFS Desktop app on your laptop or run
ipfs daemon from the command line, your device becomes a peer in the decentralized network that is IPFS.
Peer-to-Peer (P2P) - A decentralized network in which workloads are shared between peers. So in IPFS, each peer might host full or partial files to be shared with other peers. When one peer requests files, any peer that has chunks of those files can participate in the sending requested files. And then, the peer who request the data can later on share the data with other peers.
Peer-to-peer (P2P) networks were envisioned from the very conception of the internet as a way to create resilient networks that would function even if peers disconnected from the network due to major natural or human disasters, allowing people to continue to communicate.
P2P networks can be used for a variety of use cases, from video calls (eg Skype) to file sharing (eg IPFS, Gnutella, KaZaA, eMule, and BitTorrent).
One of the main challenges that all apps with P2P connections have to solve is discoverability: how can two or more peers find each other and share information? In the past, each P2P app has tackled this problem (among many others) and implemented their own solutions with different ideas and approaches customized to their individual use case.
IPFS searched for inspiration in current and past networking applications and research to try and improve its P2P system. There were plenty of scientific papers from the world of academia that provided ideas on how to solve some of these issues, but while research yielded preliminary results, it lacked code implementations that could be used and adapted.
Code implementations of existing P2P systems were really hard to find, and where they did exist, they were often hard to re-use or re-purpose due to:
So in the end, every time P2P protocols were needed, developers would solve the same challenges again and again from scratch because the P2P protocols already embedded in software packages weren't extractable and reusable.
One would think that this was a problem of the past. The open-source community has evolved over the years and built a robust ecosystem that provides thousands of open-source software packages that include a thorough battery of test suites, good documentation, and friendly APIs. But unfortunately, no good P2P protocol implementation had appeared that solved all of the presented issues across a variety of use cases.
Historically, companies that produced products like Skype or BitTorrent created their own protocols to support them. Those protocols made a lot of assumptions about the environments they'd run in and the needs they'd meet, making them incredibly hard to upgrade or adapt to new environments.
Of course the answer to all of these problems was a shiny new protocol that solved all of these problems once and for all! Well... not exactly.
There had to be a better way. Seeing that the main issue was interoperability, the IPFS team envisioned a better way to integrate all current solutions and provide a platform that facilitated innovation. A new modular system that would enable future solutions to be seamlessly integrated into the networking stack.
Feeling stuck? We'd love to hear what's confusing so we can improve this lesson. Please share your questions and feedback.