I may be biased, but I think this announcement is actually a very good sign for Redis, since it shows that the focus is back to the community edition, that is, the source tree you can just download from GitHub (and I believe this is an effect of the license change: it is possible for the company to work on the public tree without competitors to cut&amp;paste the code in SAAS services).There are few things that are interesting for me about this discussion related to complexity and use cases outside the scope.1. You can still download Redis and type &quot;make&quot; and it builds without dependencies whatsoever like in the past, and that&#x27;s it.2. Then you run it and use just the subset of Redis that you like. The additional features are not imposed to the user, nor they impact the rest of the user experience. This is, actually, a lot like how it used to be when I handled the project: I added Pub&#x2F;Sub, Lua scripting, geo indexing, streams, all stuff that, at first, people felt like they were out of scope, and yet many shown to be among the best features. Now it is perfectly clear that Pub&#x2F;Sub belonged to Redis very well, for instance.3. This release has improvements to the foundations, in terms of latency, for example. This means that even if you just use your small subset, you can benefit from the continued developments. Sometimes systems take the bad path of becoming less efficient over time.So I understand the sentiment but I still see Redis remaining quite lean, at least for the version 8 that I just downloaded and I am inspecting right now.

If your application can&#x27;t survive the Redis server being wiped without issues, you&#x27;re using Redis wrong.

Yup, agree. Or as I like to call Redis, your &quot;db building kit&quot;Of course if what you need is a traditional DB then go with a traditional DBBut it offers those data structures and other stuff that fewer competitors have (or has it in a more quirky way)

&gt; that has always been much faster than RedisDo you have some reliable recent benchmarks comparing the two?

Rarely seen Redis viewed as a database, even if that has been their push for the last few years.

Generic data structures in memory, grab bag of structures and algorithms... sounds more like a programming language or library than an external tool. C++ STL for example would fit these descriptions perfectly.Doing everything is a recipe for bloat. In a database, in a distributed cache, in a programming language, in anything.

What do you think doesn&#x27;t belong in Redis? I&#x27;ve always viewed Redis as basically &quot;generic datastructures in a database&quot; — as opposed to say, Memcached, which is a very simple in-memory-only key&#x2F;value store (that has always been much faster than Redis). It&#x27;s hard for me to point to specific features and say: that doesn&#x27;t belong in Redis! Because Redis has generally felt (to me) like a grab bag of data structures + algorithms, that are meant to be fairly low-latency but not maximally so, where your dataset has to fit in RAM (but is regularly flushed to disk so you avoid cold start issues).

You&#x27;d be surprised how many engineers make these kinda decisions.

That does not match my experience. Engineers learn a new tool, that tool is successful in solving a problem. Whether it is recency bias, incorrect pattern matching, or simply laziness, the tool is used again but with reduced success. Repeat that process a few more times (sometimes in different organizations) and now the tool is way outside the domain, ill-fit to the task at hand, and a huge pain.That often happens with engineers who pushed that tool getting promoted a few times and building their career on said tool, which is where I have seen this being pushed down, but I think it is important that in most cases are still engineers

I worked somewhere where a team, that can only be described as a clown team, decided to use Elastic as the “database” for the entire login&#x2F;auth microservice, that other teams depended on.It was so slow and terrible.

This is what I see everywhere. Something is a success and then everybody starts using it wrong. Like Elastic search as database, people use it for searching and then start using it as primary database. Mostly pushed by management BTW not always the software engineer.

Totally agree. It&#x27;s definitely not the right tool for what they&#x27;re doing, but some of the engineers don&#x27;t seem to know better, or understand, the point of being able to run scripts on Redis.Lots of Lua scripting and calculations being done on Redis that has nothing to do with the data that&#x27;s local to Redis. It&#x27;s infuriating.

&gt; The company I’m working for now keeps trying to add more and more functionality using Redis, that doesn’t belong in Redis, and then complains about Redis scaling issues.This doesn&#x27;t sound like a Redis issue, you&#x27;re just not using the right tool for the job.

