Percona builds an open source proxy to move single-instance Redis apps onto Valkey Cluster

An application written for a single Redis instance assumes one endpoint. On a distributed Valkey Cluster, the same code may need changes to handle multiple nodes, routing, and differences in how certain commands behave ^[7]. Valkey-proxy is meant to absorb those changes so the application connects to the cluster as written ^[8]. To keep that promise, the proxy has two jobs. Routing means sending each request to the right node. Command behaviour is harder. Where a command acts differently on a cluster, the proxy has to reproduce the single-instance result, or the application sees behaviour it was never written for.

Davis's objection to the existing option lines up with those two jobs. He pointed to Envoy and said it does not fully understand the Valkey protocol and handles connections in a way that means it cannot support everything Valkey can do ^[3]. "Right now there's not really any good open source solution for this, and so there's been this gap," Davis said ^[2].

The New Stack's account does not list which commands the proxy supports, what latency it adds, or when a release is due. Without that list, an operator cannot tell from outside whether a given application's command mix falls inside the no-rewrite promise.

Percona built the first version internally and plans to move it into the Valkey project before opening development to the wider community ^[11]. "From there, we're going to get a lot of contributions from Percona's customers, customers from other places, and independent developers," Davis said ^[12]. I think the order is right. Redis replaced its BSD license with source-available terms in 2024, and the Linux Foundation launched Valkey within days ^[4][5]. Valkey's appeal was a permissively licensed project with independent governance ^[6]. A proxy that sits in every request path but stays one vendor's product would fall outside that governance. That holds even though Percona is one of Valkey's backers, alongside AWS, Google Cloud and Oracle ^[9].

Davis also sees the layer as room for later work. "It provides a decoupling layer that in the future we can build other components into," he said ^[15].