Graph & Time-Travel
GraphTemporalTime Travel
AetheriusDB treats relationships and history as first-class parts of the same engine that serves your relational SQL. You don’t bolt on a separate graph database or a separate audit store — the same tables are queryable as a graph, and every committed state stays addressable on a timeline.
Why it matters
Section titled “Why it matters”Relationships and history are usually where a stack sprouts extra systems — a graph database to traverse, an audit log to keep, a warehouse to snapshot. Folding both into the relational engine means one copy of the data, one query language, and no sync jobs between stores that drift apart.
- One dataset, two lenses — query the same tables as rows or as a graph; no ETL into a separate graph store.
- History for free — every committed state stays queryable, so audit, point-in-time analytics, and “what did this look like last Tuesday?” need no separate audit table.
- Referential integrity that never blocks a write — child rows can arrive before their parents and reconcile in the background.
How fast it is
Section titled “How fast it is”- A graph hop is a direct link, not an index probe. Traversing a relationship follows a stored pointer between related rows, so multi-hop queries stay fast where a repeated join-and-lookup would slow down.
- Time travel with no replay. Querying a past instant resolves a snapshot directly — there’s no log to replay to reconstruct history.
In this section
Section titled “In this section”- Graph-Relational Duality — declare
your tables as graph nodes and edges, then query them with both standard SQL
and ISO SQL/PGQ
MATCHpatterns. - Native Graph Traversal — how a graph hop runs as a direct link between related rows instead of an index probe.
- Spectral Foreign Keys — referential
integrity that never blocks an
INSERT; child rows can arrive before their parents and reconcile in the background. - Temporal Tables & Events — query any
past state with
FOR SYSTEM_TIME AS OF, and detect event patterns withMATCH_RECOGNIZE. - Chrono Replay Debugger — a timeline slider that rewinds a running application to any past instant for debugging.
- Storage Lifecycle — old data tiers down to cold storage automatically and stays queryable through time travel.
Each feature page carries an availability badge (Stable / Opt-in / Beta / Roadmap) so you always know what you can rely on in production today.