Which is NOT a typical Redis use case?
Options
- Caching the data that is read very frequently
- Counters that are used for rate limiting
- Storing the sessions of the users
- Primary store for complex relational reports (Correct option)
Answer
Primary store for complex relational reporting
Why
Redis is an extremely fast in-memory key-value store with useful data types (strings, lists, sets, sorted sets, hashes).
Typical uses: cache, counters for rate limiting, sessions, queues, leaderboards, distributed locks.
It is not designed for complex queries, joins and reports; that is the job of a relational database or data warehouse.
Remember
Redis = fast memory store for cache, counters, sessions, queues.