I see Cayley now supports other backends beside LevelDB. "PostgreSQL and MongoDB for distributed stores" - that's good to read.
is there a description of the RDBMS low-level model? Is it something like a single s,p,o table, with indexes (s, so, spo, , po, etc)?
Exactly so, for the RDBMS model. Yeah, this has it's own issues, but it's the most direct method. We do a little extra trick with the indexing; joining on fixed hashes instead of the full value, but nothing crazy.
Maintainer here, good to see Cayley on HN again :) 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!
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. :)
Maintainer here, good to see Cayley on HN again :) 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!
If you want help with a Cassandra backend, hit me up (my HN username @ gmail or apache)
We have Elasticsearch as a generic document search engine, each document has a non-trivial amount of properties (let's say 50 or so). It's incredibly performant for all sort of searches, the details of each of which this solution wasn't specifically designed for, hence me calling it a generic search engine. Every time I contemplate of bringing graph relationships, that exist between these documents, into the mix, I get stuck. Elasticsearch doesn't quite do graph (natively), but the graph databases I tried don't do properties too well (OrientDB, Neo4J). I'm not talking about one or two properties, but multiple properties across multiple hops in the graph that I envision querying for. Let alone full text searches. I emailed back and forth with the helpful folks at Orient, but it always came down to optimising for specific queries, gone the "generic". Is anyone solving that problem? Cayley?
Maintainer here, good to see Cayley on HN again :) 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!
If you want help with a Cassandra backend, hit me up (my HN username @ gmail or apache)
Anyone use Cayley in prod? An old job used Neo4j, and the graph concept was great for specific use cases. As a lightweight graph store, Cayley was really exciting when it came out, but I haven't had a need for it since I left that job. It strikes me as really well made, and I'd love to hear any war stories.
Tried to use it in production a couple of years ago hosting a mirror copy of Freebase with mixed results: - There were a couple of issue loading the data that we fixed and contributed back the patch - Loading the data was really slow, and it got slower every time a new entry was added (Loading the full freebase dump required 1 week on a very beefy machine with SSD. Used LevelDB) - Then the queries were relatively slo…
What's the best way to load Freebase in 2017? Cayley with Postgres storage? Or some other RDF/graph DB? Or ElasticSearch? Or dump it in Postgres/MySQL? I am not interested in complex queries, but simple queries that execute reasonable fast.
Tried to use it in production a couple of years ago hosting a mirror copy of Freebase with mixed results: - There were a couple of issue loading the data that we fixed and contributed back the patch - Loading the data was really slow, and it got slower every time a new entry was added (Loading the full freebase dump required 1 week on a very beefy machine with SSD. Used LevelDB) - Then the queries were relatively slo…
What's the best way to load Freebase in 2017? Cayley with Postgres storage? Or some other RDF/graph DB? Or ElasticSearch? Or dump it in Postgres/MySQL? I am not interested in complex queries, but simple queries that execute reasonable fast.
We have it loaded on a Dgraph instance. In case you want to play around with it at https://play.dgraph.io
Maintainer here, good to see Cayley on HN again :) 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!