A week ago while in Tel Aviv I talked with my colleague which is the lead developer of RedisGraph. He will be in San Francisco at Redis Conf with us and will release exiting news about RedisGraph, currently the development is very active.
Graph on Redis is cool and I get that hexastore is the way to go. Its very different from the Neo4J like graphs where the nodes and edges have properties. Hexastore is more based on the W3C RDF model. What confuses me is then why not have SPARQL as the query language?
I believe SAP has had this for a while[0] (but they are columnar while Redis is key-value).<p>[0]: <a href="http://www.ziti.uni-heidelberg.de/ziti/uploads/ce_group/2015-PELGA.pdf" rel="nofollow">http://www.ziti.uni-heidelberg.de/ziti/uploads/ce_group/2015...</a>
Looks good! Two questions come to my mind :<p>- Is it possible to embed RedisGraph inside an Android application ?<p>- Given it is memory only, is it possible to "dump" the graph to local storage then restore it to memory later ?<p>Another question, more general :
Given an X-only application (X being memory or disk), it is possible to emulate the API on top on the other, for example filesystem-in-memory and memory-on-disk (basically, swap I guess). Would you rather build an application using exclusively a Filesystem API, or exclusively a Memory-oriented API ?<p>Best Regards
>RediSearch has a distributed cluster version that can scale to billions of documents and hundreds of servers. However, it is only available as part of Redis Labs Enterprise.
This is really cool. I wrote something similar with Python (it was slow ha) as an exercise to learn Redis a few years back. I used Gremlin/Groovy as an inspiration for the query lang, not Cypher as this project does. <a href="https://github.com/emehrkay/rgp" rel="nofollow">https://github.com/emehrkay/rgp</a>
Would this work if I wanted to store the graph forever we generally use redis as memcache to store data with expectation that it will gone at any point in time.