This technology didn’t just pop up overnight! In this section we’ll cover the background of decentralized storage from torrents until now, and go through some basics terminology to get you up to speed.
In this module, we cover how to set up your own IPFS node, and how to push and pull files from the network. We’ll also go over the addressing structure and get you caught up on the background of this technology.
State of the Industry
IPFS is just the beginning - in this module we'll catch you up on the developments currently affecting the space, and cover the various cryptocurrencies and tokens that have proposed incentive models for peer to peer storage.
The primary system employed by storage providers in 2018 is to bridge their network to more traditional HTTP(S) GET and POST requests. This allows, the client to read and store records in servers. While client-server connections have functioned relatively well until now, they suffer from some disadvantages that is addressed by a peer-to-peer structure.
In particular, when HTTP calls are routed, they use location-based routing to request files by their relation to a particular structure. As a result, all files on the network must belong to a particular domain and must be hosted by their infrastructure that supports it. This can lead to overcrowding of connections to a under-resourced server and is prone to the breaking of links as files are changed or moved.
In contrast, technologies such as IPFS use purely peer to peer transfer of data. Each file is hosted across a network of connected nodes who each participate independently of each other. In addition, these files use content-based addressing to alleviate the problems of location and revisions. In a similar fashion to the torrents used to share music or movies, these decentralized files are hard to stop, without access to every participating node in the network.