Concepts
The runtime, consistency, table, storage, indexing, and streaming concepts behind the current single-node NYXDB engine.
These pages describe the behavior of the current engine, not the future state in
an architecture decision record. The supported deployment is one nyxdb
process running EngineHost with local storage.
Distributed roles, cross-node replication, high availability, failover, multi-statement transactions, and MVCC are not production capabilities in the current revision. See the engine capability matrix for the authoritative status of every public surface.
Runtime architecture
What runs in the single process and where the product boundary sits.
Direct application access
Publish typed read-only queries for browser and platform clients without an application query proxy.
Consistency
Statement visibility, read-your-writes, durability, and unsupported transactions.
Tables
Append, keyed, and attribute table models.
Storage
Committed tail, immutable NYXP parts, compaction, and policies.
Indexes
Bitmap and skip indexes, plus committed-tail coverage.
Vector search
vector(N), HNSW, filtered ANN, and exact fallback.
Streams
Ordered local change delivery and its continuity boundary.
Streaming reads
Initial snapshot, live deltas, and historical follow.
PSI
The shared stream:key routing primitive.
Projections
Current-state reconstruction for attribute tables.
Transforms
Experimental in-process stream-to-table pipelines.
Status vocabulary
The documentation uses the same vocabulary as the engine:
| Status | Meaning |
|---|---|
| Implemented | Executable in the current profile, covered by conformance tests, and intended to remain compatible. |
| Experimental | Executable and tested, but its interface or operational contract may still change. |
| Design-only | Described by an ADR or roadmap, with no usable runtime surface. |
| Stub | A placeholder exists but does not implement the advertised behavior. |
| Unsupported | Not provided by the current revision. |
An accepted ADR records a design decision. It is not, by itself, proof that the feature is implemented.