Riak Search VS other query systems
jdaily at basho.com
Wed Aug 20 15:28:44 EDT 2014
I don't have benchmarks to discuss query performance for different tools at
different sizes, but I'd like to point out that the ultimate search tool
for Riak is to not search at all.
Riak Search, 2i, MapReduce are all capable tools, but they don't scale
nearly as well as straight key/value requests, and it is often possible to
model your data around the latter.
I covered this in https://basho.com/riak-development-anti-patterns/ and the
next edition of Eric Redmond's Little Riak Book (http://littleriakbook.com)
will have more discussion on the topic, but if at all possible, create your
query results as reports as the data is ingested, instead of attempting to
find it all later.
On Wed, Aug 20, 2014 at 3:21 PM, Alex De la rosa <alex.rosa.box at gmail.com>
> Any thoughts about this?
> One thing it worries me about Riak Search is that if one index has several
> millions of object to search for maybe it becomes slow? 2i might be faster
> On Tue, Aug 19, 2014 at 8:47 AM, Alex De la rosa <alex.rosa.box at gmail.com>
>> Hi there,
>> I had been seeing lately Riak Search as an ultimate way to query Riak...
>> and it seems recommended to use over MapReduce and even 2i... said so...
>> should we try to always use Riak Search over the other systems?
>> Is there any situation in which MapReduce could be a better approach than
>> Riak Search?
>> Same goes for 2i... I believe 2i is an optimal approach if you just want
>> keys and know very well what are you looking for, but out of that, should
>> Riak Search try to replace all 2i uses?
>> Practical example: If you are twitter and want to get twits for the
>> hashtag #Riak, what would be the best approach? 2i? Riak Search? MapReduce?
> riak-users mailing list
> riak-users at lists.basho.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the riak-users