Architecture Overview - CefasDB Docs

Documentation excerpt

CefasDB is structured as a set of narrow layers. The transport layer accepts requests. The catalog describes tables. The storage layer commits items and indexes. The query planner chooses operators. The plugin registry supplies specialized behavior. Raft and multi-raft wrap the write path when replication is enabled.

The important invariant is that the table mutation and built-in index mutation are part of the same storage batch. A committed write cannot update the primary record without updating the built-in indexes that describe it.

Reads prefer the cheapest available route. A primary-key lookup is direct. A partition query is range-oriented. A secondary index query follows pointers. A plugin-backed query can ask a plugin for candidates before applying exact filters.

Each call carries a single consistency knob, the Consistency enum from cefas.v1.Cefas: