anchor.diff:  The Embedded Driver connects directly to the Neo4j database engine. There is no server involved, therefore no network overhead between your application code and the database.
   You should use the Embedded driver if you don't want to use a client-server model, or if your application is running as a Neo4j Unmanaged Extension.
   
  -*Please note, if you want to use the Embedded driver in your deployed application, you will need to explicitly declare the required driver dependency in your project's pom file:
  -*
  +Please note, if you want to use the Embedded driver in your deployed application, you will need to explicitly declare the required driver dependency in your project's pom file:
  +
   [source,xml]
   ----
       <dependency>
  
positive.code: </dependency>
  ----
  
  .Gradle dependencies for Neo4j OGM
  [source,xml]
  ----
  dependencies {
      compile 'org.springframework.data:spring-data-neo4j:{version}'
  }
  ----
  
  
negative.code: - Http driver
  - Embedded driver
  
  By default, Spring Data Neo4j will try to configure the driver from properties file `ogm.properties`, which it expects to find on the classpath.
  In many cases you won't want to, or will not be able to provide configuration information via a properties file.
  In these cases you can configure your application programmatically instead, using a `Configuration` bean.
  
  The following sections describe how to setup Spring Data Neo4j using both techniques.
  
  ==== Configuring the Http Driver
  
  