libp2p and the cloud
summary
libp2p modular stack provides mdns for local discovery, a DHT for peer lookup, a connection manager and muxer, and protocol handlers (identity, ping, bitswap, pubsub) that IPFS actually uses. Connections resolve by querying the DHT for a peer’s announced multiaddrs and then dialling using the peer ID plus address. Kubernetes breaks this model because IPs and round‑robin load balancing send dials to pods without the expected peer ID, causing connection refusals; no cloud solution is offered.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:15A modular peer- to-peer networking stack
- 0:39What is a libp2p peer?
- 2:46So what about the cloud?
- 4:33What is the solution?
related talks
23mlibp2p: A Modular, P2P Networking Stack
31mLibp2p: A Modular, P2P Networking Stack
32mGetting started with p2p
27mDecentralized Storage with IPFS: How does it work under the hood?
25mInternet of Peers
14mThe Eternal Tussle: Exploring the Role of Centralization in IPFS
45mIPFS - The Practical Bits
12mWhy Do We Need a Decentralized Storage System?
