Talk:NoSQL: Difference between revisions
imported>Pat Palmer (intro to my review comments (to be added shortly)) |
imported>Pat Palmer (→Pat's review of this article: level of expertise of material in the article) |
||
| Line 11: | Line 11: | ||
==Pat's review of this article== | ==Pat's review of this article== | ||
This is a great beginning. The article as it stands today covers a lot of ground, and I especially appreciate the DOI in the reference list, plus the spare, lean and precise technical language employwed in many sections. Some comments, questions, and ideas for additional development are detailed in the following subsections (to be added shortly): | This is a great beginning. The article as it stands today covers a lot of ground, and I especially appreciate the DOI in the reference list, plus the spare, lean and precise technical language employwed in many sections. Some comments, questions, and ideas for additional development are detailed in the following subsections (to be added shortly): | ||
===intended readers=== | |||
This article is the product of one or more writer who appear to have a high level of technical expertise with databases in general, and who writes with admirable clarity and conciseness about technical matters. The article seems to assume that readers are already familiar with the capabilities of conventional relational database management systems, and also with map-reduce algorithms. While the technology being described is sufficiently complicated that much of the article probably may necessarily be beyond the scope of what an expert lay reader might understand, IMO it is still important to strive for satisfying both intelligent lay experts and deep subject experts. Perhaps there might be added some kind of statement about this in the overview at the beginning. It might also be useful to provide some history and market descriptive material near the top, before launching heavily into the tech speak.[[User:Pat Palmer|Pat Palmer]] 20:09, 19 August 2010 (UTC) | |||
Revision as of 14:09, 19 August 2010
Just a question on an interesting topic
Only a personal interest, but to what extent do these use XML, or are the key-value relationships implemented more as type-length-value or something even simpler? --Howard C. Berkowitz 14:54, 28 July 2010 (UTC)
Useful article?
You may want to use ACID properties. Howard C. Berkowitz 02:29, 8 August 2010 (UTC)
Pat's review of this article
This is a great beginning. The article as it stands today covers a lot of ground, and I especially appreciate the DOI in the reference list, plus the spare, lean and precise technical language employwed in many sections. Some comments, questions, and ideas for additional development are detailed in the following subsections (to be added shortly):
intended readers
This article is the product of one or more writer who appear to have a high level of technical expertise with databases in general, and who writes with admirable clarity and conciseness about technical matters. The article seems to assume that readers are already familiar with the capabilities of conventional relational database management systems, and also with map-reduce algorithms. While the technology being described is sufficiently complicated that much of the article probably may necessarily be beyond the scope of what an expert lay reader might understand, IMO it is still important to strive for satisfying both intelligent lay experts and deep subject experts. Perhaps there might be added some kind of statement about this in the overview at the beginning. It might also be useful to provide some history and market descriptive material near the top, before launching heavily into the tech speak.Pat Palmer 20:09, 19 August 2010 (UTC)