Book Image

Getting Started with RethinkDB

By : Gianluca Tiepolo
Book Image

Getting Started with RethinkDB

By: Gianluca Tiepolo

Overview of this book

RethinkDB is a high-performance document-oriented database with a unique set of features. This increasingly popular NoSQL database is used to develop real-time web applications and, together with Node.js, it can be used to easily deploy them to the cloud with very little difficulty. Getting Started with RethinkDB is designed to get you working with RethinkDB as quickly as possible. Starting with the installation and configuration process, you will learn how to start importing data into the database and run simple queries using the intuitive ReQL query language. After successfully running a few simple queries, you will be introduced to other topics such as clustering and sharding. You will get to know how to set up a cluster of RethinkDB nodes and spread database load across multiple machines. We will then move on to advanced queries and optimization techniques. You will discover how to work with RethinkDB from a Node.js environment and find out all about deployment techniques. Finally, we’ll finish by working on a fully-fledged example that uses the Node.js framework and advanced features such as Changefeeds to develop a real-time web application.
Table of Contents (15 chapters)
Getting Started with RethinkDB
Credits
About the Author
Acknowledgement
About the Reviewer
www.PacktPub.com
Preface
Index

Monitoring RethinkDB


This section is all about the tools that you can use to monitor and understand the events that occur in the lifetime of your RethinkDB cluster.

Once you have a web application up and running, how do you know what it's doing? System tables to the rescue!

RethinkDB provides us with some system tables that we can query to learn about the issues that affect the cluster or queries that are running. These tables give you a better picture of what RethinkDB is doing.

Monitoring issues

The issues table is a RethinkDB system table that provides information on problems that are detected within the cluster; when a problem is detected, a document describing it is added to the table, whereas in normal conditions, the table is empty.

You can query the current_issues table by running the following query:

r.db("rethinkdb").table("current_issues").run(conn, callback);

This table can be extremely useful for monitoring purposes, as you can write a Node.js script that uses Changefeeds to receive...