An in-memory data structure store used as a cache, database, message broker, and vector query engine for real-time applications.
Redis is an open-source, in-memory data structure store that functions as a high-performance cache, database, and message broker. It solves the need for sub-millisecond data access in real-time applications by keeping data in RAM and supporting a wide variety of data models, from simple key-value pairs to JSON documents and vector embeddings.
Developers and architects building real-time web applications, microservices, AI-powered features, or systems requiring high-throughput data processing with low latency.
Developers choose Redis for its unparalleled speed, versatility across multiple use cases (caching, messaging, search, AI), and its simple, well-documented protocol. It eliminates the need for multiple specialized data stores by providing a unified, extremely fast data platform.
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Redis achieves sub-millisecond latency by keeping data primarily in memory, as highlighted in the 'Why choose Redis?' section for real-time responsiveness.
Supports a wide range of data types from strings to JSON, streams, and vector sets, enabling use cases from caching to AI, as detailed in the data types section.
The modules API allows for custom commands and extensions like Bloom filters and vector search, though some require specific build flags as noted in the README.
With a text-based protocol and well-documented commands, Redis is battle-tested and easy to integrate, backed by a large community and client libraries.
Building from source with all modules requires specific flags and dependencies across different OSes, as shown in the lengthy, OS-specific build instructions.
Being in-memory, Redis can be costly for large datasets, requiring careful configuration for persistence, eviction policies, and scaling.
Advanced features like probabilistic data structures need modules enabled at build time, adding setup complexity and potential compatibility issues.