Book Image

Mastering Redis

By : Jeremy Nelson
Book Image

Mastering Redis

By: Jeremy Nelson

Overview of this book

Redis is the most popular, open-source, key value data structure server that provides a wide range of capabilities on which multiple platforms can be be built. Its fast and flexible data structures give your existing applications an edge in the development environment. This book is a practical guide which aims to help you deep dive into the world of Redis data structure to exploit its excellent features. We start our journey by understanding the need of Redis in brief, followed by an explanation of Advanced key management. Next, you will learn about design patterns, best practices for using Redis in DevOps environment and Docker containerization paradigm in detail. After this, you will understand the concept of scaling with Redis cluster and Redis Sentinel , followed by a through explanation of incorporating Redis with NoSQL technologies such as Elasticsearch and MongoDB. At the end of this section, you will be able to develop competent applications using these technologies. You will then explore the message queuing and task management features of Redis and will be able to implement them in your applications. Finally, you will learn how Redis can be used to build real-time data analytic dashboards, for different disparate data streams.
Table of Contents (18 chapters)
Mastering Redis
About the Author
About the Reviewers

Docker and Redis issues

In the chapter on Redis Cluster and Sentinel we didn't cover some major issues that can occur when trying to deploy Redis's high availability solution when using Docker. Docker performs a dynamic port reallocation when using the –p directive when launching a new Docker container. Sentinel's auto discovery of other running Sentinel process as well as discovering a list of slaves from a master assumes a fixed port numbers, this Sentinel feature will break if the internally running Sentinel on a Docker container is mapped to a different port.

To use Sentinel with Docker you have two options: the first is to update the sentinel announce-ip and sentinel announce-port for each of Docker container running Sentinel so that the Docker Sentinel is broadcasting (or announcing) the correct IP address and port number to other running Sentinel instances in your Redis operation. The second option (and likely the easiest to implement if you are starting your Sentinel setup and Redis...