Today we’re happy to tell the world about the general availability of Redis version 7.0, as announced at the Redis Days SF keynote earlier this year. The release has been under development for almost a year, and three release candidates preceded it, so we feel it is stable enough for use in production.
Upgrading from earlier versions is a relatively straightforward process, as backward compatibility has always been a design principle of the Redis project. However, before upgrading to Redis 7.0, please take a few minutes and get acquainted with the new version by reading the release notes.
In a nutshell, Redis 7.0 includes incremental improvements to almost every one of its aspects. Most notable are Redis Functions, ACLv2, command introspection, and Sharded Pub/Sub, which represent a significant evolution of existing features based on users’ feedback and lessons learned in production.
Version 7.0 adds almost 50 new commands and options to support this evolution and extend Redis’ existing capabilities. For example, the bitmap, list, set, sorted set, and stream data types have all been added with functionality that supports their use cases for data management. In addition, cache semantics have been extended to support existential and comparative modifiers.
While user-facing features are easy to boast of, the real “unsung heroes” in this version are efforts to make Redis more performant, stable, and lean. A large share of our developers’ brain cycles was invested in making the operation of Redis more effective by focusing on its performance vis-à-vis the resources that it uses. Redis 7.0 brings a number of improvements to almost every subsystem it manages, including memory, computing, network, and storage. Whereas some optimizations are enabled by default, others may require configuration. Please refer to the inline documentation in the redis.conf file for details.
While the release of this new version is something for us to celebrate here at Redis, we are already busy working on making Redis 7.2 a reality. If you encounter any issues or have thoughts to share, we’d love to hear from you at the Redis repository.