The first optimization is a dictionary per slot (16,384 of them in total), where each dictionary stores data for a given slot. With this simplified architecture, Valkey can handle memory more efficiently, allowing for an increase in capacity which translates to more keys stored per node. This change is significant because it directly addresses performance needs while maintaining compatibility with existing Redis command structures.
While this is a major version, Valkey takes command set compatibility seriously: Valkey 8.0.0 makes no backwards incompatible changes to the existing command syntax or their responses, ensuring that current users can upgrade without issue. However, due to threading changes, it is advisable for users to assess their infrastructure to optimize performance for this new version.
Redis moved away from open source almost 6 months ago, and I still vividly remember discussing on Slack with my former Redis contributors what we were going to do. The transition prompted us to rally together, leading to 500k container pulls and contributions from over 100 individuals across the server and client ecosystem, firmly establishing Valkey as a supported alternative.
Valkey is a high-performance key/value datastore that supports various workloads including caching, message queues, and serving as a primary database. With the option to operate as a standalone daemon or in clusters, Valkey provides users with robust replication and high availability options, catering to diverse application needs.
Collection
[
|
...
]