Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • 1
    Although your linked article is good at explaining the conceptual constructs of a graph, I don't think it actually answers the question: how does a graph database store the data? The article explains how data are related and described, but not how they are stored. Eg) "a graph database stores connections alongside the data in the model" - so? In a database record I store a foreign key value right alongside the entity's property values in the same record. So what's different in the graph db? Commented Aug 27, 2019 at 5:49
  • 1
    Eg2) "Accessing nodes and relationships in a native graph database is an efficient, constant-time operation and allows you to quickly traverse millions of connections per second per core." - yes, but why do graph dbs excel at this, over and above relational dbs? How, exactly, are they implemented to facilitate this performance? Commented Aug 27, 2019 at 5:50