Engine design

Architecture

How AsaDB carries SQL from a local browser or CLI to persistent storage.

SQL text / uploaded SQL stream ↓ Reservoir admission, durable spool, single-writer queue ↓ lexer and parser ↓ Prolog AST, planner, executor, catalog control ↓ record manager / persistent B+Tree ↓ bounded buffer pool ↓ 4 KB page manager and disk files

Entry points and SQL core

asadb.pl ↗ starts the CLI. asadb_web.pl ↗ starts the local HTTP layer used by AsAPanel. asa_portable.pl ↗ dispatches portable panel, web, CLI, REPL, and help modes. The main asadb_core.pl ↗ module owns boot, catalog, lexer/parser, AST execution, SQL-level transactions and permissions, results, recovery hooks, and simple planning decisions.

Clear boundaries

Storage, indexing, page I/O, caching, web operation, and queue pressure are separate components. Reservoir controls pressure before SQL enters the normal engine. The optional Process Guardian remains outside SQL execution, Reservoir, and database storage.

See the upstream architecture document ↗, then continue with the storage guide and the complete source map.

← Back to documentation