MapReduce is making a comeback
estuary.dev
MapReduce is making a comeback
1–10 of 39 posts
Re: MapReduce is making a comeback
#2MapReduce is a useful tool in some contexts, but the the hype surrounding it always felt like people patting themselves on the back for re-inventing relational algebra.
Re: MapReduce is making a comeback
#3Interesting but how is this as an alternative to Apache Flink's stream processing model?
Re: MapReduce is making a comeback
#4I love how data structures (block chain!) and algorithmic design patterns are now sort of like fashion trends. This industry is so faddish.
"Reduced lock contention sharded hash tables are this season's new casual!"
Re: MapReduce is making a comeback
#5MapReduce is a useful tool in some contexts, but the the hype surrounding it always felt like people patting themselves on the back for re-inventing relational algebra.
It was more about scaling than about relational algebra though.
Re: MapReduce is making a comeback
#6Every section in this article is a mistake.
For instance
- Map Reduce was not invented in 2004. it's a technique from the punch card days.
- Map reduce is not solely useful because it allows you to delete source data, it's a trivial method of parallel processing. It's not the most trivial or most modern. Just common
Re: MapReduce is making a comeback
#7MapReduce is a useful tool in some contexts, but the the hype surrounding it always felt like people patting themselves on the back for re-inventing relational algebra.
Isn't the entire field of software just people patting themselves on the back for some extremely basic relational algebra?
I don't know what I should be proud of when I learn something new, it all seems extremely basic compared as soon as I learn it.
Re: MapReduce is making a comeback
#8Every section in this article is a mistake. For instance - Map Reduce was not invented in 2004. it's a technique from the punch card days. - Map reduce is not solely useful because it allows you to delete source data, it's a trivial method of parallel processing. It's not the most trivial or most modern. Just common
But they say ‘MapReduce’, not ‘map reduce’. They’re talking about the specific model, not the general idea of map reduce.
Re: MapReduce is making a comeback
#9> Rather than producing output data and then exiting, like a Hadoop job, a continuous MapReduce program continues to update its results incrementally and in real time as new data is added
So keeping track of min/max/average as you add new data is now "continous MapReduce"?
Don't get me wrong, a data platform that ingests data and computes useful user-defined aggregates from that sounds useful. But this article feels like an attempt to position that as some kind of incredible industry-leading insight that is a novel take on $buzzword, when it really isn't.
Re: MapReduce is making a comeback
#10MapReduce is a useful tool in some contexts, but the the hype surrounding it always felt like people patting themselves on the back for re-inventing relational algebra.
The big hype was always due to the ability to shed large oracle based data warehouses. When Hadoop was full of hype in 2010 Oracle was charging 150k/cpu core/year for a rac cluster license.
Considering that oracle is not in fact magic, this meant that a large number of firms were spending 7-8 figures annually on oracle licenses. Map reduce/Hadoop was the first accepted alternative that didn’t involve spending outrageous license fees and instead involved outrageous hardware expenditure.