Having been using IPFS since 2017, I have come across very limited discussions and documentation on the MFS(Mutable File System).
Although https://docs.ipfs.io/guides/concepts/mfs/ and this this thread gives minmal context, I believe there is more information required to understand MFS adequately for developers to make key decisions in using MFS.
So, here are some of my questions:
1. Are there any design documents made available for MFS?
For e.g., how the in-memory file system works, how the state change are committed back to DAG, how the File and Directory are being mapped to their CIDs to maintain trail of changes etc.
2. Can MFS be consumed by applications, compared to directly consuming IPFS through the HTTP APIs? If so, what are the potential trade-offs?
A trade-off could not necessarily be a functional, but also inherent features of IPFS that could be missed out, by directly pointing all the changes to MFS maybe?
3. Although MFS is accessible directly from the
ipfs cli, what is the current production-readiness compared to that of IPFS HTTP APIs?
Can MFS be used in a file sharing application per se? Also, it would be nice to mention a few applications adopting MFS, if any.
I thank in advance for the answers from the community. Cheers to IPFS.