forked from spring-projects/spring-data-neo4j
-
Notifications
You must be signed in to change notification settings - Fork 0
Deployment
Andreas Kollegger edited this page Sep 29, 2011
·
1 revision
Spring Data Neo4j can be integrated with your application using two different programming paradigms (load/store or delegation) in any of three different configurations. This diagram shows the deployment permutations, with current best practices in green, numbered to reflect overall best practice.

- Embedded Delegate - Using Neo4j as an embedded database is still the most high-performance and capable approach for development. This should be the default implementation path for all new projects.
- Server Load/Store - For server deployment, Neo4j is best accessed in a traditional load/store pattern. This is recommended only when it is desirable to have a physical separation of the application and persistence layers.
- Plugin - For advanced users already using a server deployment, adding domain specific plugins effectively allows for stored procedures to be used in Neo4j to optimize some access.