Re: Curator: New Ruby ORM for Riak

2012-02-21 Thread David Dawson
Paul, Thanks for the reply, I found this in the basho doc's.. Maybe the Basho guys can shed some light on the performance trade offs Lookup Performance # Secondary Indexes uses document-based partitioning, which means that the indexes for an object are stored on the same partition as the objec

Re: Curator: New Ruby ORM for Riak

2012-02-21 Thread Paul Gross
I can't speak to the performance differences, but my understanding is that secondary indexes perform very well. Personally, I prefer one document with multiple secondary indexes instead of extra documents. I think it's cleaner conceptually, and it's a simpler implementation. On 2/21/12 2:46

Re: Curator: New Ruby ORM for Riak

2012-02-21 Thread David Dawson
This looks great Although I am still not clear when to use index's and when not to, for instance if I wanted to build a high speed backend system where you could look up a user either by their email address or their mobile number I see 2 ways to do this: 1 .Create a user document, follo

Curator: New Ruby ORM for Riak

2012-02-21 Thread Paul Gross
We at Braintree (http://www.braintreepayments.com/) open sourced our Riak ORM for Ruby called Curator. It follows a repository pattern rather than an ActiveRecord or Ripple pattern. You can check out the code on github: https://github.com/braintree/curator We also released a blog post that exp