Live data from Hacker News

Cayley – An open-source graph database

github.com

51–60 of 71 posts

Re: Cayley – An open-source graph database

#51
post #4

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!

What's the difference between Cayley and Neo4J?

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

#52
post #28

Earlier quoted context omitted.

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

The movie subset, or the whole Freebase?

The Freebase Film Data has only 21M facts. Freebase 1.9 billion facts.

Re: Cayley – An open-source graph database

#53
post #52

Earlier quoted context omitted.

We have it loaded on a Dgraph instance. In case you want to play around with it at https://play.dgraph.io

The movie subset, or the whole Freebase? The Freebase Film Data has only 21M facts. Freebase 1.9 billion facts.

This is just the film data.

Re: Cayley – An open-source graph database

#54
post #19

Earlier quoted context omitted.

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…

Benchmarks for loading freebase data in Cayley vs Dgraph. https://discuss.dgraph.io/t/differences-between-dgraph-and-c... Dgraph was 10X faster.

What's up with this toy dataset? The movie subset is just 21 mio facts. (21million.rdf.gz)

Can someone run the benchmark for the real Freebase (1.9 billion facts)?

Also LevelDB/Bolt is not suitable for this, better use MongoDB or Postgres or MySQL as Cayley data store.

Re: Cayley – An open-source graph database

#55
post #52

Earlier quoted context omitted.

The movie subset, or the whole Freebase? The Freebase Film Data has only 21M facts. Freebase 1.9 billion facts.

This is just the film data.

I would be interested if Dgraph can handle the full Freebase dataset. (250 GB RDF)

How long does it load? What's the avg query response for very simple searches (like who is the US president)?

Re: Cayley – An open-source graph database

#56
post #45

What exactly is this? The GitHub page speaks of different backends, and those appear to just be databases or key-value stores in themselves (e.g, Postgres and Bolt). Is Cayley basically a query rewritter, that is it has some tables in the backend and when queried, Cayley then goes to the "real" (for lack of a better word) database? Cayley's query language might be more full featured, but it isn't a storage mechanism…

Cayley's graph data layout is most similar to a Hexastore-style [1] triple store, though IIRC it doesn't do the full six-way index that the original Hexastore paper describes. The Redis page on secondary indexing [2] has a great quick intro to what this actually entails (search the page for Hexastore). As you might guess from the Redis link, this style of graph lends itself well to KV stores, so the answer to your qu…

Speaking of which, take a look at this Redis module that marries Hexastore and neo4j-like queries: https://github.com/RedisLabsModules/redis-module-graph

Re: Cayley – An open-source graph database

#57

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 g…

If you'd be okay with a directed acyclic graph, then SQL can work. Basically "modeling trees in SQL".

Specifically, you could use postgresql for the edge traversing and its jsonb column to store searchable attributes.

Re: Cayley – An open-source graph database

#58
post #34
post #9

I can't understand how to use the query language. It all seems so magical! I tried building something with Cayley once but couldn't fetch all the data I wanted in a single query, or didn't know how to, then got frustrated and deleted everything.

Which of the three query languages are you having trouble with? All of them? MQL has been around a long long time (2006). Gizmo is new but based on & very similar to Gremlin (2009). GraphQL is the newest (2015). Did you try them all? Or is one in particular rough?

I'm talking about that Gizmo/Gremlin.

Re: Cayley – An open-source graph database

#59
post #34
post #9

I can't understand how to use the query language. It all seems so magical! I tried building something with Cayley once but couldn't fetch all the data I wanted in a single query, or didn't know how to, then got frustrated and deleted everything.

Which of the three query languages are you having trouble with? All of them? MQL has been around a long long time (2006). Gizmo is new but based on & very similar to Gremlin (2009). GraphQL is the newest (2015). Did you try them all? Or is one in particular rough?

[deleted]

Re: Cayley – An open-source graph database

#60
post #28

Earlier quoted context omitted.

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

How is Dgraph licensed? I see both Apache and AGPL in GitHub.
Post reply on HN