The latest articles on DEV Community by Nebyu Samuel (@neba). https://dev.to/neba https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4090648%2Fb617cba3-df8e-41ae-a3fa-a4fd9dca0da1.png https://dev.to/neba en Nebyu Samuel Sun, 23 Aug 2026 09:39:06 +0000 https://dev.to/neba/redora-031-redis-for-nestjs-2blh https://dev.to/neba/redora-031-redis-for-nestjs-2blh <p>There are already good Redis tools for NestJS.</p> <p>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.</p> <p>That's why I built Redora.</p> <p>Redora adds a higher-level layer for using Redis in NestJS.</p> <p>Today it includes:</p> <ul> <li>Redis service</li> <li>Cache service</li> <li>Cache decorators</li> <li>"remember()" caching</li> <li>TTL and expiration policies</li> <li>Cache tags and eviction</li> <li>Distributed locks</li> <li>Redis diagnostics</li> <li>Logger and observability</li> </ul> <p>_The idea is simple:</p> <p>Redis gives you the primitives. Redora gives you the architecture._</p> <p><strong>What I'm working on next</strong></p> <p>I want Redora to cover more of the common things developers use Redis for:</p> <ul> <li>Session management</li> <li>Rate limiting for OTP, login, and APIs</li> <li>Distributed locks</li> <li>Message queues</li> <li>Redis for AI applications</li> <li>Redis and Valkey support</li> <li>More monitoring and telemetry</li> </ul> <p>Redora is still early and I'm building it in public.</p> <p>📦 "npm i redora"<br> 🌐 <a href="https://redora-sdk.com" rel="noopener noreferrer">https://redora-sdk.com</a></p> <p>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.</p> redis nestjs node typescript