Original article in the post misses the point (Score 1)

It claims the database technology is better in enforcing data consistency . They make this assumption keeping applications like banking, payroll etc in mind. Not the Web applications where speed matters a lot. This is where MapReduce score high. Considering speed is utmost factor, would you care design application with all referential integrity constraints or figure ways where u avoid it all together. Database schema and all looks good but doesnot provide speed or rather eats up processing power. Mapreduce allows you to process huge amount of data in parallel. While academics debate about merits of Mapreduce, Google builds new systems quickly, processes data at lightning speed. Mapreduce is the very reason for the success of google infrastructure. It makes easy to processes data, write pipelines to mine data etc.