Caching, rate-limiting, geo-positioning, and other Redis traditional use cases

Implementing the many use cases that companies demand from their technical staff requires a technological stack and a competence development plan to sustain the efforts of designing, implementing, testing, and maintaining a solution. Evaluating and benchmarking the different options is time-consuming, and introducing a new technology demands processes and often increases the time to market for new features and products, thus slowing down the innovation and competitiveness of a company. Redis Stack is often regarded as a Swiss Army knife when it comes to solving different problems. As a data structures server, it allows you to transfer many responsibilities from application servers or specialized databases to a single, compact database server. In this section, we will recap the classical use cases that made Redis popular. Those uses include the following:

• Caching
• Session store
• Rate limiter...