schaum 2 days 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.

rmbyrro 2 days ago

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

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

  • wmf 2 days 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.

    • remram a day 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.

      • petejodo 19 hours ago

        I only recently discovered minio and started using it for a project. What are you referring to by “last file system-transparent Minio version” for my own awareness?

      • KronisLV a day ago

        > I am not sure why you are being downvoted, this is not a good plan but definitely happens in practice.

        I guess this is more okay when the dated versions are not exposed publicly but are backing services, but in general it might be a question of time until some CVE puts you at risk or there's a bug that will never be fixed.

        I like the idea of having "feature complete" software that you can use from now until the end of time (or at least the end of whatever product you're working on), I just don't think this is always feasible with the way we develop software.

rowanseymour 2 days 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...

remram a day 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.

vander_elst 2 days 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?

  • bloppe 2 days 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.

  • jjice 2 days ago

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

    > This release is fully compatible with Redis OSS 7.2.4.

  • reconditerose 2 days 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.

ezekg 2 days 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 days ago

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

    • ezekg 2 days ago

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

      • rsstack 2 days ago

        It is unfortunately not failing them ("unfortunately" because I very much dislike the path they took). They lost Heroku, which also didn't pay them before the license change, but they got others. I don't know if the information is public.

      • kelsey98765431 2 days ago

        When will these money hungry vultures realize that you cannot transition a foss "brand" into a proprietary system no matter how you pitch the tree tier? You can't have your name recognition and eat it too. These groups don't realize that "NewThing from the developers of Redis" holds so much more weight than "Redis is now closed source and you have to pay for it"? There is a net negative value in detonating the bomb that is a license change versus making something new and throwing the existing name's support behind it. Just look at literally every well known license changed software becoming irrelevant while the foss fork with a new name has no problem getting traction? Just look at the graveyard of Solaris, OpenOffice and others. The open source community deeply despises these relicensing scams and has proven time and time again not to fall for ignorant consumer brand identity marketing tactics?