Are there any Design Guidelines for Documental Databases?
couchdb, document-oriented-db, nosql
Solution
Jan Lehnardt recently wrote up a useful overview of data modeling (I would not quite call it "schema" design as you correctly point out).
http://blog.couchbase.com/document-modeling-rules-thumb
Problem
Just wondering if there are any kind of guidelines for when you are designing a document-oriented db and I am talking especially about CouchDb. I know that being schemaless things can take the shape that we want but, are there any best practices? Thanks in advance! =D