"Valkey was forked from Redis in April last year after the popular in-memory database - often used as a cache - moved to a less permissive license. Shifting Redis to a dual-licensed Redis Source Available License (RSALv2) and Server Side Public License (SSPLv1) prompted the Linux Foundation to fork the code from Redis 7.2.4, backed by AWS, Google, Snap, Ericsson, Oracle, and others."
"In the past, the sharded mode was limited to having a single logical database, which means that you had to have a one-to-one mapping from the application to your Valkey setup, but in 9, what's been done is allow multiple logical databases also in cluster mode, which means from a resource point of view, you can combine many different applications to use the same cluster."
Valkey 9 enables multiple logical databases within clustered deployments so different applications and microservices can share a single Valkey cluster, reducing one-to-one mappings and improving resource utilization. The release adds a unified auto-failover configuration to maintain consistent high availability across development, staging, and production environments. A safe shutdown mode prevents shutdown commands from inadvertently terminating production workloads. Valkey originated as a Linux Foundation fork of Redis 7.2.4 after Redis moved to RSALv2 and SSPLv1 licensing, with backing from AWS, Google, Snap, Ericsson, Oracle, and other organizations.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]