One of your subheadings is "What is a View?", which is a good question, but you never exactly answer it. Instead, you describe a use case. While a use case can help the conceptual understanding of the terms, it is not really a definition, in the same sense you shouldn't define something by using a metaphor or simile. I would like to see a concrete sentence which says something like "A view in CouchDB is .... "
It would be also nice if there could be some comparison here with traditional RDBMS, where a lot of people will be coming from. One thing that I could not find out from reading this is whether or not in CouchDB a view is the same thing as a query.
One of your subheadings is "What is a View?", which is a good question, but you never exactly answer it. Instead, you describe a use case. While a use case can help the conceptual understanding of the terms, it is not really a definition, in the same sense you shouldn't define something by using a metaphor or simile. I would like to see a concrete sentence which says something like "A view in CouchDB is .... " It would be also nice if there could be some comparison here with traditional RDBMS, where a lot of people will be coming from. One thing that I could not find out from reading this is whether or not in CouchDB a view is the same thing as a query.