search

nextcloud / helm

A community maintained helm chart for deploying Nextcloud on Kubernetes.
GNU Affero General Public License v3.0
332 stars 269 forks source link

Feature: Add Valkey as an optional subchart to be an alternative to redis #600

Open jessebot opened 3 months ago

jessebot commented 3 months ago

Description of the change

Add Valkey as an optional subchart.

Benefits

It's a FOSS alternative to redis, as redis recently switched to a business source license, which could also mean that down the line, they close source more of the product. Valkey also doesn't use "slave" terminology, which has always made me uncomfortable using redis. Instead of slave, they just use "replica", but slave is still available for backwards compatibility for users switching from redis.

Possible drawbacks

It's another caching store to support, however, if parts of redis become paid, or they introduce parts of the license for redis that say you cannot get paid for support of it (like Hashicorp did with Terrform and Vault), it puts the Nextcloud company at risk for supporting it with paid support contracts as well.

Additional information

Valkey is according to their website:

an open source (BSD) high-performance key/value datastore that supports a variety of workloads such as caching, message queues, and can act as a primary database. Valkey can run as either a standalone daemon or in a cluster, with options for replication and high availability.

Valkey is available from bitnami both as stand alone valkey and Valkey cluster. I would say it would be good to support valkey cluster to allow users to scale better, but I'm open to discussion as always :)

provokateurin commented 3 months ago

I think the worst that would happen with redis that we can not update to any newer version if it gets paid-only or something like that, but I agree having this would be very nice.