NoSQL Data Models

Understanding data stores for your application.

(Neo4j) –[:IS_A]–> (NoSQL Database)
Not only SQL, but modern choices which excel at answering different kinds of questions.

Average income? Ask an RDBMS
Shopping cart? Use a Key-Value Store
How did you get here? Ask a graph
(A Graph Database) –[:TRANSFORMS_A]–> (RDBMS)

Topple the stacks of records in a Relational Database while keeping all the relationships, and you’ll see a graph. Where an RDBMS is optimized for aggregated data, Neo4j is optimized for highly connected data.
(A Graph Database) –[:RELATES_A]–> (Key-Value Store)

A Key-Value model is great for lookups of simple or even complex values. When the values are themselves interconnected, you’ve got a graph. Neo4j lets you traverse quickly among all the connected values.
(A Graph Database) –[:NAVIGATES_A]–> (Document Store)

The container hierarchy of a Document Database accommodates nice, schema-free data that can easily be represented as a tree. Which is of course a graph. Refer to other documents (or document elements) within that tree and you have a more expressive representation of the same data that you can easily navigate with Neo4j.