3 ms·
>“We don’t really use MapReduce anymore” This is not even true. They have recently published research that involved using MapReduce in their own systems. Examp
by _dark_matter_ 12y ago
>“We don’t really use MapReduce anymore”
This is not even true. They have recently published research that involved using MapReduce in their own systems. Example: http://research.google.com/pubs/pub41376.html http://research.google.com/pubs/pub41376.html
- kiyoto 12y agoAs someone who has one foot in marketing and one foot in development (I am a developer evangelist), here is what's happening. 1. Google's infrastructure is evolving atop MapReduce (FlumeJava/MillWheel). 2. Google's PR decided to call it "not using MapReduce anymore" because in marketing, "beyond <current fad>" sounds really cool. 3. The rest of the world's PR/press/marketing fall for Google's clever PR. Either way, it is great to see Google making its core technology accessible as part of their PaaS =)
- t1m 12y agoIt would be more great if they open sourced it.
- zobzu 12y agohyperscale man! cyberleetscale would have been better. IMO. Thanks for the clarifications :)
- username223 12y ago> 3. The rest of the world's PR/press/marketing fall for Google's clever PR. If "hyper-scale Analytics" counts as "clever PR," then eating paste counts as "clever food choice." It's not worth my time to decode the BS.
- rsync 12y agoI know what I'm supposed to do when my taxi driver starts recommending stocks to me ... But what do I do when people start describing themselves as "developer evangelists" ? That has to be some kind of sell signal, right ?
- j_baker 12y agoThere's a grain of truth to what he's saying. We don't write many new actual C++/Java MapReduce jobs. It's mostly flume. Although there is some momentum behind Go MapReduce.