SYSTEM Cited by 1 source
ValKey¶
ValKey is the BSD-licensed, Linux-Foundation-governed fork of Redis that emerged in March 2024 after Redis Ltd. changed its licensing from BSD to the dual SSPL / RSAL v2 scheme. AWS, Google Cloud, Oracle, and Ericsson were among the original co-sponsors; ValKey remained API-compatible with Redis 7.2 at inception and continues to track the same data-model + RESP protocol surface, with divergent roadmaps after the fork point.
For the purposes of this wiki, ValKey appears wherever Redis would — as an in-memory key-value + data-structure store used as a cache, rate-limiter, queue substrate, or fast serving tier for precomputed artifacts — with the additional signal that the consumer chose ValKey over Redis specifically, typically because managed-service availability (AWS ElastiCache for Valkey since 2024) or licensing predictability was load-bearing.
Seen in¶
- sources/2026-01-06-lyft-feature-store-architecture-optimization-and-evolution
— Lyft uses ValKey as the
write-through LRU cache
sitting on top of DynamoDB inside
dsfeatures, the online serving layer of the Lyft Feature Store. Purpose: "ultra-low-latency retrievals by storing the most frequently-accessed (meta)data with a generous TTL." Named specifically as ValKey (not Redis), consistent with the post-2024 AWS-managed-service shift.
Related¶
- systems/redis — the upstream Redis project; ValKey is a fork.
- systems/dynamodb — Lyft pairs ValKey as a write-through cache on top of DynamoDB.
- concepts/write-through-cache
- concepts/cache-ttl-staleness-dilemma