Book Image

Redis Stack for Application Modernization

By : Luigi Fugaro, Mirko Ortensi
1 (1)
Book Image

Redis Stack for Application Modernization

1 (1)
By: Luigi Fugaro, Mirko Ortensi

Overview of this book

In modern applications, efficiency in both operational and analytical aspects is paramount, demanding predictable performance across varied workloads. This book introduces you to Redis Stack, an extension of Redis and guides you through its broad data modeling capabilities. With practical examples of real-time queries and searches, you’ll explore Redis Stack’s new approach to providing a rich data modeling experience all within the same database server. You’ll learn how to model and search your data in the JSON and hash data types and work with features such as vector similarity search, which adds semantic search capabilities to your applications to search for similar texts, images, or audio files. The book also shows you how to use the probabilistic Bloom filters to efficiently resolve recurrent big data problems. As you uncover the strengths of Redis Stack as a data platform, you’ll explore use cases for managing database events and leveraging introduce stream processing features. Finally, you’ll see how Redis Stack seamlessly integrates into microservices architectures, completing the picture. By the end of this book, you’ll be equipped with best practices for administering and managing the server, ensuring scalability, high availability, data integrity, stored functions, and more.
Table of Contents (18 chapters)
1
Part 1: Introduction to Redis Stack
6
Part 2: Data Modeling
11
Part 3: From Development to Production

Configuring Redis for durability, consistency, and availability

For those scenarios where reliability matters besides availability, you can consider the following configurations.

Configuring snapshots

Snapshots (also called Redis database snapshots, or RDBs) provide a consistent binary dump of the data stored in the keyspace and are used to perform data recovery to a specific point in time. You should set the following in the configuration file:

save 900 1000
dbfilename "dump.rdb"

These settings enable snapshots every 900 seconds if at least 1,000 keys have changed. This kind of persistence is good for point-in-time restores and is also considered a backup. So, from time to time, you should copy the RDB snapshot file to an external storage device on a different, possibly remote host (invoking a script with cron, as an example) to discard major incidents affecting the local storage device. This method cannot be considered valid to achieve a good recovery point objective...