I am currently playing around with IPFS in a little weekend project and wanted to understand more about the inner workings of this peer to peer distributed file system. Especially how it differs in comparisson to BitTorrent
This paper gives a nice overview about the inner workings of this distributed file system, certain tamperproof mechanisms and how files can be addressed. It is a more general overview as a super deep-dive, but for the beginning perfect. If you want to jump deeper actually the IPFS blog is quite great.
From an academic perspective the paper puzzles me: It is the most cited one, linked from official IPFS page but still only a draft O_o
Effective resizing of images should not only use geometric constraints, but consider the image content as The Inter Planetary File System (IPFS) is a peer-to-peer distributed file system that seeks to connect all computing devices with the same system of files. In some ways, IPFS is similar to the Web, but IPFS could be seen as a single BitTorrent swarm, exchanging objects within one Git repository. In other words, IPFS provides a high through-
put content-addressed block storage model, with content-addressed hyper links. This forms a generalized Merkle DAG, a data structure upon which one can build versioned file systems, blockchains, and even a Permanent Web. IPFS combines a distributed hashtable, an incentivized block exchange, and a self-certifying namespace. IPFS has no single point of failure, and nodes do not need to trust each other.
- Merkle DAG: Explanation on what a Merkle DAG is on the IPFS site
It would be awesome if you could help growing our little paper community even more by sharing it with your circles (you can also @eu_frey me on Twitter for retweets :D):
If you have any paper recommendation for me, please do not hesitate to approach me via [email protected] (Please keep the Backend & DevOps topic focus in mind)
With much love,