What’s on the roadmap for the open-soure Redis alternative?
When Valkey, the high performance key-value database, was announced as the open-source alternative to Redis earlier this year, it set the community alight. Under the Linux Foundation’s governance, Valkey’s maintainers have signalled that the project will evolve considerably throughout 2025, with performance, extensibility, and memory efficiency in mind.
But once you’ve migrated to Valkey, what can you expect? What innovations will we see from contributors such as AWS, Alibaba, Google Cloud, Ericsson, Huawei, and Tencent? And how can you get involved in the hottest OSS project in the ecosystem?
UpCloud’s Senior Software Engineer Bachir Khiati and Kyle Davis, Senior Developer Advocate at Valkey, got together for a fireside chat to dig into future updates and releases – from multi-threaded architectures, to optimized dictionaries. Here’s the Q&A from their session, which you can also watch on YouTube.
Background
Q: What is Valkey, and how did it originate?
A: Valkey is a Linux Foundation project that originated as a fork of Redis. Redis, originally created by Salvatore Sanfilippo, became widely adopted for its high-performance capabilities. Redis transitioned from community governance to being controlled by Redis Inc., which led to a controversial license change in March 2024. This change prompted contributors from multiple organizations to fork Redis at version 7.2, forming Valkey. Unlike Redis, Valkey is neutrally governed under the Linux Foundation, ensuring open-source integrity and community control.
Q: Valkey vs Redis – how do these projects differ?
A: Initially, Valkey 7.2 was nearly identical to Redis 7.2, with changes limited to name replacements for legal reasons. However, as the two projects evolve, they are diverging in features and governance. Valkey’s roadmap emphasizes open-source innovation, performance optimization, and memory efficiency, setting it apart from Redis, which operates under a proprietary license model.
Q: What are the main advantages of Valkey over Redis?
A:
- Open-Source Commitment: Valkey ensures its features remain open-source, avoiding paywalls or restrictive licenses.
- Neutral Governance: Valkey’s neutral governance under the Linux Foundation eliminates single-vendor control, providing long-term stability.
- Performance Gains: The release of Valkey 8.0 introduces a completely rewritten multi-threading architecture, optimized for modern CPUs, resulting in significant performance improvements.
- Memory Efficiency: Enhanced dictionary structures reduce memory usage, enabling users to store more data on the same infrastructure.
Q: Why did some forks of Redis fail while Valkey gained traction?
A: Valkey benefits from:
- Contributor Expertise: Valkey’s core contributors include experienced Redis developers and representatives from major tech companies like Google, AWS, and Alibaba.
- Linux Foundation Support: Neutral governance ensures broad adoption and trust.
- Open-Source Advocacy: Unlike forks, Valkey maintains a commitment to open-source principles, attracting a wide range of supporters.
Valkey Roadmap
Q: What changes will Valkey 8.0 bring?
A: Valkey 8.0 introduces two major advancements:
- Multi-Threaded Architecture: This revamp enables Valkey to leverage modern multi-core CPUs for IO operations while maintaining single-threaded data access guarantees.
- Optimized Dictionaries: The improved dictionary structure reduces memory overhead, enabling more efficient data storage.
Additionally, Valkey 8.0 ensures backward compatibility, meaning existing applications can transition seamlessly.
Q: What features can we expect in Valkey 8.1 and beyond?
A:
- Version 8.1 (Upcoming): Enhancements include native support for JSON, Bloom filters, and vector similarity search, implemented as modular extensions.
- Version 9.0 (Planned for 2025): A major architectural overhaul is expected with V2 clustering, which will streamline node management and scalability.
Q: How is Valkey ensuring stability for enterprise users?
A: Valkey’s technical steering committee prioritizes backward compatibility, ensuring APIs remain stable across versions. This focus benefits industries like telecom, where infrastructure updates are challenging and costly.
Q: How does Valkey handle multi-threading without compromising data integrity?
A: Valkey employs a single-threaded event loop for data access, preserving order guarantees while utilizing separate threads for IO operations. This approach ensures high performance without introducing inconsistencies or breaking application functionality.
Community
Q: How can developers contribute to Valkey?
A: Developers can contribute to Valkey through its GitHub repository. Contributions can range from improving existing commands to creating new modules. The project also has a robust RFC process for major changes, ensuring community input and transparency.
Q: What is the community’s reaction to Valkey?
A: The community has embraced Valkey enthusiastically. Developers appreciate its open governance, robust feature set, and the quick resolution of issues via collaborative contributions from around the globe.
The future of open-source data bases
We’re excited to follow this project as it develops, and look forward to offering UpCloud users new features in the coming months on UpCloud Managed Valkey!
