Is KeyDB abandoned by Snap Inc? Who maintains it now?

[DavidRadan]

Dear KeyDB Team ,

I’ve noticed that KeyDB hasn’t received any major updates or maintenance since around 2023.
It seems like development has slowed down significantly , no new commits, releases, or community engagement really .

Is KeyDB still under active development or officially maintained by Snap?

If not, has Snap open-sourced or transferred maintenance to another team or community group?

I also saw in GitHub Issue #895
that @JohnSully , a main contributor, has left Snapchat. This makes me wonder about the long-term support and development of KeyDB.

I'm asking this to understand whether it’s worth considering KeyDB for a future project, particularly because of its multi-master and active-replica features, which are quite valuable compared to Redis.

Regards,
David

[mator]

as for "active-active" / multi-master feature, consider joining
valkey-io/valkey#512
maybe its going to be implemented soon.

PS: or if you don't mind, could probably try with Hazelcast (java) , it has AP (Availability + Partition Tolerance) cluster in its community edition.

[mbfdias]

@mator

actually if you want to test it, the code has already been through a round of testing and it's working quite well. Some more testers would be great

you can download from: https://github.com/bet0x/valkey, please do read https://github.com/bet0x/valkey/blob/unstable/valkey-multimaster-setup.md for instructions on setup

[Justinzobel]

Yeah looks like KeyDB is completely dead.

[alexted]

RIP KeyDB