This sort of makes me sad. Redis has strayed from what its original goal&#x2F;purpose was.I’ve been using it since it was in beta. Simple, clear, fast.The company I’m working for now keeps trying to add more and more functionality using Redis, that doesn’t belong in Redis, and then complains about Redis scaling issues.

Likely when it&#x27;s small enough to keep in RAM and you want to do some sort of on-the fly aggregation&#x2F;correlation.

When do you want to store your time series data in Redis and not a database like TimescaleDB or Clickhouse which is optimized for storage on disk and analytics queries?

It was always, and still is, a license issue. Redis stack had a proprietary license and now Redis has a proprietary license.

The inclusion of Redis timeseries is huge!This was available for a long time as an extension as part of Redis Stack, but most hosted Redis providers don&#x27;t make extensions available (I&#x27;m assuming due to nuances in Redis&#x27;s not-quite-open licensing).If cloud providers which include Redis are now going to include this, it opens up a lot of potential for my use case.

We used Redis in a project where we also manage hosting on a semi-public cloud infrastructure and I had troubled figuring out if license change applied to our situation. We didn&#x27;t want to pay a lawyer to figure this out, so we switched to Valkey.

I dunno, MongoDB is as if it&#x27;s gone, due to a license change in 2018. So asking if redis should be thought of the same as MongoDB is a legitimate question.I just gave valkey-container its 100th star <a href="https:&#x2F;&#x2F;github.com&#x2F;valkey-io&#x2F;valkey-container">https:&#x2F;&#x2F;github.com&#x2F;valkey-io&#x2F;valkey-container</a>

valkey is still dropin compatible now so migration is pretty easy.plus aws elasticache give you like 30% price cut when you switch to valkey powered engine ; which make it a pretty good incentive.

No, like yes they pissed a lot of people off and some people did migrate. But a large majority of &quot;enterprise&quot; customers didn&#x27;t, it&#x27;s just too much effort for a service you are paying for anyway.

We&#x27;ve switched to <a href="https:&#x2F;&#x2F;github.com&#x2F;microsoft&#x2F;Garnet">https:&#x2F;&#x2F;github.com&#x2F;microsoft&#x2F;Garnet</a> and been very happy

There is a lot of adoption of Valkey. I know it&#x27;s fun to hate on AWS, but there is a wider shift than just them.<a href="https:&#x2F;&#x2F;cloud.google.com&#x2F;blog&#x2F;products&#x2F;databases&#x2F;announcing-memorystore-for-valkey" rel="nofollow">https:&#x2F;&#x2F;cloud.google.com&#x2F;blog&#x2F;products&#x2F;databases&#x2F;announcing-...</a>
<a href="https:&#x2F;&#x2F;upcloud.com&#x2F;blog&#x2F;now-supporting-valkey" rel="nofollow">https:&#x2F;&#x2F;upcloud.com&#x2F;blog&#x2F;now-supporting-valkey</a>
<a href="https:&#x2F;&#x2F;aiven.io&#x2F;blog&#x2F;introducing-aiven-for-valkey" rel="nofollow">https:&#x2F;&#x2F;aiven.io&#x2F;blog&#x2F;introducing-aiven-for-valkey</a>
<a href="https:&#x2F;&#x2F;www.instaclustr.com&#x2F;blog&#x2F;valkey-now-available&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.instaclustr.com&#x2F;blog&#x2F;valkey-now-available&#x2F;</a>
<a href="https:&#x2F;&#x2F;elest.io&#x2F;open-source&#x2F;valkey" rel="nofollow">https:&#x2F;&#x2F;elest.io&#x2F;open-source&#x2F;valkey</a>

&gt;`HEXPIRE`Finally. Hope they implement this soon at Valkey.

Only AWS did, and their fork is already lacking several important new features like HEXPIRE.

I thought people stopped using Redis and moved on to a fork because of licensing issues. Is this true?

Obnoxious amount of cookie&#x2F;spam popups.

The Fastest Redis Ever