The slide that contrasts RDBMS and NoSQL DBs and asks "A step backwards?" reminds me of the rebuttal of MapReduce and NoSQL stores by Mike Stonebraker (copy of the article here: <a href="http://craig-henderson.blogspot.com/2009/11/dewitt-and-stonebrakers-mapreduce-major.html" rel="nofollow">http://craig-henderson.blogspot.com/2009/11/dewitt-and-stone...</a>)
Opinion: traditional databases suck and so do NoSQL ones, for the exact opposite reasons.<p>A better solution would be one that gives developers fine-grained control over "scalable and loose" vs "less-scalable and tight", rather than all-or-nothing in either direction.<p>That is to say: I want full ACID on my "financial transactions" collection and maximum scalability for my "chat messages" one -- but I want them in the same overall system, accessed via the same API, managed via the same tools, and with knobs that can be inexpensively modified on the running system.
Apologies for the extremely flat and boring tone of voice and the somewhat rushed comparison of the actual products. Next time I'll do better, promise :)<p>Some notes to introduce the slides: <a href="http://www.alberton.info/nosql_databases_what_when_why_phpuk2011.html" rel="nofollow">http://www.alberton.info/nosql_databases_what_when_why_phpuk...</a>