Valkey 8.0.0 Is Out

https://github.com/valkey-io/valkey/releases/tag/8.0.0

by schaum • 2 years ago

125 31 2 years ago

schaum• 2 years ago

to my knowledge and understanding it is the first valkey release that include features not just bug fixes! This release is fully compatible with Redis OSS 7.2.4.

ezekg3• 2 years ago

Congrats on the v8 release. It's super interesting to see that Heroku now uses Valkey instead of Redis [0], with no notes re: compatibility yet.

Yet another project to add to the books of successful forks re: rug-pull?

[0] https://devcenter.heroku.com/articles/heroku-redis

federationfive• 2 years ago

Heroku cant use OSS Redis anymore because of the license change to prevent Cloud vendors from running OSS Redis and charging for it

ezekg3• 2 years ago

My point was that Redis' bet on cloud vendors paying them seems to be failing.

rmbyrro• 2 years ago

And that's why the OS movement matters so much.

Otherwise, Redis users would pretty soon be as miserable as Oracle users.

wmf3• 2 years ago

Nah, Redis users would just keep using the last free version. Probably many of them will do that anyway because they missed the memo about Valkey. Like the poor people still using OpenOffice.

remram3• 2 years ago

I have a few containers on the last OSS Elasticsearch version, and everybody uses the last filesystem-transparent Minio version. I am not sure why you are being downvoted, this is not a good plan but definitely happens in practice.

vander_elst• 2 years ago

Has anyone used valkey in production? How does it compare to redis? Can it be used as a 1:1 replacement to redis or are there any caveats?

jjice• 2 years ago

Haven't tried it in prod myself, but they claim full compatibility:

This release is fully compatible with Redis OSS 7.2.4.

bloppe2• 2 years ago

They only forked 5 months ago. Assuming you haven't adopted any brand new non-backward-compatible features in the last 5 months, then it should be a perfect drop-in replacement.

forbiddenlake• 2 years ago

If you upgraded to 7.4, then redis switched to a proprietary dump format, and if you want to use those dumps you'll have to use a third-party tool to dump the data and put it back in valkey.

https://github.com/valkey-io/valkey/issues/845#issuecomment-...

ronsor• 2 years ago

Redis switched to a proprietary dump format just to lock in users?

reconditerose2• 2 years ago

I'm from the project.

There shouldn't be any caveats of replacing Redis 7.2 and early to Valkey 8.0. I've talked with a few folks who have migrated and none so far have hit any issues, one even migrated from Redis 2.6.

rowanseymour• 2 years ago

Hope to see this as an option in Elasticache soon. Feels like Valkey has the momentum over Redis now. Less sure about OpenSearch vs Elasticsearch...

remram3• 2 years ago

What about client libraries? I feel a bit weird using valkey with redis client, but I also feel weird switching client libraries if they are not affected by any license change.

Valkey 8.0.0 Is Out

Related Stories