Redis · Solution
Session and cache layer
Store sessions and cached data in a dedicated Redis process — fast, simple, and separate from your primary database.
How it works
Point your existing session middleware at a Redis connection string and store session data as keys with a prefix and an expiry.
Drop-in session store
Point your existing session middleware at a Redis connection string.
Shared cache
Cache expensive queries or API responses with a simple TTL.
Code sample
jsExpress session middleware backed by Luceris Redis
import express from 'express';import session from 'express-session';import { RedisStore } from 'connect-redis';import { createClient } from 'redis'; const redis = createClient({ url: process.env.REDIS_URL });await redis.connect(); const app = express();app.use(session({ store: new RedisStore({ client: redis, prefix: 'sess:' }), secret: process.env.SESSION_SECRET, resave: false, saveUninitialized: false, cookie: { secure: true, httpOnly: true, sameSite: 'lax', maxAge: 60 * 60 * 24 * 30 * 1000 },})); app.get('/', (req, res) => { req.session.views = (req.session.views || 0) + 1; res.send(`Views: ${req.session.views}`);});Sizing
A typical web session is 1–5 KB. The Free tier (256 MB) holds ~50,000 active sessions. For HTTP caching, the working-set size matters more than memory — measure your hit rate at different database sizes and pick the one that gives you the latency you need.
Examples
- Local session storage during development
- Caching third-party API responses in tests
- Rate-limit counters for a prototype
Frequently asked questions
Does session data survive a restart?
Sessions survive a restart on plans with AOF persistence. On RDB-only plans you can lose the writes since the last RDB save.
How do I handle session-fixation rotation?
Use your framework's session-regeneration API at login — it deletes the old key and writes a new one. On Redis we recommend setting a max-age of 30 days as a backstop.
Should I run sessions and HTTP cache on the same database?
On the Free tier, yes — separate them by key prefix. On larger workloads, run separate databases so each keeps its own keyspace and memory budget.
Add a session store in minutes.
256 MB free Redis — enough for tens of thousands of sessions. Luceris Cloud is for development environments and not for production.