Courtesy of Google Images

How Do You Know If a Graph Database Solves the Problem?

Jennifer Reif
Aug 8, 2018 · 9 min read

Self-Evaluation: Are You Desperate to Use a Graph Database on Anything?

When Are Graph Databases NOT a Good Fit?

1. Where data is disconnected and relationships do not matter.

2. Where optimizing for writing and storing data and do not need to read or query it.

3. Where core data objects or data model stay consistent and data structure is fixed and tabular.

4. Where queries execute bulk data scans or do not start from a known data point.

//Query 1:
MATCH (n)
WHERE n.name = 'Jennifer'
RETURN n
//Query 2:
MATCH (n:Person {name: ‘Jennifer’})-[r:KNOWS]->(p:Person)
RETURN p

5. Where you will use it as a key-value store.

6. Where large amounts of text or BLOBS need to be stored as properties.

Recap

When are Graph Databases a Good Fit?

Courtesy of Google images

Conclusion

Resources

Neo4j Developer Blog

Developer Content around Graph Databases, Neo4j, Cypher, Data Science, Graph Analytics, GraphQL and more.

Jennifer Reif

Written by

Jennifer Reif is an avid developer and problem-solver. She enjoys learning new technologies, sometimes on a daily basis! Her Twitter handle is @JMHReif.

Neo4j Developer Blog

Developer Content around Graph Databases, Neo4j, Cypher, Data Science, Graph Analytics, GraphQL and more.