There are already good Redis tools for NestJS.
Most of them mainly help you connect NestJS to Redis and use the Redis client. That's useful, but as a project grows, you often need to build more things around Redis yourself: caching, TTL, cache invalidation, locks, rate limiting, sessions, monitoring, and more.
That's why I built Redora.
Redora adds a higher-level layer for using Redis in NestJS.
Today it includes:
- Redis service
- Cache service
- Cache decorators
- "remember()" caching
- TTL and expiration policies
- Cache tags and eviction
- Distributed locks
- Redis diagnostics
- Logger and observability
_The idea is simple:
Redis gives you the primitives. Redora gives you the architecture._
What I'm working on next
I want Redora to cover more of the common things developers use Redis for:
- Session management
- Rate limiting for OTP, login, and APIs
- Distributed locks
- Message queues
- Redis for AI applications
- Redis and Valkey support
- More monitoring and telemetry
Redora is still early and I'm building it in public.
📦 "npm i redora"
🌐 https://redora-sdk.com
If you use NestJS and Redis, try it and let me know what you think. I'd really like to hear what works, what's missing, and what you would change.
