How kushall-07/forgedb works
ForgeDB is an early-stage, single-node key/value storage engine, not a network server. Its demonstrated workflow is a command-line run that opens the WAL-backed store, writes and reads a value, closes it, then reopens the same data directory and reads the recovered value. The storage path separates the Store API, WAL-backed orchestration, in-memory ordered state, and durable log. The README is empty; the tree and sampled source do not establish server, replication, or configuration workflows, so they are omitted.
Main entry points: memstore.go MemStore · wal.go WAL · main.go CLI entry · memtable.go MemTable
Components 11
Demo entry
- CLI entry
cmd/forgedb/main.go - Demo workflow
cmd/forgedb/main.go - Logging
internal/metrics/logger.go
Storage engine
- Store contract
internal/storage/storage.go - MemStore
internal/storage/memstore.go - MemTable
internal/storage/memtable/memtable.go - Skip list
internal/storage/memtable/skiplist.go
Persistence
- WAL
internal/storage/wal/wal.go - Record codec
internal/storage/wal/record.go - WAL file
Other components
- Operator
Connections 13
- Operator → CLI entry: runs
- CLI entry → Demo workflow: calls
- CLI entry → Logging: logs startup
- Demo workflow → MemStore: opens store
- Demo workflow → Logging: logs results
- MemStore → Store contract: implements
- MemStore → WAL: opens and replays
- MemStore → MemTable: creates and applies
- MemStore → WAL: appends and syncs
- MemStore → MemTable: reads and mutates
- MemTable → Skip list: stores entries
- WAL → Record codec: encodes and decodes
- WAL → WAL file: reads and writes