Database Reference
In-Depth Information
Chapter 10. Neo4j: embedded versus server mode
This chapter covers
• The two main usage modes: embedded and server
• How to weigh the pros and cons of each mode
• Getting themostoutofyourserverwithCypher,plugins,extensions, andstreaming
Nowthatyouhaveagoodunderstandingoftheapproachesandpracticaltechniquesrequired
to design and model your world in the Neo4j graph database, it's time to look at the two
main ways you can run Neo4j, namely in embedded or server mode. Before embarking on
any serious Neo4j project, one of the first things you'll need to do is make a decision about
which mode you ultimately want to run in production. This choice will influence, among
otherthings,whatlanguagesandarchitecturallandscapesyourapplicationcanoperatewith-
in, so it's an important consideration.
You'll be pleased to know that, regardless of which mode you choose, everything you've
learned so far is still applicable. The semantics around using each mode are quite different,
and it's important to understand what these are and how to use them appropriately, but the
core principles remain the same.
In this chapter, we'll cover why there are two modes, what the main differences are, and
whatthetrade-offs,pros,cons,andimplicationsareofusingeachmode.Let'sgetintolearn-
ing mode and get going!
10.1. Usage modes overview
WhenNeo4jwasfirstreleased,itwasaimedsquarelyattheJava-basedworld,andbackthen
it only supported the
embedded mode
. Within the embedded mode setup, your Java applica-
tionandnewshinyNeo4jdatabasewerehappilybundledtogetherasasingledeployableen-
tity, and together they went forth to conquer the brave new world of interesting graph-based
problems.
The broader capabilities and functionality of Neo4j, however, did not go unnoticed by other
languages, which were also interested in being able to leverage and make use of this new
