Social network data / Graph properties of Riak

Jeroen van Dijk jeroentjevandijk at
Fri Nov 18 14:49:49 EST 2011

I didn't include the riak list...

---------- Forwarded message ----------
From: Jeroen van Dijk <jeroentjevandijk at>
Date: Fri, Nov 18, 2011 at 8:36 PM
Subject: Re: Social network data / Graph properties of Riak
To: Eric Moritz <eric at>

On Fri, Nov 18, 2011 at 5:06 PM, Eric Moritz <eric at>wrote:

> If you're storing the graph in a graph database where you're simply
> connecting keys to other keys and then you store the actual properties
> in Riak identified by those keys, then yes Riak will be a fine
> solution for you.
> For instance, you traverse the graph using a graph db, collecting a
> list of keys you want the properties for and then load the property
> documents for the keys you collected.

Is that what you're envisioning?
Thank you for this suggestion. I might end up with this kind of solution,
but I think it is not completely what I'm envisioning. I would like to have
the power to scale horizontally as Riak can. If I would be depending on a
graph database to store the relationships I think that this will at some
point turn out to be the bottleneck, unless there are property graph
databases I'm unaware of that have a similar way of scaling as Riak does.

So I basically want to be able to store the complete graph/dataset in Riak
without losing any information on edges or vertices. The database should be
able to scale on read and writes horizontally by just adding machines as
Riak is supposed to do. Advanced queries will be done in the graph
database. The graph database should be fed with the data that is stored in
Riak and this process should not be too slow. I'm thinking of to have my
application write to both Riak and a graph database. And I'll want to sync
on set times from Riak to the graph database to make sure no data is lost
in the graph database. I guess this syncing part is also non-trivial for
big datasets.

Does the above make sense to you?


> Eric.
> On Fri, Nov 18, 2011 at 10:38 AM, Jeroen van Dijk
> <jeroentjevandijk at> wrote:
> > Hi all,
> > I'm currently evaluating whether Riak would fit as the main storage of my
> > current project, a social network. The reason I am attracted to Riak and
> > less to a Graph database as main storage is that I want the easy
> horizontal
> > scalability and multi-site replication that Riak provides. The only
> thing I
> > doubt is whether the key-value/link model of Riak is flexible enough to
> be
> > able to store a property graph ( I am
> not
> > asking whether the querying/graph traversing will be easy; I'm probably
> > going to use a graph database or a Pregel like platform (e.g.
> > for that problem. I guess my main question
> is
> > whether it would be easy/feasible to import and export a property graph
> in
> > and from Riak? Has someone done this before?
> > I realize the above might be too specific, so here are two more questions
> > that I think are relevant:
> > - Is there a known upper limit of links that can be stored (I don't want
> to
> > add them all at once so 1000 per request is fine,
> >
> )
> > - Is there a way to add meta data to links (edges)? E.g. weigths and
> other
> > attributes.
> > Any other ideas or advise are also highly appreciated.
> > Cheers,
> > Jeroen
> > _______________________________________________
> > riak-users mailing list
> > riak-users at
> >
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the riak-users mailing list