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

Accessing changefeed (real-time feed) in RethinkDB


We had mentioned in Chapter 1, The RethinkDB Architecture and Data Model, that the real-time feature of RethinkDB is called changefeed. It is the heart of the RethinkDB real-time functionality. RethinkDB changefeed provides continuous live updates about the changes happening in the subscribed table.

In order to avail the feature of changefeed, you just need to attach your listener for the particular table, and you should receive every single minor update happening in the table such as addition, deletion, update, and so on.

Let us demonstrate this using our users table. Here is the piece of code that will add the listener to the table:

rethinkdb.table("users").changes().run(connection,function(err,cursor) { 
if(err) { 
throw new Error(err); 
  } 
cursor.each(console.log); 
}); 

That's it! Run the code on a separate terminal in order to observe the behavior. Let's try to add a new document into the table and see...