Ask HN: To everybody who uses MapReduce: what problems do you solve?

Re:Ask HN: To everybody who uses MapReduce: what problems do... by alecco on Sunday November 10, 2013 @01:01PM (#6707599)

Maybe I misunderstood what you were asking.

Note both MapReduce and NoSQL are overhyped solutions. They are useful in a handful of cases, but often applied to problems they are not as good.

[ Parent | on HN ]

Re:Ask HN: To everybody who uses MapReduce: what problems do... by aidos on Sunday November 10, 2013 @02:11PM (#6707954)

I'm not sure that the two concepts are resulted at all. Obviously mongo has map reduce baked in - but that's not that relevant. Map/reduce is a reasonable paradigm for crunching information. I have a heavily CPU bound system that I parallelise by running on different machines and aggregating that results. I probably wouldn't call it map reduce - but really it's the same thing.

How do you parallelise your long running tasks otherwise?

[ Parent | on HN ]

Re:Ask HN: To everybody who uses MapReduce: what problems do... by alecco on Sunday November 10, 2013 @02:46PM (#6708090)

I can't say without more information on the problem to solve. As I said above, there are cases where MapReduce is a good tool.

And even if you improve the DS/Algorithm first, usually that is usable by the MapReduce port and you save a lot of time/costs.

[ Parent | on HN ]