Some may think this problem requires MapReduce. The quote from the original implementation blog post certainly seems to indicate so.
Some may think this problem requires MapReduce. The quote from the original implementation blog post certainly seems to indicate so.
Pretty confident that not a single developer anywhere in this world would be first thinking of MapReduce. Just like they wouldn't jump straight to Cobol.
Well, Hive and Spark create MapReduce jobs to satisfy your queries: it's still in the background, but you don't have to think about it (as much).
You've seen people writing pages and pages of Java code to do ETL ?
The rest of the world does not particularly care about SV fashion trends.
Edit: We're also a fairly greenfield team, with a product in beta that's less than 4 years old. So like, the leaders of the team knowingly crafted us in this particular direction.