From 9581254590989b9879092c8d2705cfd021bb3e1e Mon Sep 17 00:00:00 2001 From: David Dias Date: Sun, 4 Dec 2016 16:34:30 +0100 Subject: [PATCH] docs: remove old ARCHITECTURE.md --- ARCHITECTURE.md | 96 ------------------------------------------------- 1 file changed, 96 deletions(-) delete mode 100644 ARCHITECTURE.md diff --git a/ARCHITECTURE.md b/ARCHITECTURE.md deleted file mode 100644 index ce760a22ae..0000000000 --- a/ARCHITECTURE.md +++ /dev/null @@ -1,96 +0,0 @@ -# Architecture - -``` -┌───┐ ┌───────────────┐ ┌──────────────┐ -│CLI│───▶│ HTTP API ├───▶│IPFS Core Impl│ -└───┘ └───────────────┘ └──────────────┘ - △ △ △ - └──────────────└──────────┬─────────┘ - │ - ┌─────┐ - │Tests│ - └─────┘ -``` - -## IPFS Core implementation architecture - -IPFS Core is divided into separate subsystems, each of them exist in their own repo/module. The dependencies between each subsystem is assured by injection at the IPFS Core level. IPFS Core exposes an API, defined by the IPFS API spec. libp2p is the networking layer used by IPFS, but out of scope in IPFS core, follow that project [here](https://github.com/diasdavid/js-libp2p) - - -``` - ▶ ┌───────────────────────────────────────────────────────────────────────────────┐ - │ IPFS Core │ - │ └───────────────────────────────────────────────────────────────────────────────┘ - │ - │ │ - │ - │ ┌──────────────┬──────────────┼────────────┬─────────────────┐ - │ │ │ │ │ - │ │ │ │ │ │ - ▼ │ ▼ │ ▼ - │ ┌──────────────────┐ │ ┌──────────────────┐ │ ┌──────────────────┐ - │ │ │ │ │ │ │ │ - │ │ Block Service │ │ │ DAG Service │ │ │ IPFS Repo │ - │ │ │ │ │ │ │ │ - │ └──────────────────┘ │ └──────────────────┘ │ └──────────────────┘ - │ │ │ │ - IPFS Core │ ▼ │ ┌────┴────┐ │ - ┌────────┐ │ ▼ ▼ │ - │ │ Block │ │ ┌────────┐┌────────┐ │ - └────────┘ │ │DAG Node││DAG Link│ │ - │ │ └────────┘└────────┘ │ - ┌──────────────────┐ │ │ ┌──────────────────┐ - │ │ │ │ │ │ │ - │ Bitswap │◀────┤ ├──────▶│ Importer │ - │ │ │ │ │ │ │ - └──────────────────┘ │ │ └──────────────────┘ - │ │ │ │ - │ │ ┌────┴────┐ - │ │ │ ▼ ▼ - │ │ ┌────────┐┌────────┐ - │ ┌──────────────────┐ │ │ │ layout ││chunker │ - │ │ │ ┌────────────┘ └────────┘└────────┘ - │ │ Files │◀────┘ │ - │ │ │ - │ └──────────────────┘ │ - ▶ │ - ▼ - ┌───────────────────────────────────────────────────────────────────────────────┐ - │ │ - │ │ - │ │ - │ libp2p │ - │ │ - │ │ - └───────────────────────────────────────────────────────────────────────────────┘ -``` - -#### IPFS Core - -IPFS Core is the entry point module for IPFS. It exposes an interface defined on [IPFS Specs.](https://github.com/ipfs/specs/blob/ipfs/api/api/core/README.md) - -#### Block Service - -Block Service uses IPFS Repo (local storage) and Bitswap (network storage) to store and fetch blocks. A block is a serialized MerkleDAG node. - -#### DAG Service - -DAG Service offers some graph language semantics on top of the MerkleDAG, composed by DAG Nodes (which can have DAG Links). It uses the Block Service as its storage and discovery service. - -#### IPFS Repo - -IPFS Repo is storage driver of IPFS, follows the [IPFS Repo Spec](https://github.com/ipfs/specs/tree/master/repo) and supports the storage of different types of files. - -#### Bitswap - -Bitswap is the exchange protocol used by IPFS to 'trade' blocks with other IPFS nodes. - -#### Files - -Files is the API that lets us work with IPFS objects (DAG Nodes) as if they were Unix Files. - -#### Importer - -Importer are a set of layouts (e.g. UnixFS) and chunkers (e.g: fixed-size, rabin, etc) that convert data to a MerkleDAG representation inside IPFS. - -