cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lucas Nodine <lucasnod...@gmail.com>
Subject Re: Cassandra for graph data structure
Date Fri, 24 Sep 2010 14:08:01 GMT
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!

- Lucas

On Fri, Sep 24, 2010 at 8:51 AM, Courtney Robinson <sabco@live.co.uk> wrote:

>  Apoligies for the first e-mail with the misleading subject i was reading
> a thread and mistakenly replied
> I've been using Cassandra for a while now and no problems. I have a new
> project coming up now that we're penciling out the data structure for.
>
> The best we've come up with has turned into a graph structure i'm just
> wanting to know what people think because i
> know there are graph db's out there like neo4j etc.
> 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.
> Main reason for this approach is because i am already very familiar with
> Cassandra and it will be fast to write a client or modify an existing
> one than to learn a new API.
>
> Do you think there are any gotchas in this approach? Any tips, pointers?
>



-- 
Lucas J. Nodine
Assistant Labette County Attorney
201 S. Central, Suite B
Parsons, KS 67357
(620) 421-6370

Mime
View raw message