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

Securing RethinkDB


In this section, we will look at some basic security mechanisms that can help secure the database.

Earlier in the book, I mentioned that RethinkDB was being actively developed and that there maybe features that have been added since the publication of this book. This is especially true for security mechanisms in RethinkDB. Although, there are already some basic security options available while I'm writing these lines, more features are being discussed.

Securing your RethinkDB cluster is extremely important as the default options allow queries to be executed by anyone. If your database instance is on a public network, anyone can access the web interface and driver ports. Thus, anyone can practically create tables, delete documents, and change database settings.

The very best thing that you can do to secure your database is to run it on a private network that doesn't allow access from the outside world. However, this may not always be feasible, especially if you're working...