daniel.mccreary (21) [Avatar] Offline
We frequently get the following suggestions on our book from reviewers:

• You don’t talk about product X
• You mention product Y but not X
• I would like sample code for product X

We would like to explain why we frequently will not be able to accommodate these requests.

Our book has a focus on the underlying concepts and patterns around the NoSQL movement. We build a vocabulary of the new concepts in chapter 2 and then explore the patterns in chapters 3 and 4. Chapter 3 isolates the existing popular patterns so you can skim that chapter if you have a strong background in RDBMS, OLAP and revision control systems. Chapter four is about the newer patterns.

The rest of the book is about applying these patterns to specific types of problems: Big Data, search, high availability and agility. We then close with optional topics (functional programming and security) before we pull everything together in a discussion of formal objective database selection processes.

One of the principal goals of the book is to help the solution architect develop a good understanding of the patterns and how they will apply to a problem. We then suggest a formal process for doing this.

It has never been our intent to enumerate the hundreds of NoSQL products and classify each one of them and then to compare them. We do mention some NoSQL products in chapter one to orient our readers. However, this is just a sample and does not reflect studies on the number of downloads, market share, or the number of citations in journals. Any book that attempts to do this would be out of date in a few months. Our goal is to write a book that will have consistent value for many years to come as many of the design patterns books have done in the past.

So you won’t see any MongoDB vs. Cassandra discussions but you will see discussions of how to evaluate the fit of document stores and column family stores to a specific business concerns like scaleability or findability.

When we do mention a specific product it is because we feel it is representative of a useful learning example, not because of its mind-share. Some of the early innovators in the NoSQL movement like Google, Yahoo, MarkLogic and Amazon get mentioned more because their early work helped users understand the benefits of moving away from RDBMS systems.

Because our book also has a strong focus on mapping the business problems to a general pattern we don’t have room in the book for large blocks of sample code. If you need sample code we suggest you checkout Manning books on individual NoSQL products. There are a few exceptions but we think they are justifiable because they are unique and show architectural variation.

If you do have comments on new general concepts or patterns that span multiple products we are very interested to hear about them.