How fix-project/fix works
Main Components
a) Core Runtime System:
• Following sub-components from src/runtime:
• Executor (executor.cc/hh)
• Evaluator (evaluator.cc/hh)
• Scheduler (scheduler.cc/hh)
• ELF Loader (elfloader.cc/hh)
b) Storage Layer:
• Below the runtime system
• Components from src/storage:
• Repository (repository.cc/hh)
• Runtime Storage (runtimestorage.cc/hh)
• Hash Table (hash_table.cc/hh)
• FixCache System (fixcache.hh)
c) WebAssembly Runtime:
• On the right side
• Components from src/wasm-rt
• Connection to the core runtime
d) Component System:
• On the left side
• Object and Program handlers from src/component
e) HTTP Interface:
• At the top
• HTTP client/server components from src/http
Relationship Flows
• External requests → HTTP Interface
• HTTP Interface → Runtime System
• Runtime System → Wasm Runtime (for execution)
• Runtime System → Storage Layer (for object persistence)
• Runtime System → Component System (for object handling)
Special Elements
a) File System Integration:
• .fix repository structure:
• data/
• labels/
• pins/
• relations/
b) Build System:
• CMake configuration flow
• Connection to wasm-toolchain
Architectural Patterns to Highlight
• Component-based architecture
• Event-driven execution model (shown by eventloop.cc/hh)
• Object storage and caching system
• Modular design with clear separation of concerns
Implementation Details
• Resource limits handling
• Dependency graph management
• Concurrent execution capabilities
• Object handle system
External Dependencies
Connections to:
• BLAKE3 (third-party)
• Abseil (third-party)
• Wasm toolchain (external)
Testing Infrastructure
A section showing:
• Unit tests
• End-to-end tests
• Benchmark system
• Flatware tests