hamster21 / knot Goto Github PK

Afero has the benefit of writing to a local file system first, and lateron add a backend that is a shared file storage across a distributed network. It would also be possible to never even store files locally, but in Amazon S3 buckets instead. Or shove all files incoming through SSH to your NAS and work with them from there

There is a library to write go fuzzing tests call Go-fuzz, which would be useful to test if arbitrary file inputs can break the program. This can then be extended to build arbitrary objects in pretty random ways and see if they can take the application down.

Another important fuzzing test use would be network transmission of objects in the distributed network. The communication should gracefully handle arbitrary messages or 1s and 0s being sent to the participant

A knot object looks and feels like a git object. It has an identifier, a type and data assigned to it and can be stored as a file on the filesystem.

A knot object has to fulfill a number of requirements:

1. it must produce the same identifier for identical input
2. data of the file must not be changed
3. A persisted file stores the type as a string and the compressed file contents, separated by a newline character. The filename given is the identifier of the file content.

As a result the stored object is known to know, it can be discovered and is the basis for a content-addressable database/filesystem.