cayley

Hey, maintainer of Cayley ( https://github.com/google/cayley ) here. Glad to see more people interested in this space! It looks like your code is mostly stubbed out right now -- using gorm for any persistence. You'll find that storing a basic graph is easy; doing more complex traversals and optimization is a harder problem. I can appreciate your concept of experimenting with adding monetary incentives on top of requests and datasets. Graphs can be a useful for this, if you view a graph as a (requestable) URI of triples. I'd recommend linking in Cayley as your backend (you can use it as a library), and dealing with the requests/economics as an API layer on top. The benefit of open source is you don't have to reimplement everything yourself. And if you have novel notions on how to distribute a graph that could be interesting, feel free to p

I implemented a "light" version of MQL atop Cayley (https://github.com/google/cayley) that I'd be happy to extend :) tsturge did a prescient job with the original (yeah, GraphQL is 2007 all over again) and I wanted to keep the flame alive.

Anyone know how this compares with Cayley? https://github.com/google/cayley/

If you want to help hack on this, I've written a Postgres backend for the graph database Cayley that's fairly fast and about to merge (for use on a prod feature): https://github.com/google/cayley/pull/289 For traversals, it tries its level best to let Postgres create the appropriate JOINs, which Postgres does well... most of the time anyway. In doing this, I learned really fast how many weird semantic corners of bog-standard SQL are, and the optimization choices Postgres makes based on the way you formulate the query. Ping me on that PR! And/or join #cayley on Freenode

Take a look at Cayley - https://github.com/google/cayley

Very much so! I'd love some help writing/documenting/explaining to people a lot of the work I've done behind Cayley (http://github.com/google/cayley). I can explain it very well one-on-one or to a developer but my writing/explaining/diagramming gets a little esoteric for the people at large. Even planning/prioritizing some things would be useful. So if graph databases strike you as cool new technologies and you'd like to learn more, check it out and feel free to drop me a line personally at barak (at) cayley.io