// screenshot of redis.io ↗
Redis is an in-memory key-value store used as cache, message broker, session store, queue, pub/sub, and primary database. Single-threaded, sub-millisecond latency, with extensive data structures (strings, hashes, lists, sets, sorted sets, streams, bitmaps, HyperLogLog). The default cache layer in modern web architecture.
Redis is an in-memory key-value store used as cache, message broker, session store, queue, pub/sub, and primary database. Single-threaded, sub-millisecond latency, with extensive data structures (strings, hashes, lists, sets, sorted sets, streams, bitmaps, HyperLogLog). The default cache layer in modern web architecture.
If your application needs to cache anything or coordinate state, Redis is almost always the answer.
Concrete scenarios where teams pick Redis over the SaaS alternative.
speed up DB queries via memoization
stateless app servers + session in Redis
Sidekiq, BullMQ, Celery all use Redis as queue backend
real-time messaging between services
counters + atomic increments per user/IP
If your team profile matches one of these, Redis is a strong fit out of the box.
caching DB queries / sessions
providing Redis as internal service
using pub/sub for live features
running async work via Redis queues
implementing rate limiting
When evaluating self-hosted options for this category, here are the dimensions on which Redis consistently lands above the alternatives.
The stack you'll plug Redis into — services, protocols, and adjacent apps in the BluixApps catalog.
redis:7-alpine (LTS minor version)/data for RDB + AOF/data (RDB + AOF files)Operational guidance from running this in production — what to do before you scale, what to lock down, what surprises people.
6379:6379 · redis:7-alpine