Client-side distributed lock?

[thearchitector]

It would be great if GLIDE had a distributed lock that could be used in the various language bindings. I know with Redis, the goto implementation was Redlock. If that algorithm still holds up in terms of correctness/reliability, there is at least one rust reference that could be helpful.

Regardless of implementation, something that is built-in to GLIDE that would guarantee, for some period of time and in a distributed environment, exclusive control over one or set of keys.

[jamesx-improving]

Hi @thearchitector , thank you for reaching out!

I guess you're referring to this: https://valkey.io/topics/distlock/

I might not be the best person to answer this. Will ask the team and see if we have had support or roadmap on this.

[jamesx-improving]

Update: We currently do not support it, nor do we have any confirmed plan/roadmap for it. The only thing relevant is our team member @avifenesh came up with this example project on top of GLIDE: https://github.com/avifenesh/glide-distributed-lock

@thearchitector any chance you could help on this?

[thearchitector]

I've thought about this some more since initially proposing this be a GLIDE feature, and this confirms my decision -- I've never done anything in Rust but have been wanting to for a while, so think this will be a nice isolated learning experiment.

I'll give it a go and see where I land.

[asafpor]

Cool, let us know how it goes