Explore the models / 8DB
Give a shared event its full cast.
Represent a relationship that involves several participants and their roles, without reducing its meaning to a list of independent pairs.
The decision / Specialist context
A sample, instrument, method and result form one experimental fact. Their roles and shared identity matter more than a pile of disconnected pairs.
8DB’s hypergraph representation offers a direct way to keep multi-participant facts alongside their measurements and documents. Compare role-aware queries and updates across equivalent representations.
Explore the connected workflow ↗First-class relations with typed participants and schema constraints.
Read the source ↗Established n-ary modeling through an explicit relation resource.
Read the source ↗W3C’s n-ary guidance explains the need to represent more than two participants and their roles. It also makes clear that several sound representations exist.
Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application.
A native n-ary fact retains its own identity and participants. This can simplify asking about the whole observation and its evidence without rebuilding the intended grouping from unrelated pairwise edges.
Filter · sort · project
Explore model ↗Observe · window · analyze
Explore model ↗Structure · search · trace
Explore model ↗These connections show the models involved in the application design. Compare the supported combination and full workflow with a realistic alternative.
Rows share a structure. A query selects the fields and records relevant to the question.
Conceptual application workflow. Qualify the supported operations, external tools, protection and persistence for the complete path. These diagrams are explanatory, not measured results.
Measure the work of creating, updating and recovering the same grouped fact, including role constraints and source retrieval. Avoid comparing one native lookup with an artificially inefficient graph query.
A property graph provides a realistic alternative through explicit observation nodes and relationships. Compare the representation, validation burden and query path rather than claiming that pairwise stores cannot express the fact.
Neo4j property graph modelCompare 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
Distinguish who did what in the shared fact.
Count work when one participant or role changes.
Include relation identity, indexes and attributes.
We’ll use its output, quality and operating requirements to define a useful comparison.
Verify role/cardinality enforcement and persistent relation identity; compare with TypeDB and an efficient relation-node graph, including group updates.
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 property graph model; 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