3 ms·

Where did everyone end up on the Redis/Valkey split? Is there still a reason to use Redis after the license kerfuffle?

by tapoxi 4mo ago

FunnyLookinHat 4mo ago
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-elasticache-costs-by-up-to-60-with-valkey-and-cudos/ https://aws.amazon.com/blogs/database/reduce-your-amazon-ela...
- glouwbug 4mo ago
  But what about Geico?
  - jihadjihad 4mo ago
    It's so easy a grug brain can do it.
- Salgat 4mo ago
  We're planning to go to Valkey for exactly that reason.
hakube 4mo ago
We went with DragonFlyDB
- esafak 4mo ago
  Are you happy with it? Is it faster as claimed?
atraac 4mo ago
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).
- esafak 4mo ago
  https://microsoft.github.io/garnet/docs/welcome/compatibility 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.
kfir 4mo ago
Went with 100% ValKey, if you are solely on AWS it is a no-brainer
stevoski 4mo ago
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.
lukaslalinsky 4mo ago
I've switched to Valkey and I'm not really looking back. I'm much more comfortable with those people maintaining the software.
- deleted 4mo ago
  [deleted]
CamouflagedKiwi 4mo ago
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.
- gadders 4mo ago
  They prefer it because they don't have to pay to use it.
  - CamouflagedKiwi 4mo ago
    Sure. I prefer that because they charge me less.
olavgg 4mo ago
We're a self hosted shop, we went with Valkey. Valkey also has support for RDMA, which we already is running in our infrastructure.
jillesvangurp 4mo ago
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.
NorwegianDude 4mo ago
Most people seems to have switched to Valkey, and it's backed by the Linux foundation.
benatkin 4mo ago
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.

Where did everyone end up on the Redis/Valkey split? Is there still a reason to use Redis after the license kerfuffle?

by tapoxi 4mo ago

Where did everyone end up on the Redis/Valkey split? Is there still a reason to use Redis after the license kerfuffle?

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-elasticache-costs-by-up-to-60-with-valkey-and-cudos/ https://aws.amazon.com/blogs/database/reduce-your-amazon-ela...

glouwbug 4mo ago
But what about Geico?
- jihadjihad 4mo ago
  It's so easy a grug brain can do it.
Salgat 4mo ago
We're planning to go to Valkey for exactly that reason.

hakube 4mo ago

We went with DragonFlyDB

esafak 4mo ago
Are you happy with it? Is it faster as claimed?

atraac 4mo ago

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

esafak 4mo ago
https://microsoft.github.io/garnet/docs/welcome/compatibility 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.

kfir 4mo ago

Went with 100% ValKey, if you are solely on AWS it is a no-brainer

stevoski 4mo ago

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.

lukaslalinsky 4mo ago

I've switched to Valkey and I'm not really looking back. I'm much more comfortable with those people maintaining the software.

deleted 4mo ago
[deleted]

CamouflagedKiwi 4mo ago

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.

gadders 4mo ago
They prefer it because they don't have to pay to use it.
- CamouflagedKiwi 4mo ago
  Sure. I prefer that because they charge me less.

olavgg 4mo ago

We're a self hosted shop, we went with Valkey. Valkey also has support for RDMA, which we already is running in our infrastructure.

jillesvangurp 4mo ago

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.

NorwegianDude 4mo ago

Most people seems to have switched to Valkey, and it's backed by the Linux foundation.

benatkin 4mo ago

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.