Database Reference
In-Depth Information
Figure 10.7. Two possible deployment scenarios for the social network application: embedded and server modes
With the embedded mode, the lifecycle, memory, and processing capabilities of the applic-
ation (social-movie.war) are tightly bound to those of the embedded Neo4j database; with
the server mode, there are separate JVMs handling the application and the Neo4j database
(JVM 1 and JVM 2). In the server version, the administration application is separated out
into its own PHP-based web client, even further decoupling the main components and ap-
plications from one another.
In embedded mode, your application and Neo4j share the same JVM and therefore share
the same Java heap; they're subject to the same garbage collection (GC) cycle and will es-
sentiallyliveanddietogether.IfyourapplicationcausesortriggersGCinembeddedmode,
this may impact the performance of Neo4j. What may appear to be Neo4j reacting slowly
may simply be Neo4j waiting for a GC pause to complete. There may also be cases when
you'll want to tune the Neo4j JVM and GC parameters separately from those of your ap-
