Look in a different way if you need scale - this is not suitable
August 02, 2022

Look in a different way if you need scale - this is not suitable

Anonymous | TrustRadius Reviewer
Score 2 out of 10
Vetted Review
Verified User

Software Version

Enterprise Edition (on-premise)

Overall Satisfaction with Neo4j

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.
  • Graph traverse.
  • Scaling and clustering.
  • Transactions limitations.
  • Performance on millions of data.
  • Backup and restore.
  • 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.

Do you think Neo4j delivers good value for the price?


Are you happy with Neo4j's feature set?


Did Neo4j live up to sales and marketing promises?


Did implementation of Neo4j go as expected?


Would you buy Neo4j again?


Small to medium data sets (up to tens of millions of nodes) work acceptably.
Big data sets - hundreds of millions - look another way.