diff --git a/src/docbkx/reference/neo4j-server.xml b/src/docbkx/reference/neo4j-server.xml index 00fde69b6..435657937 100644 --- a/src/docbkx/reference/neo4j-server.xml +++ b/src/docbkx/reference/neo4j-server.xml @@ -1,6 +1,6 @@ - + Neo4j Server Neo4j is not only available in embedded mode. It can also be installed and run as a stand-alone server diff --git a/src/docbkx/reference/performance.xml b/src/docbkx/reference/performance.xml index 09ceb369e..d9bcba8db 100644 --- a/src/docbkx/reference/performance.xml +++ b/src/docbkx/reference/performance.xml @@ -1,6 +1,6 @@ - + Performance considerations Although adding layers of abstraction is a common pattern in software development, each of these layers @@ -15,14 +15,14 @@ mapped to the graph with very little work. Building on this foundation, one can later explore other, more efficient ways to explore and process the graph - if the performance requirements demand it. - - - - - - - - + + Like any other object mapping framework, the domain entities that are created, read, or persisted + represent only a small fraction of the data stored in the database. This is the set needed for a + certain use-case to be displayed, edited or processed in a low throughput fashion. The main advantages + of using an object mapper in this case are the ease of use of real domain objects in your business + logic and also with existing + frameworks and libraries that expect Java POJOs as input or create them as results. + Spring Data Graph, however, was not designed with a major focus on performance. It does add some overhead to pure graph operations. Something to keep in mind is that any access of properties and relationships diff --git a/src/docbkx/reference/preface.xml b/src/docbkx/reference/preface.xml index 2db55f800..937cb355c 100644 --- a/src/docbkx/reference/preface.xml +++ b/src/docbkx/reference/preface.xml @@ -118,30 +118,25 @@ The provided samples, which are also publicly hosted on github are explained in . - - + + The performance implications of using Spring Data Graph are detailed in . This chapter also discusses + which usecases should be handled with Spring Data Graph and when it should not be used. + + + Being a Spring Data library, Spring Data Graph also implements a comprehensive template for interacting with the Neo4j graph database. + The Neo4jTemplate provides all basic graph operations as well as advanced querying with + Indexes, Cypher, Gremlin and Traversals with a convenient API. + + + As AspectJ might not come that easy to everyone, some of the core concepts of this Aspect oriented programming implementation for Java + are explained in . + + + How to consume the REST-API of a Neo4j-Server is the topic of . But Spring Data Graph can also + be used to create custom Extensions for the Neo4j Server which would serve domain model abstractions to a suitable front-end. So instead of + talking low level primitives to a database, the front-end would communicate via a domain level protocol with endpoints implemented + in Jersey and Spring Data Graph. + diff --git a/src/docbkx/reference/template.xml b/src/docbkx/reference/template.xml index 4179c40bf..cdb05e73a 100644 --- a/src/docbkx/reference/template.xml +++ b/src/docbkx/reference/template.xml @@ -1,6 +1,6 @@ - + Neo4jTemplate The Neo4jTemplate offers the convenient API of Spring templates for the Neo4j graph