Book Image

Getting Started with NoSQL

By : Gaurav Vaish
Book Image

Getting Started with NoSQL

By: Gaurav Vaish

Overview of this book

<p>Relational databases have been used for decades, and in the last few years NoSQL has been a growing choice for large-scale web applications. Non-relational databases provide the scale and speed that you may need for your application. To switch you must know the options available, the advantages and drawbacks, and scenarios which it is suited to the most and where it should be avoided at all costs.<br /><br />Getting Started with NoSQL is a from-the-ground up guide that takes you from the very first steps to a real-world NoSQL application. It provides you with a step-by-step approach to design and implement a NoSQL application that will help you make clear decisions on database choices and database model choices. The book is suited for a developer, an architect, as well as a CTO.<br /><br />This book is a comprehensive guide to working with NoSQL. You will learn to make key decisions, and to design and implement NoSQL applications. You will learn about NoSQL jargon, data models, and databases on the market. The case studies and comparisons presented will help you to make a decision on whether or not to use NoSQL, and if so which model and product to use. This book is an indispensable resource for you to have in your library. You will learn everything you need to know about understanding and working with NoSQL and how to implement an application with the correct NoSQL for you.</p>
Table of Contents (14 chapters)

NoSQL approach


NoSQL-based solutions provide answers to most of the challenges that we put up. Note that if ACME Grocery is very confident that it will not shape up as we discussed earlier, we do not need NoSQL. If ACME Grocery does not intend to grow, integrate, or provide integration with other applications, surely, the RDBMS will suffice. But that is not how anyone would like the business to work in the long term.

So, at some point in time, sooner or later, these questions will arise.

Let us see what NoSQL has to offer against each technical question that we have:

  • Schema flexibility: Column-oriented databases (http://en.wikipedia.org/wiki/Column-oriented_DBMS) store data as columns as opposed to rows in RDBMS. This allows flexibility of adding one or more columns as required, on the fly. Similarly, document stores that allow storing semi-structured data are also good options.

  • Complex queries: NoSQL databases do not have support for relationships or foreign keys. There are no complex queries...