Architecture
Architecture Overview
Six clear layers from FUSE to object storage — not a black box.
BrewFS separates filesystem semantics, metadata transactions, object-block storage, and background maintenance into clear layers that can be inspected, benchmarked, debugged, and extended.
The six layers
| # | Layer | Responsibility |
|---|---|---|
| 01 | CLI / Daemon | Starts BrewFS, loads configuration, mounts, operational commands |
| 02 | FUSE | Receives kernel filesystem operations, maps them to VFS operations |
| 03 | VFS | Path lookup, inode management, file handles, rename, truncate, read, write |
| 04 | Metadata | Namespace, directory entries, inode attributes, chunk metadata, slice descriptors, transactions |
| 05 | Chunk Engine | Chunk / Block / Slice layout, read/write mapping, sparse holes, compaction, GC |
| 06 | Object Backend | Stores file data as object blocks on LocalFS or S3-compatible storage |
Applications / Agents
↓ POSIX-like FUSE
VFS Layer
↓
Metadata Layer · Chunk Engine
↓
Object Backend (LocalFS / S3)Continue with the Read & Write Path.