Use this page as the entry point for low-level architecture details. Component overview and usage pages stay with each component; this section collects the deeper internal design pages in one place.
Component Map
Section titled “Component Map”| Component | Architecture focus |
|---|---|
| AkkEngine | Write path, read path, storage components, lifetimes, and durability boundaries. |
| SST | Sorted-table files, lookup and scan paths, flush, compaction, recovery, and Manifest boundaries. |
| Manifest | Append-only lifecycle metadata, SST state, checkpoints, Blob references, cluster breadcrumbs, and recovery. |
| API Server | Transport backends, framing, request limits, and server lifecycle. |
| Cluster | Runtime roles, routing, replication frames, ACK behavior, and operational boundaries. |
| VersionLog | History storage, segment indexes, recovery, retention, and Blob interaction. |
Reading Order
Section titled “Reading Order”Start with AkkEngine Architecture when you want the storage path: WAL, MemTable, SST, Blob, VersionLog, and snapshots.
Read SST Architecture when you need the persistent sorted-table layout, flush and compaction behavior, or the boundary between current-state SST data and VersionLog history.
Read Manifest Architecture when you need to understand how recovery finds live SST files, how compaction commits become durable, or how checkpoint, Blob, and Cluster metadata are recorded.
Read VersionLog Architecture when you need point-in-time reads, history, rollback, retention, or MVCC boundaries.
Read API Server Architecture or Cluster Architecture when the engine is exposed outside the process or replicated between nodes.