ctor as a layer.
--
From: "Ran Tavory"
Sent: Saturday, September 25, 2010 1:41 PM
To:
Subject: Re: Cassandra for graph data structure
Courtney this certainly sounds interesting and as Nate suggested we're
always looking for valuable contribu
of the
> setbacks i'd run into using neo4j, not to mention having to learn it...
>
> ------
> From: "Nate McCall"
> Sent: Friday, September 24, 2010 4:14 PM
> To:
> Subject: Re: Cassandra for graph data structure
>
>
&
d pay for reads offsets a lot of the
setbacks i'd run into using neo4j, not to mention having to learn it...
--
From: "Nate McCall"
Sent: Friday, September 24, 2010 4:14 PM
To:
Subject: Re: Cassandra for graph data structure
My ide
> My idea however was to fork hector, remove all the stuff i don't need and
> turn it into a graph API sitting on top of Cassandra.
We are always looking for ideas and design feedback regarding Hector.
Please feel free to make suggestions or fork and send pull requests.
http://groups.google.com/gr
Just a tip for evaluation. Reads using Cassandra are expensive. Each link
in the graph would probably require a read transaction. I have never used a
graph db, but I would expect their API will be much more efficient for your
needs. Just something to consider before deciding.
Good luck!
- Luc
