Look in a different way if you need scale - this is not suitable
Use Cases and Deployment Scope
Scaling is a huge issue in Neo4j. Clusters are supposed to allow horizontal scaling and they say they support billions of nodes, but in fact, a database with ~600 mil nodes and 1.5TB in size is barely manageable. Backups slow, count() times out, server restart will take hours (!!!!). And 2GB hard transaction limit is another hard candy of a clustered mode, requiring to use things like apoc.iterate for long updates, making them impossible to rollback in case something goes wrong (apoc.iterate commits results on the go).
So - if you need scaling, think twice.
Pros
- Graph traverse.
Cons
- Scaling and clustering.
- Transactions limitations.
- Performance on millions of data.
- Backup and restore.
Most Important Features
- Graph traverse.
Return on Investment
- Positive: Less complex queries on graph structures, than in relational databases.
- Negative: maintenance is a huge deal, things doesn't work and break, requiring lengthy restore operations.


