Digging into Valkey

### Overview In this presentation, Madelyn (engineer at AWS and creator of Valkey) and Kyle (developer advocate for the Valkey project) introduce Valkey, an open-source in-memory data store established under the Linux Foundation. They outline the historical background leading to the fork from Redis, detail the launch and current state of Valkey 7.2.5 GA, compare Valkey with other Redis alternatives, and describe the architectural roadmap and governance model going forward.

### Key Topics - **In-Memory Systems & Redis History**: The talk covers the historical motivation for in-memory systems—namely, fast writes, instant seeks bypassing spinning disks, and byte-level memory control. It traces Redis from Salvatore Sanfilippo's original project through early Ruby community adoption, clustering in 2014, and the 2020 transition to a multi-organization core team (including AWS, Alibaba, and Redis Labs). - **The License Transition & Fork**: On March 20, 2024, Redis moved away from open-source licensing to non-open source licenses (RSALv2 and SSPL) and removed the core team governance. In response, contributors established Valkey (initially known as placeholderkv) under the Linux Foundation to preserve a truly open, BSD 3-Clause licensed in-memory store. - **Landscape Comparison**: The speakers compare related projects across licensing and architecture, distinguishing Valkey (BSD 3-Clause, single-threaded C, Linux Foundation governance) from Redis (RSALv2/SSPL), Garnet (MIT, written in C#), Redict (LGPLv3, copyleft), KeyDB (BSD 3-Clause, multi-threaded C), and DragonflyDB (BSL, C++).

### Technical Details - **Compatibility & Migration**: Valkey 7.2.5 GA functions as a drop-in replacement based on the Redis 7.2 branch. It maintains near-zero functional changes from the base: identical APIs, return values, configuration syntax, and persistence file support (AOF and RDB snapshots). Operators can transition by pointing Valkey at existing persistence files or running heterogeneous clusters without breaking existing paths or symlinks. - **Future Technical Roadmap (Valkey 8 and Beyond)**: - *Cluster Reliability*: Fixing slot migration failure modes to prevent inconsistent cluster states during node failures, alongside ongoing efforts toward 'Cluster V2' (adopting centralized state management inspired by Kubernetes to replace noisy peer-to-peer reconciliation). - *Performance & Concurrency*: Introducing multi-threading improvements to support vertical scaling and optimizing single-core execution for modern CPU parallelism. - *Memory Density*: Optimizing data structures (e.g., removing unnecessary pointers) to increase cache hit rates and lower memory footprints. - *Extensibility*: Expanding beyond traditional types through native modules, including native JSON support, vector similarity search for generative AI workloads, time-series data, and rate limiting. - **Contribution & Governance**: Contribution requires compliance with a Developer Certificate of Origin (DCO) using Git commit sign-offs (`-s`), with no Contributor License Agreement (CLA) required.

### Takeaways Valkey provides an open-source, BSD 3-Clause licensed continuation of Redis backed by a vendor-neutral governance model through the Linux Foundation and a Technical Steering Committee (TSC). The project emphasizes seamless backward compatibility for 7.2 migrations while steering future development toward multi-threaded performance, robust cluster management, improved memory density, and community-driven module extensibility.