Book Image

Redis Applied Design Patterns

By : Arun Chinnachamy
Book Image

Redis Applied Design Patterns

By: Arun Chinnachamy

Overview of this book

<p>With new data stores making their way onto the market, it's necessary for businesses to understand the features and techniques to use data stores most effectively. Redis Applied Design Patterns is designed to guide you into the world of Redis and will help you understand how business problems can be solved using Redis in your application stack.</p> <p>This book introduces you to the NoSQL way of thinking and how it is different from SQL. It helps you understand various functionality of Redis through a series of use cases designed for you to learn the more complex and less well-known features of Redis in an incremental way. By the time you've read this book, you will be capable of designing a system using Redis. This book will guide you through various use cases along with code samples, easy-to-understand diagrams, and tips to help you take advantage of Redis. The book explains the benefits of adding Redis to the application stack and discusses various practical use cases for Redis such as the caching system, commenting system, and social networking.</p>
Table of Contents (18 chapters)

Session management and analysis using Redis


Sessions allow the web application to maintain the state across multiple requests. There are times when we need to store a lot of real-time session data. Saving the session data in a cookie is not always the best approach. So, it makes sense to move from cookie-based management to server-side session management. There is no limit to the amount of data we can store as session data. Typically, session data is stored in a temporary directory and the same variables are read on subsequent requests.

Why use Redis

If we have to use a load balancer with multiple web servers behind it, we need to centralize the session information. If not, we will end up having an inconsistent experience for the user. Let's say that the first request from the user was directed to server A, which then created the required session variables. If the subsequent request is directed to Server B by the load balancer, the session variables are lost and will be initialized again.

To...