Applications commonly use session stores to track user identity, login credentials, personalization information, recent actions, shopping cart items, and more. The application reads-and-writes this data only to the session store, so speed and durability are critical. Redis Enterprise provides all the essential requirements for a session store: speed, scale, availability, and cost efficiency.
How session store works in a mobile banking application
When the user logs into the application, a user session is created.
For the duration of the user session, the session data is stored in Redis Enterprise as a key:value pair with the user identifier as the key and session data as the value. While the session is live, the application can consult and update the user information in Redis Enterprise.
How Redis Enterprise solves your challenges
The problem
The Redis Enterprise solution
Slow user experiences when applications read or write session data, as the result of latency.
Redis Enterprise’s real-time speed enables applications to instantly read and write session data for instantly responsive users sessions.
Difficulty scaling session storage during periods of peak activity.
Redis Enterprise is highly scalable. It maintains sub-millisecond latency at high volumes to enable flawless user sessions even during periods of peak demand.
Application unavailability or loss of critical customer data from session storage failure.
Redis Enterprise is highly resilient, with 99.999% uptime, to ensure users sessions are always consistent and responsive.
Benefits of using Redis Enterprise for session storage
More responsive applications with more responsive user sessions
Increased scalability to ensure users sessions perform seamlessly even during times of peak demand
High availability and resilience avoid application outages for the session store that render applications unavailable or unusable
A session store is a location where an application stores data about user interactions and current status during a given session, such as a website or a game. Session state is typically stored as a key-value pair, with user identifier as the key and session data as the value.
What kind of data can be stored in session storage?
Apps commonly store data related to user activity like identity, login credentials, personalization information, recent actions, shopping cart, and more. Session data can vary by application type or industry, for example an e-commerce retailer may hold a customer’s login and authentication details, shopping cart items, browsing history, preferences, and recommendations. A session for a brokerage application may store an investor’s portfolio details, preferred portfolio views, current trades, and open orders. A video game session may keep the player’s current level, score, and control configuration and maintain the game’s state.
How long does session data last?
Session data is held in Redis Enterprise for the duration of a user session, it can then be volatile (and discarded) or persisted to a primary database.
When should I use session storage?
Session storage should be used for all customer-facing applications, especially when there is a large volume of users and application responsiveness is important.
By continuing to use this site, you consent to our updated privacy agreement. You can change your cookie settings at any time but parts of our site will not function correctly without them.
Redis Enterprise’s real-time speed enables applications to instantly read and write session data for instantly responsive users sessions.
