Abstract Ponderings on how to build an efficient mapreduce system that keeps up-to-date (aka reaches consistency eventually) even if the data underneath changes, without recomputing from scratch. I'm also including a visual overview of mapreduce that may help fellow visual/spatial thinkers understand the topic better. Background So Google has their MapReduce , the people behind CouchDB are throwin