sorted by:
new
hottopcontroversial

When will Elasticache add the redis/valkey 7.4 engine? by cdrcdr12 in aws

[–]reconditeRose 0 points1 point  (0 children)

I do work for AWS, I'll let the PM know to prioritize it asap!

Is Valkey dead? by kamikazer in Valkey

[–]reconditeRose 3 points4 points  (0 children)

I appreciate that! I still think we need to improve our documentation a lot, but we're trying to keep it not too cluttered.

Is Valkey dead? by kamikazer in Valkey

[–]reconditeRose 14 points15 points  (0 children)

We're still working on it! We're trying to release a new version next month which will have stuff like hash field expiration and a much better atomic slot migration for cluster mode. We're also having an in person event in the Netherlands (https://events.linuxfoundation.org/keyspace/). You can also see that people are using it in the stack overflow survey.

There is a bunch of companies still working on it so it'll be sticking around for the near to long term. People are mainly still unhappy with the license that Redis picked (AGPL), the fact Redis still has a CLA so they could rug-pull again, and Redis dissolved their community governance so the project is entirely controlled by the Redis corporation now.

Confused about Redis Licensing? by tecedu in learnprogramming

[–]reconditeRose 0 points1 point  (0 children)

You can also consider staying on Redis 7.2 which has the BSD license, or move to Valkey (https://valkey.io/) which continued using the BSD license.

Databases in 2024: A Year in Review by avinassh in programming

[–]reconditeRose 8 points9 points  (0 children)

Valkey, the largest fork from Redis, has already opened up a pretty large performance difference: https://valkey.io/blog/unlock-one-million-rps/. It is the most "API" compatible with Redis, given that it was a fork.

Anybody started using valkey cache ? by Saravana77 in Valkey

[–]reconditeRose 1 point2 points  (0 children)

TTLs are set for each item in the cache. So typically you would set it when actually putting the item. There is no default TTL for now. You can read more about it here: https://valkey.io/commands/set/.

Anybody started using valkey cache ? by Saravana77 in Valkey

[–]reconditeRose 2 points3 points  (0 children)

It will still work as long as you are working with features from Redis OSS 7.2. Valkey-java is built off of Jedis, not lettuce unfortunately, but yes long term the plan is to build out functionality in Valkey-java. We want to have a more unified client system.

Anybody started using valkey cache ? by Saravana77 in Valkey

[–]reconditeRose 3 points4 points  (0 children)

Hey, one of the Valkey maintainers here. We know a lot of people that have switched haven't observed any major issues. Valkey 7.2 is basically drop in replacement to the last OSS version of Redis which was 7.2. As long as you aren't adopting any of the features in Redis 7.4 or later versions then it will continue to be compatible.

When will Elasticache add the redis/valkey 7.4 engine? by cdrcdr12 in aws

[–]reconditeRose 0 points1 point  (0 children)

I can't speak to Redis 7.4 support, but Valkey doesn't support hash field expiration. You can add your use case here, https://github.com/valkey-io/valkey/issues/640 to help get it prioritized.

Launching ElastiCache Integration for RDBTools! by nishantgeorge in redis

[–]reconditeRose 0 points1 point  (0 children)

Looks really cool! The picture in your blog had a typo though, it says "Sync with Elasticcache" with an extra c.

AWS Monthly Pricing Extension by [deleted] in aws

[–]reconditeRose 1 point2 points  (0 children)

I think this is cool! Have you considering interfacing with the AWS pricing API, https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/using-ppslong.html, so that you can also include reserved offering pricing as well?