On Monday, June 4, 2012 at 2:53 PM, Mark Phillips wrote:
> Hi,
>
> Assuming I'm understanding your use case correctly, the first option seems
> like your best bet.
>
> Primary key lookups are where Riak really shines, and if you're only GET-ing
> one key and then manipulating the associated j
Hi,
Assuming I'm understanding your use case correctly, the first option seems
like your best bet.
Primary key lookups are where Riak really shines, and if you're only
GET-ing one key and then manipulating the associated json-dict with some
app code, things should perform quite well (assuming you
Hello,
I am evaluating Riak for a project, and am looking for some recommendations on
modeling data for optimal performance. The data is a single 'object'
(henceforth named 'Widget') that needs to be looked up via N possible
attributes, and should have a reference to theses keys. There will be
