Valkey Blog

Valkey is the open-source fork blessed by antirez and where the community is moving. https://valkey.io Migrating a bunch of old and new dbs from Redis 6.x to Valkey 7 went smoothly here. If you're migrating: 7.2 is the ideal version to switch over. If you upgrade Redis above it, compatibility guarantees drop.

I am confused because: - Valkey [0] is a project of the Linux Foundation - CNCF is part of the Linux Foundation - The CNCF landscape includes Redis [1] but not Valkey Do someone understand their logic? - [0] https://valkey.io/ - [1] https://landscape.cncf.io/?item=app-definition-and-development--databa…

We recently published a blog post about designing an effective AZ Affinity Strategy to improve multi-AZ performance and reduce bill in cloud-based Valkey systems. The post dives into: Why cross-AZ latency matters and its impact on performance and cost. Whether you're optimizing for high availability, minimizing latency, or cutting costs, this strategy offers insights that can apply to many cloud architectures—not just Valkey. Check it out here: https://valkey.io/blog/az-affinity-strategy/ We’d love to hear your feedback and stories about handling affinity strategies in your own systems!

Yes, nobody says that there's something illegal here. Were it so, Redis is high enough profile project for someone to take a legal action. But this is a takeover that is slowly draining the value from the community and directing it to private pockets. E.g. Redis is now source-available. There are still compatible alternatives: https://valkey.io/ (C, a direct Redis fork) or https://keydb.dev/ (C++, an evolved Redis fork), both BSD-licensed. I wish RethinkDB was more alive :-\

Reminder that redis has been forked into valkey - https://valkey.io/

Had a really fun time reading the 8.0rc1 notes a couple weeks back, and diving into the PRs. The PRs on these performance improvements were excellent: very nicely written up PRs, and a logical sequence of work. Of course now there's a great higher level blog post to the topic too. https://github.com/valkey-io/valkey/pull/861 https://valkey.io/blog/unlock-one-million-rps-part2/ There's also a very early RDMA transport, which sounds extremely fun for those so blessed as to be able to try it! https://github.com/valkey-io/valkey/pull/477 I'm impressed with the whole team so much, firing on all cylinders. Great communication in code review, great fast review cycles, smart use of the blog to share updates. Kind of wild seeing smart players from big tech companies collaborating so actively together in public.

This is basically the original source of the claim, https://valkey.io/blog/unlock-one-million-rps/. We are working on a followup that goes more into depth about how to setup the benchmark so that is easier to reproduce.

What about it? Earlier this year: Valkey Turns One: Community fork of Redis https://news.ycombinator.com/item?id=44140379 More recently: https://valkey.io/blog/introducing-valkey-9/

It seems like it went over your head that the package name is valkey, not valkey-server, so the instructions won't work. Why paste a long faulty AI response instead of linking to the concise official documentation? https://valkey.io/topics/installation/

Valkey has lots of corporate sponsors, including Amazon, Oracle, Google, Percona, and Ericsson. It's a also under the Linux Foundation and will get support and coverage from there (which in turn is sponsored by even more large companies) https://valkey.io/participants/

> I'm curious, why hasn't Valkey picked up corporate sponsors to the degree OpenTofu did when HashiCorp changed Terraform's licensing? You seem to be completely out of the loop. Valkey is backed by AWS, Google Cloud, Oracle, etc. If I recall correctly, a principal engineer from AWS was spearheading the project. https://valkey.io/participants/

There’s an interesting optimization along those lines in Valkey https://valkey.io/blog/unlock-one-million-rps-part2/

Some past “what is this” context: https://lwn.net/Articles/966631/ But what I’m most excited about is the change to replication https://valkey.io/blog/valkey-8-0-0-rc1/#replication

I see your point about commit ratio, and that I admit is a correct view of the tangible contributions, but I also dont think those are what got Sentry its traction. I will then ask, do you think Sentry would have been able to get enough of a mass of users to justify getting the VC funding it did if it weren't a MITish licensed product in its early years? How do you value the various libraries of user interaction, issue submission, and other market intangibles? For a product developer, that is an external cost/value to you (the theoretical 'you', in this case), insomuch as there's no contractual obligations there and its not exactly clearly recorded in valuations and balance sheets, I believe. That openness and availability over time builds up a body of goodwill that I believe is critical to the success of a longterm opensource product. As for Redis, enough people cared about the license change that valkey (https://valkey.io/blog/hello-world/) got stood up essentially immediately, which also got significant amount of developer traction. I notice that you dont mention them at all in your writing about Redis. Why is that?