Domain: databasecolumn.com
Stories and comments across the archive that link to databasecolumn.com.
Comments · 5
-
Re:AI != design brain
http://www.databasecolumn.com/2008/01/mapreduce-a-major-step-back.html
As both educators and researchers, we are amazed at the hype that the MapReduce proponents have spread about how it represents a paradigm shift in the development of scalable, data-intensive applications. MapReduce may be a good idea for writing certain types of general-purpose computations, but to the database community, it is:
1. A giant step backward in the programming paradigm for large-scale data intensive applications
2. A sub-optimal implementation, in that it uses brute force instead of indexing
3. Not novel at all -- it represents a specific implementation of well known techniques developed nearly 25 years ago
4. Missing most of the features that are routinely included in current DBMS
5. Incompatible with all of the tools DBMS users have come to depend on
-
Re:Perhaps a good addition to data warehousing
Since the main difference between a RDBMS and MapReduce seems to be that the former is most suited for structured data and the latter best suited for unstructured data, it might be a good fit to use them both. And according to studies, it might be that north of 80% of our data is unstructured. This has been a big topic in data warehousing and led to the start of the whole DWH 2.0 thing.
So the fact that MapReduce is used in massive parallel processing machines like the ones from Greenplum (as quoted from the article) is not as bad as Stonbraker and Co. seem to think.
Zaaf
-
First they attack it
http://www.databasecolumn.com/2008/01/mapreduce-a-major-step-back.html
then they embrace it
-
Re:may be missing the (data)points
> I don't know why this article is so harshly critical of MapReduce.
> Are these guys just trying to stake a reputation based on being critical of Google?
Um... yes?
The Database Column is being coy about being a corporate blog for Vertica, a high performance database database product, but in fact it is. Vertica is a commercial implementation of C-Store and was founded by Michael Stonebraker, the most prominent proponent of column based databases (get it? the database column). So yes, they have a very good reason to be hostile to Google.
http://www.vertica.com/company/leadership
http://en.wikipedia.org/wiki/C-Store
http://en.wikipedia.org/wiki/Michael_Stonebraker
http://www.databasecolumn.com/2007/09/contributors.html -
Huh!?
...they should be considered legacy technology, more than a quarter of century in age and "long in the tooth".
http://www.databasecolumn.com/2007/09/one-size-fit s-all.html
The point is clear. People could(and in many cases should) be getting a lot of use out of column oriented databases. The title of his post is "One Size Fits All - A Concept Whose Time Has Come and Gone". His argument basically comes down to saying that blindly throwing Oracle at all of your database problems is stupid and outdated. There are better solutions for many situations out there, and custom built solutions can offer many benefits as well.