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)

Web-scale application


This last application type is probably more relevant today in consumer applications, whether they are completely web-based or mobile-native apps or a combination of both.

Some of the key characteristics of this type of application are:

  • The application should be able to scale because of the enormous volume of content that it operates on, the sheer number of users, and the vast geography where the users access it because of which one datacenter is unfeasible.

  • The users of this application may be fine working with non-real-time, relatively stale data. The staleness may range from few tens of milliseconds to few days, but the latest data may definitely not be available within the fraction of millisecond.

  • The schema may evolve over time as the application allows integration with other applications.

  • Since the data can never be completely normalized or denormalized, the relationships will exist.

An example of this application is a web analytics application or a social microblogging...