Peer-to-Peer

In a client-server system, clients only ask for things and servers only answer. A browser talks to a web server, a phone app talks to an API. The server is special: it holds the data, does the work, and everyone depends on it.

Peer-to-peer flips that. There is no special machine. Every node, called a peer, runs the same software and plays both roles. When you download a movie over BitTorrent, your machine is downloading pieces from dozens of strangers and uploading pieces to dozens of others at the same instant. You are a client and a server in the same breath.

Because no single node is in charge, P2P systems are decentralized. There is no central authority that must stay online for the network to work. If half the peers disappear, the rest keep going. This is the property that makes P2P resilient and hard to shut down, and it is also what makes it harder to coordinate and secure.

The hard problem in P2P is discovery: how does a peer find the other peers that have what it wants? There are two common answers. Some systems use a structured approach based on a distributed hash table (DHT), where every piece of content has a key and the network agrees on which peers are responsible for which range of keys. Kademlia, the DHT used by BitTorrent and IPFS, lets any peer locate the owner of a key in about log(N) hops, so finding data among a million peers takes roughly 20 lookups.

Other systems use a tracker or a set of bootstrap nodes just to help newcomers join, then run fully peer-to-peer after that. A BitTorrent tracker hands you an initial list of peers, but the actual file transfer never touches the tracker.

Once peers know each other, they exchange data directly. They split content into chunks so a file can be assembled from many sources in parallel, and they verify each chunk with a cryptographic hash so a malicious peer cannot feed you garbage. Blockchains add a consensus layer on top, where peers must agree on a single shared history through rules like proof of work or proof of stake, because money is at stake and disagreement cannot be tolerated.

P2P shines when you want to scale capacity with the crowd. In client-server, every new user adds load to your servers. In P2P, every new peer brings its own upload bandwidth and storage, so the network often gets faster as it grows. This is why P2P is a natural fit for large file distribution, live video at scale, and systems that need to survive without a trusted operator.

The costs are real. Discovery and consistency are much harder without a central coordinator, so engineering effort goes up. Peers come and go constantly, a behavior called churn, so the system must constantly heal. Security is trickier because you are trusting unknown machines, which is why hashing, encryption, and consensus are not optional. Latency can be unpredictable because the peer holding your data might be on the other side of the planet on a slow connection.

A practical middle ground is the hybrid model. Spotify originally streamed music partly over P2P to cut bandwidth costs while keeping central servers for login and search. WebRTC sets up direct peer connections for video calls but still uses central STUN and TURN servers to punch through firewalls. Pure P2P is rare in production; most real systems keep a thin central layer for the parts that genuinely need coordination.

Say a Linux distribution releases a 4 GB ISO and a million people want it on launch day. Serving that from one set of servers would cost a fortune in bandwidth and likely fall over.

With BitTorrent, the publisher creates a small torrent file that lists the chunk hashes and a tracker URL. The first downloaders, called seeders, get the whole file. As new peers join, they download chunks from whoever has them, and the moment a peer finishes a chunk it starts uploading that chunk to others. A peer with the complete file is a seeder; one still downloading is a leecher.

The result is that the popular ISO actually downloads faster, because a hot file means more peers sharing it. The original publisher might only ever upload one or two full copies, and the crowd does the rest. That inversion of cost, where popularity reduces load on the origin instead of increasing it, is the core reason P2P keeps getting reinvented for new problems.