Content-addressable union file system built on Fuse, Hyperlog, LevelDB and Node

Without looking at the code, I assume each file is stored as a binary blob with a hash, snapshot and volume id. This would allow you to keep identical files only once.

The last paragraph is conjecture. However the idea is that the filesystem is arranged so that it only stores the difference(or a different version) of the file.

A content-addressable filesystem associate each path to the hash of its content, and then keeps a separate mapping of each hash to a content. Which means that if two files are identical (= have the same hash), then the content is only stored once.

A union filesystem is a filesystem that is organised as a set of "layers". You have a normal filesystem at the bottom, above it you have a set of layers, where each layer only stores the files that have changed (each time you create a snapshot, the filesystem creates a new layer).

In practical terms, you have a filesystem where taking snapshots and reverting to older snapshots is very efficient.

Or, in other words, a filesystem that behaves like a git repository.