4 ms·
One of the questions I haven't been able to track down that has prevented adoption by me is how efficient the caching around MapReduce queries are in Riak. In
by pixelcort 14y ago
One of the questions I haven't been able to track down that has prevented adoption by me is how efficient the caching around MapReduce queries are in Riak.
In CouchDB MapReduce queries are completely incremental; if only a little data changes, only the relevant parts need to be rerun through the MapReduce process.
Riak looks really promising as:
1. It allows chaining MapReduce functions together
2. It supports sharding
Looking into Riak, it looked like there was a cache for part of the MapReduce system, but I wasn't sure how that cache worked or if it would be enough for large datasets that only change in little increments.
Edit: formatting.