in reply to Valkey and Redis support

A couple of years ago our guys were in the process of migrating our code from Memcached to Redis. We decided we would continue to use our custom memcached library, but tweak it a bit so we could implement Redis as a base. This way, none of our scripts or applications would have to change anything. The front end API to them stayed the same, just the innards had changed to use a new backend.

Then this whole Open Source thing happened, and we transitioned to Valkey. We did not have to make any code changes to change the backend from Redis to Valkey. Regardless if the fiasco is fixed, we're sticking with Valkey.

Replies are listed 'Best First'.
Re^2: Valkey and Redis support
by hippo (Archbishop) on Sep 05, 2025 at 08:36 UTC

    Thanks for this info, stevieb. You and pfaut have given me the confidence to proceed with Valkey and in the week or so I've been testing it out it has worked really well. My Perl code is accessing it via CHI::Driver::Redis::SortedSet and it has been very easy to drop into some of our existing CHI-driven code in place of (or as l1_cache addition to) some of our other less efficient back ends.

    Just out of curiousity, what was the reason for your initial Memcached to Redis migration? Aside from the non-volatility of the Redis store there doesn't immediately seem to be a massive difference between them.

    Regardless if the fiasco is fixed, we're sticking with Valkey.

    Sounds very prudent. I suspect we will do the same.

    🦛

[reply]

In Section Seekers of Perl Wisdom