Showing Post From Valkey
Redis, Valkey, and Dragonfly clients: revisit your connection settings before the next failover
An order service runs on Valkey with Sentinel. At 2 AM the team runs a planned failover before patching the primary.
Read moreRedis, Valkey, and Dragonfly memory and upgrades: revisit before the next spike
A payments team runs its session cache with maxmemory 12gb on a 16 GB node and feels safe. On a festival sale evening a replica reconnects, a reporting job pulls a few huge hashes, and the kernel kills the process while used_memory still shows less than 12 GB.
Read moreRedis, Valkey, and Dragonfly operations: persistence and failover
A cache becomes a database the day nobody can rebuild it. After that day, persistence and failover are not settings copied from a blog.
Read moreRedis, Valkey, and Dragonfly benchmarks: read the method first
A benchmark number without its method sounds complete, but it does not tell you what happened. The first note in this series, Redis, Valkey, or Dragonfly: revisit the choice before you treat them as the same cache, covered licences, history, data file compatibility, and cluster mode.
Read moreRedis, Valkey, or Dragonfly: revisit the choice before you treat them as the same cache
If your service already uses Redis, the name on the port has not changed. The product behind that name has. Treating Redis, Valkey, and Dragonfly as three labels for one cache is the habit worth unlearning.
Read more