distributed filesystems

go-ipfs

23 May 2020Last Commit9697 (1641/yr)Github Stars936Issues

IPFS is a global, versioned, peer-to-peer filesystem. It combines good ideas from previous systems such as Git, BitTorrent, Kademlia, SFS, and the Web. It is like a single BitTorrent swarm, exchanging git objects. IPFS provides an interface as simple as the HTTP web, but with permanence built-in. You can also mount the world at /ipfs.

For more info see: https://docs.ipfs.io/introduction/overview/

Before opening an issue, consider using one of the following locations to ensure you are opening your thread in the right place:

xtreemfs

No Repo
* XtreemFS is a fault-tolerant distributed file system for all storage needs.

tahoelafs

No Repo
* secure, decentralized, fault-tolerant, peer-to-peer distributed data store and distributed file system.

swift

No Repo
* A highly available, distributed, eventually consistent object/blob store.

sheepdog

No Repo
* A distributed Blockdevice, Rest, QEMU and distributed Filesystem storage.
* A Secure Distributed File System built for offline operation.

openafs

No Repo
* Distributed network file system with read-only replicas and multi-OS support.

moosefs

No Repo
* Fault tolerant, network distributed file system.

mogilefs

No Repo
* Application level, network distributed file system.

lustre

No Repo
* Parallel distributed file system, generally used for large-scale cluster computing.

leofs

No Repo
* Unstructured object/data storage and a highly available, distributed, eventually consistent storage system.

hdfs

No Repo
* Distributed, scalable, and portable file-system written in Java for the Hadoop framework.

glusterfs

No Repo
* Scale-out network-attached storage file system.

drbd

No Repo
* Distributed Replicated Block Device.

ceph

No Repo
* Distributed object store and file system.

camlistore

No Repo
* A set of open source formats, protocols, and software for modeling, storing, searching, sharing and synchronizing data.