Neo4j basically only runs in single-node mode with optional replication for failover. You can't really do distributed graph queries without losing all the advantages of a graph db (namely following links is constant-time).
I haven't looked at DGraph much but if they are trying to store the graph in a distributed manner then the use-cases will be different.
From experience, using GrapheneDB/Neo4j takes much less than 1/10th of an engineer / year to manage, so unless your data doesn't fit in 1 box you'd be better off with Neo4j
I haven't looked at DGraph much but if they are trying to store the graph in a distributed manner then the use-cases will be different.
From experience, using GrapheneDB/Neo4j takes much less than 1/10th of an engineer / year to manage, so unless your data doesn't fit in 1 box you'd be better off with Neo4j