Responding to several comments. (The _underscores_ in the following quotes are mine for emphasis.) >kpmah: I think most are pragmatic and admit you _may_ hav

Responding to several comments. (The _underscores_ in the following quotes are mine for emphasis.) >kpmah: I think most are pragmatic and admit you _may_ have to do denormalise for performance >calpaterson: So _rare_ to actually have to denormalise for performance today though. The article's author didn't describe it as "may"/"rare" which leaves some wiggle room for the cases of denormalization required in real-world implementations. Instead he used absolute qualifiers such as "never", "no reason", "any": - the "additional development costs" that Bolenok refers to -- but they would _never_ be justified: - "consistency-performance tradeoff [...], there is _no_ reason to expect _any_." The author does write his advice in abstract terms instead of discussing concrete "case studies" so we are left to speculate what mental model of the database world he holds in his mind when he's rigid with strict rules of normalization and relational purity. Based on the topics in his papers[1], I'm guessing his world consists of a single OLTP database. E.g, you develop a non-cloud restaurant reservation & POS system with a single-instance database. Yes, you don't need any denormalization hacks in that scenario. But for other problems such as distributed databases, you can't do joins across 2 geographically separated data centers. (Well, you theoretically could do it but the slow nested-loop performance across the WAN would make it unusable for a real-world application.) Some duplication via data denormalization is required and no "sufficiently smart db engine"[2] can automatically optimize for it. An application architect has to manually make that design decision and live with the deliberate tradeoffs. (E.g., batch jobs now have to be run to periodically keep databases at different datacenters in sync.) There are many real-world scenarios that require denormalization which have nothing to do with a junior programmer's lack of SQL knowledge to join 20 tables to populate an "edit customer" data entry screen. [1]http://www.dbdebunk.com/p/papers_3.html http://www.dbdebunk.com/p/papers_3.html [2]riff on the theoretical "Sufficiently Smart Compiler" to solve all performance optimizations so there's never a need to write performance-specific language syntax or switch to a "faster" language... because as we all know... "languages" are not fast or slow -- it's the "implementations" that are fast or slow. That Ruby is not as fast as C/C++ is an implementation detail (SSC) and not the issue of the language syntax.