Modules

[bitnom]

What's the plan regarding the existing modules? Do they come along for the ride?

[madolson]

The existing modules available in Redis stack were always source available (Json, Search, Bloom, timeseries, etc). If there is some specific feature you are interested in, please open issue and we'll look into implementing it in a way that everyone can use it.

[natoscott]

We are using the Search and JSON modules for some peripheral functionality on a project here, small number of keys and small values - both have been perfectly fine for this use-case. Search vendors Bloom, so we indirectly use that too.

[PingXie]

I think it would make sense to start curating a module repo under the valkey-io project.

[zuiderkwast]

To start with, let's at least link to these on our README and/or docs!

[madolson]

I would love to see us have links for recommended modules as well as something similar to redis stack with our curated list of modules. (Maybe overlapping with ping's suggestion)

Open source only? I.e. No rsal modules.

[natoscott]

Once the current API changes settle down and a release is available, I'd be happy to start moving these open source modules over to Valkey-specific module APIs and shift the git repos over here under the valkey.io umbrella - if there's consensus this is the way to go?

[zuiderkwast]

We'll keep a compatible module API so you can run proprietary modules if you want. That said, I'd like to see the open ones if people are willing to contribute.

[natoscott]

I've migrated the first couple of modules (forked from before license change) over to Valkey APIs here:

https://github.com/natoscott/valkey-bloom
https://github.com/natoscott/valkey-json

These (as well as Search, and others) use two small helpers - test and SDK modules, which are here:

https://github.com/natoscott/valkey-module-test
https://github.com/natoscott/valkey-module-sdk

If this is the way you'd like to go, let me know and I can do the other modules as well.