News for hackers. Stuff that matters.
Re:Redis 8.8: New array data structure, rate limiter, perfor... by tapoxi on Friday June 05, 2026 @08:21AM (#48411431)
Where did everyone end up on the Redis/Valkey split? Is there still a reason to use Redis after the license kerfuffle?
Re:Redis 8.8: New array data structure, rate limiter, perfor... by FunnyLookinHat on Friday June 05, 2026 @08:24AM (#48411464)
For those who may not know, you can cut your costs in AWS by going with Valkey over Redis for about 33% savings.

https://aws.amazon.com/blogs/database/reduce-your-amazon-ela...

Re:Redis 8.8: New array data structure, rate limiter, perfor... by glouwbug on Friday June 05, 2026 @08:46AM (#48411664)
But what about Geico?
Re:Redis 8.8: New array data structure, rate limiter, perfor... by jihadjihad on Friday June 05, 2026 @11:25AM (#48413829)
It's so easy a grug brain can do it.
Re:Redis 8.8: New array data structure, rate limiter, perfor... by Salgat on Friday June 05, 2026 @11:23PM (#48421077)
We're planning to go to Valkey for exactly that reason.
Re:Redis 8.8: New array data structure, rate limiter, perfor... by jillesvangurp on Friday June 05, 2026 @10:33AM (#48413110)
We switched to Valkey two years ago. I haven't really looked back. I think both projects have done a lot of nice stuff since the split but it's not really impacting anything I use. The feature set was fine five years ago and I don't think we're using anything in Valkey that wouldn't work in Redis. There are probably a lot of projects that never switched over because they had no real need.

But most of the cloud providers now offer Valkey because of the license changes. Of course, cloud providers not offering Redis was the intention of the license change from the Redis point of view. So mission accomplished for Redis.

But the flip side of course is that if you want to deploy on standard infrastructure rather than self hosting Redis, Valkey is now the easy, low risk path that probably should be the default for most companies that target AWS, Azure, GCP, etc. Same with Elasticsearch vs. Opensearch and a few other products where the community forked because of license changes.

Mentioning Elasticsearch because I know people in both communities and I'm deeply familiar with the stack. A few years on, Opensearch has taken a lot of the momentum from Elasticsearch.

Re:Redis 8.8: New array data structure, rate limiter, perfor... by lukaslalinsky on Friday June 05, 2026 @09:55AM (#48412640)
I've switched to Valkey and I'm not really looking back. I'm much more comfortable with those people maintaining the software.
Re:Redis 8.8: New array data structure, rate limiter, perfor... by CamouflagedKiwi on Friday June 05, 2026 @10:03AM (#48412735)
Valkey, because our cloud provider is hosting it and that's obviously what they prefer.

I feel like we're using about 1% of its features at this point - really just as a fast K/V store - so it would be easy to switch if needed, but I can't see a case where we would.

Re:Redis 8.8: New array data structure, rate limiter, perfor... by gadders on Friday June 05, 2026 @10:12AM (#48412834)
They prefer it because they don't have to pay to use it.
Re:Redis 8.8: New array data structure, rate limiter, perfor... by CamouflagedKiwi on Saturday June 06, 2026 @03:38AM (#48422432)
Sure. I prefer that because they charge me less.
Re:Redis 8.8: New array data structure, rate limiter, perfor... by olavgg on Friday June 05, 2026 @10:16AM (#48412882)
We're a self hosted shop, we went with Valkey. Valkey also has support for RDMA, which we already is running in our infrastructure.
Re:Redis 8.8: New array data structure, rate limiter, perfor... by stevoski on Friday June 05, 2026 @09:51AM (#48412563)
We switched to Valkey after the Redis license kerfuffle happened, discovered we were saving money on our AWS bill, and have no motivation to go back to Redis.

So we’ve stayed with Valkey.

Re:Redis 8.8: New array data structure, rate limiter, perfor... by atraac on Friday June 05, 2026 @08:56AM (#48411794)
We use almost exclusively Valkey now, mostly because we host on AWS and Render, which both use Valkey. It's faster, cheaper and compatible. I'd consider Garnet too but I believe it doesn't support LUA(or didn't at the time we needed it).
Re:Redis 8.8: New array data structure, rate limiter, perfor... by esafak on Friday June 05, 2026 @06:36PM (#48419245)
https://microsoft.github.io/garnet/docs/welcome/compatibilit...

> Garnet now has full-fledged and efficient support for Lua scripting. You can enable Lua with the --lua switch.

Re:Redis 8.8: New array data structure, rate limiter, perfor... by NorwegianDude on Friday June 05, 2026 @10:38AM (#48413165)
Most people seems to have switched to Valkey, and it's backed by the Linux foundation.
Re:Redis 8.8: New array data structure, rate limiter, perfor... by kfir on Friday June 05, 2026 @09:08AM (#48411981)
Went with 100% ValKey, if you are solely on AWS it is a no-brainer
Re:Redis 8.8: New array data structure, rate limiter, perfor... by hakube on Friday June 05, 2026 @08:55AM (#48411773)
We went with DragonFlyDB
Re:Redis 8.8: New array data structure, rate limiter, perfor... by esafak on Friday June 05, 2026 @06:37PM (#48419248)
Are you happy with it? Is it faster as claimed?
Re:Redis 8.8: New array data structure, rate limiter, perfor... by benatkin on Friday June 05, 2026 @04:08PM (#48417508)
Valkey continues to be the real redis, released under a permissive open source license like redis originally was. The fork of redis known as redis because those that decided to fork it had the trademark at first wasn't under an OSI-certified open source license and now is under a non-permissive OSI-certified open source license.

I'm taking liberties with the concept of forking.