Alex Sicular posted about this on his blog the other day:
http://siculars.posterous.com/paginating-with-riak Basically, he uses a
combination of Riak and Redis to manage pagination.
If you're absolutely opposed to using multiple data stores, Eric's approach
should work. Otherwise, I'd offload sort
I have also been toying with the idea of a linked list using a "next"
links on entries. Theoretically I could use link walking to get the
next 19 entries given a "HEAD" entry. It feels like a maintenance
nightmare though.
On Sat, Jan 15, 2011 at 7:23 PM, Gary William Flake wrote:
> I am buildin
First, check out Riak Search. It can sort your records by dates and
your can use it for
filtering on secondary indexes. If your criteria for listing the
records is pretty simple and can be expressed with a search query,
that may be your best bet. For instance, listing a user's blog
entries is as
I am building a backend for a web service and Riak looks to be a strong fit
for my needs at this point. However, there is one really simple requirement
that I can't figure out how to implement on Riak with any sort of
efficiency. To simplify the question, suppose that I want a twitter-like
servic
