From another CouchDB usage story:
One of the things that attracted the SkinnyBoard team to CouchDB is the document-based store with its inherent flexibility. It allows them to store entities and their relationships in a single document without the need for complex lookups and joins required by traditional relational databases. CouchDB’s support for map/reduce also means that they can construct complex queries and store them as design documents externally without the need for having this business logic in their main application.
While using the document model sounds like the right choice from the scenario, I’m confused by the map/reduce related comment which sounds more like stored procedures than normal app queries.
Original title and link: CouchDB Case Study: SkinnyBoard (NoSQL databases © myNoSQL)