Use Neo4j with Clojure when relationships are the central model rather than an afterthought.
This section bridges the chapter overview and the detailed lessons below. For Java engineers, the practical question is how to handle Neo4j graph modeling and Clojure integration in Clojure code at the database boundary.
| Review focus | What to check |
|---|---|
| Graph fit | Use graph storage when traversals are the primary question. |
| Cypher | Keep query intent readable at the Clojure boundary. |
| Modeling | Represent relationship-heavy domains without forcing document shapes. |
Use the child lessons to move from concept to implementation. The section goal is to make the trade-off visible before the code hardens around a database assumption.