Synthetic benchmarks measure how fast Valkey can run. Production measures how long it remains predictable, and those are different questions.
Under sustained, high-volume write ingestion, as in a production-scale CDC pipeline, raw throughput is rarely the limiting factor. Instead, clusters become unstable when replication falls behind during resharding, memory amplification exhausts available headroom before eviction recovers capacity, or failover triggers large-scale reconnect storms.
These failure modes rarely appear in benchmark reports, but they're often responsible for production outages.
Using a production-scale CDC workload as the reference system, we'll investigate how Valkey behaves under sustained write load, exploring:

* Why is replication an early warning signal of cluster instability?
* How do resharding, replica promotion, and failover interact under write load?
* Why adding replicas doesn't always improve resilience.
* The operational signals and metrics that reveal instability before users do.

You'll leave with practical heuristics for capacity planning, shard sizing, observability, failover testing, and operating Valkey clusters under sustained write pressure.

ValkeyConf 2026, Prague, Czechia