anchor.diff:  === Migrating from OGM 1.x to 2.x
   
   OGM 2.0 introduces a few minor changes that you will need to take into account when migrating an existing 1.x application.
  -These changes are a consequence of the support for different database drivers. In 1.x, the only connectivity to Neo4j was over Http, and the code reflected this in its design, as it closely coupled the session with the Http client.
  +These changes are a consequence of the support for different database drivers. In 1.x, the only connectivity to Neo4j was over HTTP, and the code reflected this in its design, as it closely coupled the session with the HTTP client.
   In 2.0 this design is no longer appropriate, and the connection to the database is abstracted via a Driver interface.
   
   This has an impact on your application code in two areas, testing (discussed above) and session configuration.
  
positive.code: 
  === Using an in-process server for testing
  
  If you want don't want to use the Embedded Driver to run your tests, it is still possible to create an in-process Http server instead.
  Just like the Embedded Driver, a TestServer exposes a GraphDatabaseService instance which you can use in your tests.
  You should always close the server when you're done with it.
  
  
negative.code: new SessionFactory(configuration, packages...);
  ----
  
  _Note: Please see the section below describing the different ways you can pass credentials to the HTTP Driver_
  
  ==== Configuring the Bolt Driver
  
  The Bolt Driver connects to and communicates with a Neo4j server via the binary Bolt protocol. If your application is running in client-server mode, you must use either the HTTP or Bolt driver.
  
  .ogm.properties
  [source, properties]
  