Developers
Code Structure
A map of the BrewFS repository.
brewfs/
├── crates/
│ ├── brewfs/ # CLI / daemon entry, mount command
│ ├── brewfs-fuse/ # FUSE request handling
│ ├── brewfs-vfs/ # VFS: paths, inodes, handles, read/write
│ ├── brewfs-meta/ # metadata clients: sqlx, redis, etcd, tikv
│ ├── brewfs-chunk/ # Chunk / Block / Slice engine, compaction, GC
│ ├── brewfs-object/ # object backends: local-fs, s3
│ └── brewfs-bench/ # benchmark entries
└── docs/ # design notesThe layering mirrors the architecture: each crate boundary is a layer boundary, which keeps the IO pipeline inspectable and testable.