Architecture

A storage engine you can reason about.

LioranDB V2 is documented as a Rust-powered document database with a persistent storage path, WAL and checkpoint lifecycle, indexing paths, and multiple client transports. This page keeps implementation status visible.

Request flow

From client request to persistent state.

The public architecture direction describes this path. Exact behavior is version-sensitive and belongs in the maintained docs.

Pre-alpha / version-sensitive
01

Client request

JavaScript / TypeScript SDK, REST, or gRPC

02

Document API

Collections, filters, updates, and query execution

03

Storage paths

Primary storage plus configured secondary/text indexes

04

Durability

WAL and checkpoint lifecycle

05

Persistent state

Local or managed deployment storage

Engine properties

Keep implemented, tested, and planned distinct.

Implemented / pre-alpha

Rust engine

The V2 engine is documented as Rust-powered.

Configuration-dependent

Nodes and partitions

Benchmark artifacts show node and partition settings; do not infer general clustering availability.

Implemented / tested

WAL and checkpoints

WAL and checkpoint paths are present in the documented test surface.

Available in test paths

Indexing

Secondary and text indexes are documented; specialized raw-write tests may disable them.

Tested / pre-alpha

Recovery

Public artifacts include WAL replay and crash-recovery test paths.

Not asserted

Replication / failover

Do not treat multi-node configuration as automatic replication or failover without authoritative proof.

Operational boundaries

What to verify before production adoption.

AreaWebsite can establishVerify in docs / deployment
DurabilityWAL and checkpointing are configured in the supplied workload.Acknowledgement semantics, fsync behavior, and reopen guarantees.
TransportJavaScript, TypeScript, gRPC, and REST paths are described publicly.Endpoint details, auth, TLS, and compatibility for your version.
ScalingNodes and partitions appear in test configurations.Replication, placement, automatic failover, and supported topologies.
ObservabilityBenchmark and recovery artifacts are linked.Metrics, alerting, backups, restore drills, and incident procedures.
Review deployment options