Book Image

Mastering RethinkDB

By : Shahid Shaikh
Book Image

Mastering RethinkDB

By: Shahid Shaikh

Overview of this book

RethinkDB has a lot of cool things to be excited about: ReQL (its readable,highly-functional syntax), cluster management, primitives for 21st century applications, and change-feeds. This book starts with a brief overview of the RethinkDB architecture and data modeling, and coverage of the advanced ReQL queries to work with JSON documents. Then, you will quickly jump to implementing these concepts in real-world scenarios, by building real-time applications on polling, data synchronization, share market, and the geospatial domain using RethinkDB and Node.js. You will also see how to tweak RethinkDB's capabilities to ensure faster data processing by exploring the sharding and replication techniques in depth. Then, we will take you through the more advanced administration tasks as well as show you the various deployment techniques using PaaS, Docker, and Compose. By the time you have finished reading this book, you would have taken your knowledge of RethinkDB to the next level, and will be able to use the concepts in RethinkDB to develop efficient, real-time applications with ease.
Table of Contents (16 chapters)
Mastering RethinkDB
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Data modeling for our application


Since our data is unified and should be visible in an accurate manner to every administrator across the world, we are going to store our polls in the following manner:

{ 
  "Question" : "Which is best phone?", 
  "polls" : [ 
    { 
      "option" : "iPhone", vote : 0 
    }, 
    { 
      "option" : "Android", vote : 0 
    } 
   ] 
} 

As you are aware, in RethinkDB we store documents (JSON for geeks) and for our application we are going to store data in the former manner.

Each poll created by admin will be stored in RethinkDB and on each vote, we will update the vote field of our specific document, which in turn will be broadcast to every connected client to reflect the change.

Although there is no restriction on us to perform mandatory data modeling, NoSQL databases provide us the power to have schema less design. This data modeling is just for representation and explanation purposes.

Let's move ahead...