Social network data / Graph properties of Riak

Eric Moritz eric at
Fri Nov 18 11:06:59 EST 2011

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?


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

More information about the riak-users mailing list