Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redis license change #1262

Open
fabcor-maxiv opened this issue Jun 26, 2024 · 3 comments
Open

Redis license change #1262

fabcor-maxiv opened this issue Jun 26, 2024 · 3 comments

Comments

@fabcor-maxiv
Copy link
Contributor

The topic of Redis license change came up at MAX IV.

https://devops.com/valkey-is-rapidly-overtaking-redis/

I am not sure if it is a worry for MXCuBE. I do not know if there is a policy regarding the licenses of the dependencies used in MXCuBE. Is it something to be discussed? How dependent on Redis are we really? Should we try Valkey, supposedly THE drop-in replacement, committed to staying FLOSS forever?

@elmjag
Copy link
Contributor

elmjag commented Jun 26, 2024

How is Redis used by MXCuBE-Web? Perhaps we can refactor MXCuBE so that can drop Redis dependency?

It would be nice from deployment and maintenance point of view as well.

@marcus-oscarsson
Copy link
Member

We are not using redis from mxcubeweb directly any longer but mxcubecore is using it for some functionality like the DataPublisher. We could drop the dependency on redis for mxcubeweb but it would be more difficult for mxcubecore

@marcus-oscarsson
Copy link
Member

I think that we in this case do need to consider to switch to Valkey

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants