Video
Refreshing and Extending Redis.io
Learn more
Become a Redis expert.
See what's new in Redis University
share
Today we’re thrilled to announce Redis Stack. Redis Stack consolidates the capabilities of the leading Redis modules into a single product, making it easy for developers to build modern, real-time applications with the speed and stability of Redis.
At Redis, we’re building a real-time data layer to meet the universal demand for responsive, low-latency applications and services.
To build applications that provide real-time experiences, you need a database that can process any request, whether a simple object retrieval, a search, or a complex aggregation, with the fastest possible response times, preferably in less than a millisecond. The rationale is simple: in a typical application, every user interaction generates multiple calls to the database, which can result in significant overhead; if you add to that the round trip latency of the network between the end-user and the app, every extra millisecond spent in the database makes it more difficult to deliver a real-time end-user experience.
This holds no matter the data model, be it a key/value, document, stream, graph, time series, or probabilistic data structures.
As the trend of the last 24 months at DB-Engines makes clear, the fastest-growing data models are key-value, search, document, graph, and time series. This trend also shows that fewer and fewer developers are choosing to model their applications with relational databases.
As it turns out, we’ve spent the past four years building several dedicated data engines that extend the core key/value data-structure functionality of Redis with modern data models and data processing capabilities, such as search, document, graph, time series, and probabilistic data structures.
Implemented as Redis modules, we’ve built these engines from the ground up using the same design principles as open source Redis, with an in-memory architecture and an efficient codebase written in C or Rust, allowing developers to run a wide variety of data workloads with the lowest latency possible.
After listening to our community and customers, we realized that we needed to simplify the developer experience of the leading Redis modules and the capabilities they provide, along with their documentation and clients that support their functionality. We wanted to help developers be fully productive from the moment they started using Redis.
This is why we created Redis Stack.
Redis Stack unifies the leading Redis modules in a single product. This makes it easy to start building with our Redis-based search, document, graph, and time series capabilities.
Redis Stack is a suite of three components:
Redis Stack is now generally available for Redis 6.2, and we also have a release candidate for Redis 7.0.
We’re providing several ways to quickly get started with Redis Stack:
Once you have Redis Stack Server up and running, you can immediately leverage RedisInsight to visualize, analyze and optimize your Redis data. RedisInsight includes a series of guides that walk you through several Redis Stack use cases.
On the client side, we’re supporting Redis Stack in several leading Redis clients — Jedis (Java), redis-py (Python), and node-redis (JavaScript) — and with our new object mapping libraries (redis-om-spring, redis-om-python, redis-om-node, redis-om-dotnet).
You can clone an example repository for each language we support to start developing your freshly created database.
We’re excited about the universe of real-time applications that we believe Redis Stack will make possible. But we’d like to be very clear that Redis Stack is not a replacement for Redis.
Redis is a core, open source technology, and our focus on its continued development is not changing. You’ll always have the option to download, build, install, and run open source Redis.
When you’re ready to run Redis Stack, you can easily migrate your data using the Redis replication mechanism or by loading your RDB or AOF files.
All the codebase components of Redis Stack are open and free for everyone to use, but we still want to be very clear about the Redis Stack licensing model since we updated our licenses as mentioned in this blog:
We’re committed to continuing to develop Redis as an open-source project, supporting one of the largest developer communities on earth, and cooperating with our growing number of active contributors to the project.
We will continue adding capabilities to Redis Stack, to allow developers to quickly and easily develop modern applications for the real-time era that are entirely based on Redis.
To learn more about Redis Stack and the capabilities it provides, tune into deep-dive sessions on Redis Stack delivered at our RedisDays event available now on-demand.
We’ve also put together quick answers to anticipated questions – on the short FAQ section.
Finally, we’d love to get your feedback on Redis Stack. Send us a note on the Redis mailing list or join the Redis Discord server to let us know what you think.
Redis Stack is a single package that includes open source Redis with the leading Redis modules (Redis Stack Server), and RedisInsight.
For the initial release of Redis Stack Server, we’re including five modules: RedisJSON, RedisSearch, RedisGraph, RedisTimeSeries, and RedisBloom.
Redis Stack is supported by official Redis client and object mapping libraries and allows developers to easily use the advanced Redis Stack capabilities with several application frameworks, including Spring, ASP.Net Core, Express, and FastAPI.
Redis Stack lets developers:
We’ll consider adding new capabilities or even modules to Redis Stack if:
RedisGears adds database triggers, stream processing, distributed functions, and full programmability to Redis.
We will add RedisGears to Redis Stack once the support for JavaScript is GA, later this year.
Yes, you can!
The Redis object-mapping libraries provide a level of abstraction above the Redis command API, much like an ORM does for a SQL database. Let’s distinguish the core Redis client libraries from Redis object mapping libraries.
These object-mapping libraries always depend on one or more core Redis libraries.
Currently, the recommended client for .NET developers is StackExchange, which is not formally supported by Redis, Inc. You can extend the client with NRediSearch for RediSearch, NRedisGraph for RedisGraph, and NRedisTimeSeries for RedisTimeSeries. You can also use the redis-om-dotnet library that builds on top of StackExchange.
RedisInsight is not yet available on Redis Enterprise Cloud. However, you can connect with the RedisInsight application to your cloud database. We plan to add RedisInsight to the cloud later this year.
Yes, you can leverage our Replica-Of solution to migrate your database to our fully managed cloud service without any downtime.
