Skip to content

Commit a991788

Browse files
authored
Refactor graph database types section for clarity and conciseness. Clarify description of ArcadeDB as a property graph database (#331)
1 parent 0def69d commit a991788

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

src/main/asciidoc/core-concepts/graphs.adoc

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -44,20 +44,18 @@ with:
4444
[discrete]
4545
==== Graph Database Types
4646

47-
There are two common types of graph databases,
48-
which are instances of directed graphs,
49-
but differ by the underlying objects of vertices and edges:
47+
There are two prevalent data models for graph databases (both usually directed):
5048

51-
1. **Knowledge Graph**: the underlying vertex and edge objects are (just) labels.
52-
2. **Property Graph**: the underlying vertex and edge objects are (labeled) documents.
49+
1. **Triple store (RDF graph)**: data is represented as subject–predicate–object triples; all facts are uniform triples and semantics are standardized (RDF, RDFS/OWL, SPARQL).
50+
2. **Property Graph**: vertices and edges carry labels (types) and arbitrary key/value properties directly attached to them.
5351

54-
ArcadeDB is a property graph, which means a vertex or edge consists of an identifier (RID),
55-
a label (type), and properties (document), in addition to the ordered pairs of endpoints.
56-
The latter are here vertex properties of incoming and outgoing edges, instead of edge properties of ordered vertex pairs, for technical reasons.
52+
ArcadeDB is a property graph database: vertices and edges have labels and can store arbitrary key/value properties, supporting compact storage, fast traversals, and flexible schema evolution within its multi-model, document‑oriented engine.
53+
54+
Practically, a vertex or edge consists of an identifier (RID), a label (type), and properties (document), plus ordered endpoint references. The latter are here vertex properties of incoming and outgoing edges, instead of edge properties of ordered vertex pairs, for technical reasons.
5755

5856
[discrete]
5957
==== Why (Property) Graph Databases?
6058

6159
- The modeled domain is already a network.
6260
- Fast traversal of relations instead of costly joins in relational databases.
63-
- Naturally annotated edges instead of inconvenient reification in knowledge graphs.
61+
- Naturally annotated edges instead of inconvenient reification in RDF graphs.

0 commit comments

Comments
 (0)