Key Points from the book NoSQL Distilled
This page presents the key points of the book "NoSQL Distilled" by Pramod Sadalage & Martin Fowler. Sadalage and Fowler present key points of 11 chapters of their book "NoSQL Distilled." The chapters covered are:
1. Why NoSQL?
2. Aggregate Data Models
3. More Details on Data Models
4. Distribution Models
5. Consistency
6. Version Stamps
7. Map-Reduce
12. Schema Migrations
13. Polyglot Persistence
14. Beyond NoSQL
15. Choosing Your Database
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
Tags:
Comments
Chris Travers replied on Fri, 2012/09/21 - 5:25am
I am confused about this point: "Most applications, particularly nonstrategic ones, should stick with relational technology—at least until the NoSQL ecosystem becomes more mature."
It seems to me we may be discussing different ideas of "stragegic" but it seems to me that the more strategic an application is, the more the business folks will want to be able to come up with new metrics every week to report against the application. It seems to me that the only model which really works well for this sort of moving target, reporting-wise, is the relational model for two reasons:
1) If you have strong schemas and math behind that, you can reliably transform your data on output, and
2) Relational databases have really heavily matured with reporting in mind
So it seems to me that the miore strategic an application is, the more important it is to have a relational model to back it up. That doesn't speak against polyglot persistance, but it seems to me that it suggests that for such apps, NoSQL databases should be adjuncts to, rather than replacements of, the relational database.