Map-reduce is just one way of organizing your computation. If you have something simpler, then I would say that you are doing fine.
There are plenty of tasks that are best served by a DAG of simple tasks. Systems like Amazon's simple queue (where tasks come back to life if they aren't "finished") provide a very natural control flow for these problems. You can phrase many of them as map-reduce programs with trivial reducers, but there really isn't much point in that if your inputs are large. One thing that you may be missing out on is task placement. It would be nice to invoke code close to the inputs to avoid some network traffic. That would be pretty easy to do, I would guess. On 12/20/07 6:46 PM, "Kirk True" <[EMAIL PROTECTED]> wrote: > Thoughts?
