Redis for Builders
Redis is an in-memory data store used by companies at every scale to cache expensive queries, manage rate limits, power background job queues, and broadcast real-time events. This course teaches you the Redis data structures and patterns you actually encounter when building Node.js and Next.js applications.
What you'll learn
Course outline
Free — start now
Full course — $49 one-time
Lists
LIST: queues, stacks, and ordered collections
Sets and Sorted Sets
SET and SORTED SET: unique members and leaderboards
TTL, EXPIRE, and Cache Invalidation
TTL, expiry, and the art of cache invalidation
Caching Patterns
Cache-aside, write-through, and read-through
Queues with BullMQ
Background job queues with BullMQ
Pub/Sub
Pub/Sub: broadcasting real-time events across services
Redis in Next.js
ioredis, Upstash, and rate limiting in Next.js applications
Get the full course
All 10 lessons. Caching, queues, pub/sub — the Redis skills that separate senior from junior.
Written by the RadarTrek editorial team · Reviewed June 2026
About this course
Redis is an in-memory data store used by companies at every scale to solve problems that relational databases are poorly suited for: caching expensive query results to serve them in microseconds, rate-limiting API endpoints, managing background job queues, storing user sessions, building real-time leaderboards, and broadcasting events with pub/sub. Because Redis keeps data in RAM rather than on disk, reads and writes are orders of magnitude faster than a PostgreSQL query — a cache hit that takes 0.1 milliseconds versus a database round trip taking 5–50 milliseconds is a meaningful difference at scale. Understanding when and how to use Redis is one of the skills that separates junior developers from seniors who can build systems that stay fast under load.
In the Node.js and Next.js ecosystem, Redis is accessed via ioredis (for traditional servers) or Upstash (a serverless-friendly managed Redis with a REST API, ideal for Vercel deployments). BullMQ, one of the most popular background job libraries, uses Redis as its queue store. This course teaches the Redis data structures — Strings, Hashes, Lists, Sets, and Sorted Sets — alongside the caching patterns, rate-limiting implementations, and BullMQ queue setup that you will encounter in real production codebases.
Frequently asked questions
What is Redis and what is it used for?
Redis is an in-memory key-value store that makes data available at RAM speed — typically 0.1–1 millisecond per operation versus 5–50 milliseconds for a database query. The most common uses in web applications are: caching expensive database query results so repeated requests are served instantly, rate-limiting API endpoints by counting requests per key with TTL expiry, background job queues via BullMQ, user session storage, real-time leaderboards with Sorted Sets, and pub/sub for broadcasting events across services.
Do I need to install Redis locally or can I use a managed service?
For local development, you can run Redis locally via Docker with a single command: `docker run -p 6379:6379 redis:alpine`. For production and serverless environments like Vercel, Upstash offers managed Redis with a free tier and a REST API that works without persistent TCP connections. Railway and Render also offer managed Redis add-ons. For heavy workloads, ElastiCache (AWS) and Memorystore (Google Cloud) are the enterprise managed options. This course covers both local setup and Upstash for serverless.
How is Redis different from a regular database like PostgreSQL?
PostgreSQL stores data persistently on disk with full ACID transaction support and is optimised for complex relational queries across large datasets. Redis stores data primarily in RAM, making it dramatically faster for simple key-value operations but unsuitable as a primary database for most applications — RAM is expensive and Redis has limited query capabilities compared to SQL. They are complementary: PostgreSQL stores your canonical data, Redis caches hot subsets of it or handles workloads where speed matters more than complex querying.
What is BullMQ and how does it relate to Redis?
BullMQ is the most popular background job queue library in the Node.js ecosystem. It uses Redis as its storage layer — jobs are stored as Redis data structures, and BullMQ provides the worker pattern, retry logic, job priorities, delayed jobs, and rate limiting on top. Any task that should not block an HTTP response — sending emails, generating PDFs, processing uploads, calling slow third-party APIs — belongs in a BullMQ worker. This course covers BullMQ queue setup, worker definition, and job event monitoring.
Is Redis worth learning in 2026?
Absolutely. Redis is one of the most durable skills in the backend ecosystem — it has been the go-to in-memory store for over 15 years and remains the default choice for caching, queues, and real-time features in 2026. BullMQ, the dominant Node.js job queue, requires Redis. Rate limiting at scale almost always uses Redis. If you are building any application that needs to handle meaningful traffic, Redis knowledge pays dividends immediately. The Upstash serverless model also makes Redis accessible in Vercel-hosted Next.js projects that previously had no easy access to persistent TCP connections.