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

Evaluating query performance


As you develop and operate applications with RethinkDB, you may need to analyze the performance of the application and its database. Usually, when you encounter degraded performance, it is often due to incorrect database access strategies or poorly-written queries.

RethinkDB provides a tool called a database profiler that shows performance characteristics of queries executed on the database. This tool is accessible from the database web interface. Once enabled, the profiler will present you with a breakdown of all operations performed on the database during the execution of a query, including the time it took to run each operation.

Probably, the most useful piece of information provided by the database profiler is the server time, which represents the total execution time of a query on the database server. This doesn't include the additional overhead caused by the network round trip; however, if you are interested in the total time, including the time it took...