NoSQL Data Modeling Techniques
First off I find the NoSQL term in itself very strange. How can you say anything intelligent about "everything that is not using SQL as a query language"? Its like talking about NoJava, instead of talking about Ruby.<p>Props for a well written article with lots of nice graphs but I dont agree with much of its content.<p>A few examples:<p>"software applications are not so often interested in in-database aggregation"<p>In my experience this is what 99% of business support apps are doing. Doing this aggregation in procedural application code will only give you more code to maintain and more bugs.<p>"joins are often handled at design time as opposed to relational model where joins are handled at query execution time"<p>Im glad you know beforehand about your changing requirements over the next 10 years and can "design" your joins for every eventuality right now.
It feels like the exact oppisite of agile.<p>I also agree with the very insightful comment by Voice in the wind (comment #4 below the article)