Database Reference
In-Depth Information
rather to the embedding of the Neo4j engine (the classes and associated processes) that run
and manage the Neo4j database directly.
10.2.1. Core Java integration
The most common embedding scenario involves embedding Neo4j directly within a Java-
based application, as shown in
figure 10.2
.
Figure 10.2. Typical Java-embedded deployment scenario, where the Neo4j libraries are embedded in the Java
application
The core Neo4j classes that are packaged and run within your application do more than
simply act as a mechanism for funneling data backward and forward between the physical
data store and your application. The classes themselves form an integral part of the whole
database offering, handling, for example, all the logic and in-memory requirements neces-
sary to perform traversals, queries, and so on. From an application architecture perspect-
ive, this is interesting because it means that the logic controlling your application, as well
as that controlling the database, needs to be able to live in harmony within the same JVM
space. The implications of this cohabitation are covered in
section 10.4
, but for now it's
enough to know that the embedded mode means that both your application and Neo4j code
will be residing and operating within the same JVM.
Embedded mode requires that the appropriate libraries (JAR files) are bundled or made
available to your application when it starts up. It's then your application's responsibility
