is this project still actively maintained?

[m1cha3lf]

Hi,

i'm wondering if this project is still actively maintained or not. I see some really critical bug reports but no activity from existing maintainers.

As it's nature a database needs a reliable environment and consistency in its development.

I'm a happy user of KeyDB but concerned about the existing issues and uncertainty.

If it was just a wrong impression feel free to delete this issue.

michael

[mbfdias]

there was a recent issue (duplicate of this and closed by @JohnSully ) #788

don't know if it answers your question :)

[m1cha3lf]

Hi,

thanks! I saw this issue as well, but created a new one because since then there was no activity in this project at all. No reaction to critical bug reports etc. I think the situation is a bit different now.

Given the time of almost 2 weeks without a response from a maintainer confirms what was expected i think...

[kanpov]

Yeah, I'm probably just going to use Valkey or even something more "cutting-edge" like Garnet since KeyDB seems to be mostly abandoned.

[ilyavaiser]

This project is dead now and have some really critical bugs, don't use it in production

[m1cha3lf]

does anyone know why it's dead? I mean it's still Snap behind who might have an interest to keep it running!?

[osevan]

Im still using in production systems.

[williamstein]

This project is dead now and have some really critical bugs, don't use it in production

See comments from the lead developer last week to understand their development and maintenance priorities: #798 (comment)

[binaryfire]

I just looked at the activity of the 2 main contributors. It appears one is now contributing to Valkey and the other hasn't been online much since June. So yeah, it seems development has definitely stalled. It's a real shame - the EXPIREMEMBERS command is a gamechanger for tagged caching. But I'd advise against using KeyDB in production going forward.