Valkey 8.0.0 Is Out
(github.com)118 points by schaum 2 days ago
118 points by schaum 2 days ago
Minio used to have a filesystem backend that would store each file as a file on the local filesystem. They removed this, so lots of people still use the last version before that.
> 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.
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...
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?
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-...
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.
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?
Heroku cant use OSS Redis anymore because of the license change to prevent Cloud vendors from running OSS Redis and charging for it
My point was that Redis' bet on cloud vendors paying them seems to be failing.
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?
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.