Related to my CouchDB question.
Can anyone explain MapReduce in terms a numbnuts could understand?
Step 2 is Map. Step 3 is Reduce.
For example,
The reason MapReduce is split between Map and Reduce is because different parts can easily be done in parallel. (Especially if Reduce has certain mathematical properties.)
For a complex but good description of MapReduce, see: Google's MapReduce Programming Model -- Revisited (PDF).