TechEcho

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.

And that's why the OS movement matters so much.<p>Otherwise, Redis users would pretty soon be as miserable as Oracle users.

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...

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.

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?

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.<p>Yet another project to add to the books of successful forks re: rug-pull?<p>[0]: <a href="https://devcenter.heroku.com/articles/heroku-redis" rel="nofollow">https://devcenter.heroku.com/articles/heroku-redis</a>

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.

And that's why the OS movement matters so much.<p>Otherwise, Redis users would pretty soon be as miserable as Oracle users.

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...

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.

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?

Valkey 8.0.0 Is Out

6 comments

Valkey 8.0.0 Is Out

6 comments