Open pekkanikander opened 10 years ago
While CEPH and IPFS an abstract storage layer of sorts, distributed accross several nodes, they are aiming towards different things (datacenter-grade storage layer vs. fully distributed, end-user, opportunistic access and retrieval storage layer). That said, I have not much experience with Ceph anyways.
@pekkanikander I think these two projects could take a lot of aspects from each other. IPFS is easy to configure and access while CEPH is NOT. CEPH has CRUSH! an algorithm that I think would be an excellent addition to an IPFS-cluster. Consider automatic pinning of blocks/objects . Say that you want a data set to be "permanent", tell the IPFS-cluster how many copies you want to have, of that set, and with CRUSH!, it would be chunked and pinnned, across your IPFS instances. CEPH also seems to use more resources than IPFS. You could use a cryptographic hash as a link to the IPFS cluster through PubSub to control who gets access or notification about the data. CEPH also has some interesting ways to access your data, which would be very useful for IPFS. Much like Tahoe-LAFS https://tahoe-lafs.org/trac/tahoe-lafs.
In terms of non-commercial use consider using ActivityPub with a social interface and using the data supported by IPFS to share resources with others.
Only my thoughts, if any of these ideas have been realized, by all means, please let me know.
Considering scalability, I'm wondering how IPFS compares to Ceph RADOS? RADOS is clearly able to store mutable data on any keys, but AFAICS it would be trivial (though not necessarily optimal) to implement IPFS on the top of RADOS.
Cf. e.g. http://ceph.com/community/more-than-an-object-store/
Any thoughts?