Database Reference
In-Depth Information
kind of queries that you can access and shown you the right direction should you choose to
continue down this path.
9.5.3. Traversals
Once again we find ourselves unable to cover everything, and unfortunately, graph tra-
versals within SDN is one area we can't cover in depth here. Not to be left out completely,
however, we will point out that the traversal framework you encountered in
chapter 4
is
also accessible from within SDN. If you hadn't already guessed it, there's an annotation
for it—namely,
@GraphTraversal
—as well a whole repository interface
(
TraversalRepository
) dedicated to helping with traversals involving domain entit-
ies.
9.6. Summary
In this chapter we introduced the Spring Data Neo4j (SDN) framework that provides a
variety of tools that allow you to use a standard POJO-based domain model backed by the
powerful Neo4j database. You saw how easy it was to annotate your POJOs in a manner
that allowed SDN to seamlessly take care of all the mapping logic between your domain
model and the underlying graph primitives.
You learned how to make use of both the Neo4j template- and repository-backed imple-
mentations to perform CRUD and indexing operations on your entities, as well as how to
define and execute queries involving node entities.
Youalsolearnedalittlebitmoreaboutthetwomainobject-graphmappingmodesavailable
to you: simple and advanced. You discovered that although they both ultimately do the
same thing, they take quite different approaches to accomplishing this, which can have
memory and performance implications that need to be considered.
As we stated in the
section 9.1.4
, we've only been able to scratch the surface of what SDN
can do. We hope that this chapter has served to whet your appetite and that you'll continue
to look further into what SDN has to offer. Next up, you'll delve into understanding the
differences between using Neo4j in embedded versus server mode.
