Explore the models / 8DB
Preserve what can be compared.
Represent partial order, joins and meets when the relationships among values matter to the application.
The decision / Specialist context
Some states can be ordered. Others are incomparable. Preserving that distinction can make a decision more faithful to the information behind it.
8DB’s lattice representation gives applications explicit partial order and supported joins and meets. Evaluate a concrete decision algebra rather than assuming every lattice is a replication system.
Explore the connected workflow ↗A commercial embedded database with local-first synchronization and CRDT merge behavior. Adjacent, not a lattice-query equivalent.
Read the source ↗Join-semilattice-based distributed programming, useful algebraic context.
Read the source ↗Figma’s engineering account demonstrates real conflict-resolution and collaboration needs. That is evidence for the application problem, not proof that customers want a generic lattice database.
Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application.
Typed joins, meets and frontiers give applications operations over bounds and alternatives. The documented time-series path uses interval enclosures, while other carriers represent confidence, labels and clocks with their own rules.
Connect · traverse · follow
Explore model ↗Group · relate · intersect
Explore model ↗Observe · window · analyze
Explore model ↗These connections show the models involved in the application design. Compare the supported combination and full workflow with a realistic alternative.
A document is represented through its sections and passages, with a route back to the source.
Conceptual application workflow. Qualify the supported operations, external tools, protection and persistence for the complete path. These diagrams are explanatory, not measured results.
The comparison is about preserving distinctions and applying the right algebra. A conventional database can store fields representing these objects; the work to define, validate and apply their semantics still belongs in the evaluation.
Property graphs and application-side algebra are plausible alternatives. Compare the complete representation and operator contract rather than assuming SQL rows or graph nodes cannot encode the values.
Neo4j graph conceptsCompare equivalent outputs and required guarantees, including the simplest single-product alternative where one exists. A specialist may remain the better fit when its operators, ecosystem or operational maturity are decisive. Combining native models becomes valuable when your actual question crosses them.
Modality performance / Evidence reviewed 18 September 2026
A reviewed timing for this specific job is not yet published here. The evaluation below defines the useful result and the measures that matter. Supporting measurements must match this model, its quality target and the required operating conditions.
Record build-time and serving memory separately, original and derived stored bytes, measured joules per completed job, and physical writes including indexing, compaction and recovery. A smaller representation does not by itself prove lower energy or longer device life.
Match correctness, freshness, durability and protection across alternatives. Encryption, authorization, adapters, network setup and output delivery belong in the complete-job comparison wherever required. No universal zero-overhead claim follows from these results.
Evaluate the result you need
Illustrative evaluation workflow · qualify the required operations and deployment
Test join/meet behavior on the admitted domain.
Preserve incomparable states and explicit policy choices.
Measure stored state and repeated merges where applicable.
We’ll use its output, quality and operating requirements to define a useful comparison.
Bind supported algebra to fixtures and validate one buyer problem. Only measure replicated convergence if the actual sync path uses the tested algebra.
Match the required correctness, freshness, durability and protection. Include ingestion, transformation, indexing and delivery in a complete-job result. Measure memory, stored bytes, energy and physical writes separately. Vendor descriptions establish offers, not independent rankings or 8DB compatibility.
Market review: 20 September 2026 · Reference revision 3.0. Linked benchmark results retain their own dates and scope. Standards are evaluation context, not an 8DB certification.
Verify the supported API/SDK, data format, persistence and indexing behaviour for the release you plan to use. Match the operation-by-modality protection profile and device qualification to the workload.
Explore the ideas and implementation context behind this capability.
Explore the ideas and implementation context behind this capability.
This reference explains 8DB’s public modality description with an explicit workload and selection criteria. It is a documentary review, not fresh execution of every operator or platform.
Public sources: 8DB modality scope; Neo4j graph concepts; the related articles above. Internal source leads and outstanding release checks remain in the editorial record.
Download this referenceBring the data shapes, input state, expected output and the systems you use today. Define a comparison around that complete job.
Discuss your workload