Suggest an editImprove this articleRefine the answer for “What are the most common Redis use cases?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)Redis is most often used for caching (between an application and a slow DB), storing user sessions, message queues and pub/sub, real-time counters and rankings, geolocation, and rate limiting. **Key point:** what unites all these scenarios is a need for speed, low latency, and atomic operations - places where a traditional disk-backed DB would become a bottleneck.Shown above the full answer for quick recall.Answer (EN)ImageRedis is used most often where **speed**, **low latency**, and **simple data structures** matter. Here are the main scenarios where Redis gets used in practice: ### 1. Caching Redis often sits **between an application and a slow DB** (e.g. PostgreSQL). Frequently requested data is stored in Redis, so the disk doesn't have to be hit every time. Example: - Caching HTML pages, SQL query results, user profiles. - A TTL (key lifetime) automatically clears out stale data. *The result:* instant access to "hot" data and less load on the main database. ### 2. Storing user sessions Redis is often used for **temporary session storage**, auth tokens, or shopping carts. Example: - When a user logs into a site, their session (ID, login, time) is stored in Redis. - On logout or once the TTL expires, it's removed automatically. *The result:* fast session checks with no load on the SQL database. ### 3. Message queues and jobs Redis supports the **List** and **Stream** structures, making it convenient for building **task queues** and **Pub/Sub mechanisms**. Example: - Notification systems, order processing, distributed workers. - Redis Pub/Sub, for instantly broadcasting messages to subscribers. *The result:* simple, fast communication between microservices. ### 4. Counters, rankings, statistics Redis is a great fit for **real time**, updating likes, views, points, counters. Example: - Counting online users. - A leaderboard system (Sorted Set). - Monitoring metrics: requests, errors, load. *The result:* atomic operations and instant updates. ### 5. Geolocation and tracking Redis has a **GEO** data type, letting you store coordinates and run "near me" queries. Example: - Showing the nearest taxis, stores, couriers. *The result:* fast distance filtering with no complex calculations. ### 6. Locking and limits (rate limiting) Redis supports atomic operations, so you can cap the number of actions over a period. Example: - "No more than 5 login attempts per minute." - Implementing distributed locks. *The result:* protection against spam, overload, and abuse. **Summary:** Redis is used mainly for **caching, session storage, queues, counters, geolocation, and rate limiting**, places where you need **instant response, heavy load, and simple data structures**.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.