How to structure a neo4j-based system? by Gauthier Lemoine.
From the post:
Neo4j is a powerful, free and easy to use graph database. It is ideal to store, for example, relationships between people, items etc. It provides great features including a rich API (like easy traversal of graph, pathfinding), high level query DSLs (Gremlin, Cypher), a server featuring REST protocol, nodes and relationships indexing, ACID compliant, etc.
In this article, I give pointers to help you decide which topology to use for your Neo4j projects: embedded db? server?
This choice is important, because all options have advantages, disadvantages and limitations that have to be taken into consideration before implementing the system. However, one important thing is that whatever solution you use, the way the database is stored on disk is the same. It means that you can change your architecture without having to re-build a database.
Overview of choosing between installation options for Neo4j. Best to test your choice with realistic data as well.
I first saw this in a tweet from Peter Neubauer.