Database Reference
In-Depth Information
Now, let's move ahead and discuss scenarios where we can think of leveraging either of
the deployment models.
Scalability and High Availability are one of the critical
non-functional requirements
(
NFR
s) for most of the enterprise systems and that is sufficient reason/argument to deploy
Neo4j as a REST-based server and then developing REST clients to perform CRUD and
search operations. Also this is one of the most common forms of deployment models for
the production environments as it provides scalable and highly available database systems
for your enterprise applications.
But there are applications where quick and faster development is a priority or you do not
want to have dedicated hardware or a separate process to be deployed, which may be too
costly due to many obvious reasons, and in all those cases, Neo4j as an embedded server
would be the best choice.
Considering the advantages/disadvantages and the scenarios, we would conclude that
there is no single deployment model which works the best or is applicable for all scenari-
os. So based on the needs of your use case, decide upon the appropriate deployment mod-
el. It is good to have the requirements and vision of your application drive the selection of
deployment models and not the other way round.
