Closed glitsj16 closed 8 months ago
Unbound uses the libhiredis library for the cachedb module. That is a C client interface. It seems to be in the valkey repo at valkey/deps/hiredis.
I would think that it would work straight away. Since it is a copy of the externally developed hiredis library and that is what unbound uses, I guess that would work without needing changes in Unbound. Unbound has support to be able to support different backends for the cachedb module. It can be configured with the backend: "redis"
option in the cachedb:
section of the config.
Realizing it's early days, but now that the Linux Foundation officially launched valkey, my first thought was to replace unbound's redis backend with it.
Any plans/roadmap on the horizon?