Re:Dgraph is a next generation graph database with GraphQL a...
by mosselman on Sunday June 19, 2016 @05:19PM
(#11934720)
Thank you for the clarification.
How would Dgraph compare to Neo4j for example?
I have looked at google cayley's as well (looked through the docs) and I must say I liked the premise. Do you think the support of multiple databases has degraded the database's performance?
Re:Dgraph is a next generation graph database with GraphQL a...
by woodcut on Sunday June 19, 2016 @05:27PM
(#11934765)
I worked on implementing a backend for google cayley, the issue is the iterators abstract how a backend actually works so it becomes harder to optimise without introducing tighter coupling, also imho effort is better spent on more important things like high availability etc. I haven't touched it in a while so i can't speak re. its performance today.
I've never worked with Neo4j but it's a stable and matured product with numerous large scale deployments, enough said. :)
Re:Dgraph is a next generation graph database with GraphQL a...
by bogomipz on Monday June 20, 2016 @01:29AM
(#11936214)
Could you elaborate? I was under the impression that Cayley supported MongoDB and LevelDB as backends:
http://google-opensource.blogspot.com/2014/06/cayley-graphs-...
Re:Dgraph is a next generation graph database with GraphQL a...
by woodcut on Monday June 20, 2016 @04:39AM
(#11936823)
yeah cayley supports numerous backends that do have replication such as mongodb and postgres or cockroach db. The issue being that a complex query consists of multiple stages like 'friends of friends of friends'. So if you're using a remote backend iterating over the result of a query then recursively making new queries results in performance that is at best poor.
I'm pretty positive about this project, it's like google cayley if it hadn't have got bogged down in trying to support numerous database drivers. It'll show its strength if and when it implements raft and reaches a stable production state.