Why Neo4J Sucks
- issues in cluster mode and scaling
- not built for distributed data (or even big data)
- issues with bulk loading, indexing (e.g. range, sort, etc), slow upsert
- bottleneck with large volume of writes due to slave/master topology
- extremely expensive to replicate entire graph across each node
- confusing license terms for production use
- heap allocation and GC cause out-of-memory errors (buggy configs)
- practically only useful for small dataset reads that require visualization
- not appropriate for high read/write/index searches on KG
- re-indexing can be very slow, require elasticsearch/solr as added dependency step
- deceptive marketing ploys that provide for flawed benchmarks
