Valkey, the open-source fork of Redis, emerged after licensing changes in March 2024 prompted a split from the original project. Since then, Valkey has focused heavily on performance enhancements, redesigning key low-level features to reduce memory usage and boost throughput. While it retains the core capabilities familiar to Redis users, the optimizations make it particularly appealing for high-demand applications where speed and efficiency are critical.
Key/value stores like Valkey remain essential for modern cloud-native development. They handle session state, caching, and other transient data needs, allowing applications to scale seamlessly on platforms like Kubernetes. Choosing between Redis and Valkey now comes down to specific project requirements, particularly around performance and memory efficiency, as the two projects have diverged enough to create meaningful differences.
Valkey Version 9.0 is nearing release, with most of the remaining work focused on finalizing a few high-priority features. Meanwhile, the current 8.1 release continues to be widely adopted. Interested developers can track the progress on GitHub, where the roadmap dashboard shows remaining tasks before general availability. This transparency helps teams plan migrations or new deployments with confidence.
Running Valkey on Microsoft’s Azure ecosystem requires some additional setup. While Azure provides managed Redis instances, Valkey currently needs to be self-hosted. Microsoft has published guidance for deploying Valkey on Azure Kubernetes Service (AKS), integrating with other open-source projects like Apache Kafka and Airflow. Implementing Valkey on AKS involves setting up a cluster, creating a KeyVault for secrets, and deploying the cache cluster as a node pool using Linux-based Standard D4 VMs. Though there’s no native Windows version, Linux hosts or Windows Subsystem for Linux (WSL) provide sufficient flexibility for local development and testing.