Valkey is used for more than caching: the project describes it as a platform for message queues and primary-database workloads, alongside newer capabilities such as JSON data handling, Bloom filters and vector search. The title’s discussion refers to a “Future of Valkey” fireside chat at Valkey Developer Day in Vienna on 19 September 2024. The official agenda confirms the event and speakers, but does not provide a transcript or detailed conclusions from that conversation.
What happened at Valkey Developer Day?
Valkey Developer Day took place in Vienna on 19 September 2024. The Linux Foundation event page described it as a place to learn about Valkey’s future and migration experiences. Its agenda listed Madelyn Olson, then identified with AWS as a Valkey maintainer and principal engineer, for “What’s New in Valkey 8 Tech Talk”; Viktor Söderqvist, listed with Ericsson, for “Valkey in Telecom: How Ericsson is Using Valkey in Mobile Networks”; and a “Fireside Chat: The Future of Valkey” at 14:25.
As an Amazon Associate I earn from qualifying purchases.
See the official event agenda and event information. The agenda establishes who was scheduled and what sessions were called, not what the fireside-chat participants said. Olson and Söderqvist should not be credited with particular predictions or claims from that discussion without a recording or transcript.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →How Valkey’s role extends beyond a cache
The project’s stated uses have broadened from familiar cache and session-storage roles to include message brokering and real-time analysis. The project now describes Valkey as suitable for message queues and primary-database workloads as well. That is a statement of possible use, not a blanket recommendation: whether an in-memory store can serve as a system of record depends on the application’s data model, durability and recovery requirements, data volume, and operational design.
#1 Best Overall
The Linux Foundation’s 2024 launch announcement described Valkey as a high-performance datastore for caching, lower-latency and higher-throughput storage alongside backend databases, real-time analysis, session storage, and message brokering. A 2025 Valkey project article describes caching, queues, and primary-database use. Read together, these sources show the breadth of the project’s intended applications, not that all workloads have the same requirements or results.
The Linux Foundation’s Valkey community launch announcement and the project’s 2025 overview of Valkey’s development provide those descriptions.
What newer data and search features add
JSON and Bloom filters
In its 2025 overview, the Valkey project discusses JSON support for working with structured data natively and Bloom filters for compact checks of whether an item may exist in a set. These features can make a datastore more useful for applications that need structured values or space-efficient membership checks. The article does not establish that every deployment includes every feature, or that a specialized database or search system is no longer appropriate.
Vector similarity search
The same project article describes Valkey Search for vector similarity search, including approximate and exact search approaches. This extends the kinds of queries the project discusses beyond simple key retrieval. Feature availability and deployment requirements can vary; consult current Valkey documentation before choosing a version or planning a production rollout.
What the Valkey 8 releases say about reliability and performance
The Linux Foundation’s September 2024 Valkey 8.0 announcement highlighted observability and manual-failover improvements. It also quoted Söderqvist on cluster improvements for cases where failover occurs during an ongoing slot migration, with the aim of making cluster scaling safer and more reliable. These are release-announcement statements about Valkey 8.0, not remarks established from the Developer Day fireside chat.
In its 2025 Valkey 8.1 announcement, the Linux Foundation reported three release-specific figures:
Rank #4
- Up to 20% lower memory footprint for common key/value workloads.
- Up to 20% better performance for encryption-in-transit workloads using I/O threading.
- Up to 90% lower P100 request latency when active memory defragmentation is used.
These are figures reported by the Linux Foundation for Valkey 8.1, each tied to a different feature or workload condition. They are not independently established guarantees for every application, nor should they be treated as current benchmarks for later versions. Read the Valkey 8.0 announcement and Valkey 8.1 announcement for the release context.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteWhat this means when evaluating Valkey
Valkey’s wider feature set makes it relevant to more than cache replacement, but a product description cannot decide whether it fits a particular application. Evaluate it against the needs of the workload rather than assuming that a queue, primary database, or vector search use will behave like caching.
- Data model and workload: Check whether the application’s access patterns fit Valkey’s available data structures and capabilities.
- Durability and recovery: Define what data loss is acceptable and how persistence, backup, restoration, and recovery must work before treating an in-memory store as a primary database.
- Scale and failure behavior: Consider data size, cluster operations, failover, and the effect of maintenance or node loss.
- Operations and observability: Confirm that the deployed version and surrounding tools provide the monitoring and operational controls the team requires.
- Feature and service availability: Verify which modules or search capabilities are available in the chosen deployment and whether a managed service supports them.
- Migration effort: Map existing data types, commands, client libraries, persistence expectations, and operational procedures before moving a workload.
The Developer Day event explicitly raised migration experiences as a topic for attendees. Its agenda alone, however, does not document a migration recipe or endorse a particular hosting provider.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
