feat: Add support for Valkey vector store

[daric93]

Valkey Vector Store Integration Request

Adding Valkey as a possible data store would be quite beneficial for the library, as it’s a community-driven, Redis-protocol-compatible project that’s seeing growing adoption as a vendor-neutral alternative. Supporting Valkey would expand Rig’s compatibility with existing Redis-based infrastructure and managed services, increasing the number of potential use cases for caching, metadata storage, and lightweight retrieval workflows.

I’m happy to implement this if it makes sense for the project — the scope looks fairly clear (adding a new crate, implementing the relevant datastore traits, and wiring it into the release list). I wanted to reach out first to check whether Valkey support would be welcome before starting work.

Resources

Valkey
Valkey-Glide

[linear]

RIG-1132

[joshua-mo-143]

Hi @daric93, thanks for opening an issue!

I think it would be very beneficial to see examples of companies that are actually using Valkey in production for this specific use case. I'm happy to accept this but it's difficult to justify adding if nobody's actually going to use it

[daric93]

That makes sense. Since Valkey adoption is still early, I’m happy to switch the proposal to Redis instead. Redis is widely used in production for embeddings, metadata, and lightweight vector similarity, which should make the justification much clearer. Given Valkey’s Redis protocol compatibility, this would also keep the door open for Valkey support later with minimal additional work or full compatibility.

[daric93]

Hi @joshua-mo-143
Went ahead and implemented this as a Redis vector store in PR #1509 . Used Redis instead of Valkey given the more established production adoption. Happy to adjust based on your feedback!