Re:Cayley – An open-source graph database
by StreamBright on Saturday April 08, 2017 @02:53PM
(#14068357)
Do you have documentation how to get started with Cayley? I was reading this -> https://cayley.io/1-getting-started/ A little bit too short for my taste. :)
Re:Cayley – An open-source graph database
by scalatohaskell on Saturday April 08, 2017 @05:16PM
(#14069083)
Whats the difference between Cayley and lets say OrientDb / ArangoDb ?
One of the difference is Cayley/Arangodb doesn't provide an index free adjacency (a moot point as I'm not sure if it is even worth considering as hash index are quite fast and gives O(1)) while OrientDb has IFA.
If you want help with a Cassandra backend, hit me up (my HN username @ gmail or apache)
Emailed!
Re:Cayley – An open-source graph database
by chaostheory on Saturday April 08, 2017 @06:38PM
(#14069452)
What's the difference between Cayley and Neo4J?
Re:Cayley – An open-source graph database
by maxdemarzi on Saturday April 08, 2017 @09:13PM
(#14069955)
Neo4j has control end to end. Cayley storage is handled by other databases. You can say one is a graph database and the other is a graph library on top of another database. Same as Titan now Janus.
Think about Datomic. It can use Riak as a backend or something else but it is still seen ad Datomic to the outside world. (You can also compare it to Lucene vs Solr)
Re:Cayley – An open-source graph database
by foobarchu on Tuesday April 11, 2017 @10:56PM
(#14094365)
Wait, Datomic with Riak as the backend? That seems a ridiculous level of abstraction, since Riak itself uses pluggable backend stores (Bitcask or LevelDB). Like creating a programming language whose interpreter runs on the JVM.
Re:Cayley – An open-source graph database
by scrollaway on Saturday April 08, 2017 @01:36PM
(#14067991)
If you add a newline after the </p> in the README.md that should fix your links.
Cool to see cayley on HN again :) Pretty excited to use it some time.
We've got a lot of new features on master, (GraphQL support, Gephi interfaces, Recursive iterators, etc) and are cutting a release next week.
Active work in the coming releases on tightening down the indexing and really bringing it into prod.
EDIT: Feel free to join the new Slack or the Discourse mailing list/discussion board!