This article made me wince. It describes a style of programming which has been common among corporate Oracle and Microsoft developers for years but seems very

This article made me wince. It describes a style of programming which has been common among corporate Oracle and Microsoft developers for years but seems very inefficient and outdated now. Writing a set of stored procedures in the database to call for each query you intend running has always seemed absurd to me but if you're using an ORM framework like Rails or Catalyst or whatever it's not even an option. I wonder if the author of this has even heard of things like replication, sharding, memcached or CouchDB or BigTable... Perhaps it would have been better titled "Ten Characteristics of a Very Conventional Corporate Approach to Database Design."