The Trickery in "MapReduce vs. Parallel DBs"
everythingisdata.wordpress.com
everythingisdata.wordpress.com
Mapreduce is for batch processing; databases are for live queries. You often use mapreduce with a database; the mapreduce can fill a database with data or take all the data out of a database and produce something of a different format. You don't write 100,000 line SQL statements but mapreduce is designed to run arbitrary code in the inner loop. You can't write a mapreduce-backed website that kicks off a mapreduce with each request, but that's a great use of SQL. Etc etc.
No, databases are also commonly used for batch queries. Are you familiar with data warehousing? Teradata, Greenplum, Netezza, and similar products? This sort of stuff, for example:
http://www.dbms2.com/2009/04/30/ebays-two-enormous-data-ware...
Parallel databases have been around since the late 1980s, and can be used for many of the same things MapReduce is often used for (large-scale batch data analysis). Hence the comparison.
"query" != "live query".
[MapReduce was not designed for] anything where the output is less than 10G or so
Where does the MapReduce architecture make any such assumption?
It is implausible to communicate with remote servers or parse html using a database. But those are normal things to do in a mapreduce.
Sure -- while it is quite possible to do such things using SQL UDFs, I can believe it isn't done very often. Nevertheless, there is considerable overlap between the two tools, and plenty of scope for comparison.
At least one clustered sql database vendor supports the use of map-reduce to do data transforms. The results of which are made available via standard sql queries.