In-memory database Redis wants to dabble in disk

I was confused because I know Redis already offers persistence. <a href="https:&#x2F;&#x2F;redis.io&#x2F;docs&#x2F;management&#x2F;persistence&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;redis.io&#x2F;docs&#x2F;management&#x2F;persistence&#x2F;</a> The main difference here is how its runtime will shift from runtime data only in RAM to not storing as much data in RAM and looking up on disk. Current Redis persistence looks like the runtime is stored in RAM and changes are periodically or append only persisted to disk. I hope I got that right.

For those interested in an alternative to Redis on disk, compatible with the Redis protocol, have a look on Kvrocks[1] which was recently accepted in the Apache foundation. It is based on RocksDB and works quite nicely for us.<p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;apache&#x2F;kvrocks">https:&#x2F;&#x2F;github.com&#x2F;apache&#x2F;kvrocks</a>

&gt; It is part of the drive to make Redis &quot;more like your classic database,&quot; he said. In the future, support for natural language queries and enhanced vector and feature store capabilities will be added. This initiative aligns with Redis&#x27;s ambition to be seen as more than just a fast, albeit expensive, cache<p>This sounds to me like not understanding your place in the market or why people use your product. I can name half a dozen classic SQL databases off hand. I can’t name a tool that competes with Redis at their niche. Why aim for an already oversaturated market when you already have a good profitable niche.

&gt; One main criticism of Redis had been its lack of support for SQL, the ubiquitous query language. Trollope said that was fixed now. A module RediSQL is available on GitHub.<p>I think redisql has been supplanted by zeesql - <a href="https:&#x2F;&#x2F;zeesql.com&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;zeesql.com&#x2F;</a>

I&#x27;ve tried Redis-on-flash (enterprise version), and performance was very poor. Its just lsmt underneath and suffers from all the usual lsmt issues.<p>In the end we went with Aerospike which actually while backed by NVMe, outperforms redis backed by memory. Aerospike in memory is completely absurd speeds and throughput. Sadly the setup is a bit weird and query model is a bit wonky but we worked around it. A bit sad on how expensive the enterprise version is.

They mention both flash and disk, which finally gets explained as tiers 2 and 3. Also less clear though I assume this applies to their hosted service offering and not the core software.<p>&gt; &quot;We can take the lesser-used data that hasn&#x27;t been touched in a while and shuttle it off to flash where it can sit for a while. When the user comes back eventually, it&#x27;s very easy for us to seamlessly move it from flash back into memory. And that allows the company to save costs,&quot; he said.<p>&gt; Redis is now planning to extend the concept to disk-based memory to offer support for a three-tiered architecture.

How bad is Redis with a swap file on SSD?<p>I would expect it to be a very reasonable middle ground that requires almost no work and it is already enough and ready for most use cases.

Anyone know how their plans differ from the Virtual Memory plans that antirez had about 13 years ago, implemented in Redis 2.6, and then (wisely) abandoned?<p><a href="https:&#x2F;&#x2F;redis.io&#x2F;docs&#x2F;reference&#x2F;internals&#x2F;internals-vm&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;redis.io&#x2F;docs&#x2F;reference&#x2F;internals&#x2F;internals-vm&#x2F;</a>

How would the example of a scoreboard work with tiered memory?<p>Surely you need the sorted set in memory to derive rank&#x2F;manipulate it etc?<p>Or would you have to shard it and add other elements on top in app code to focus on only a subsection of the data?

I think I would rather they added a write-ahead-log to make writes durable, than disk lookup to support bigger-than-RAM datasets (slowly).

It&#x27;s not mentioned in the article but this is Redis Enterprise which is more like a superset of open source Redis.

memcached has recently gained the ability to spill to disk: <a href="https:&#x2F;&#x2F;github.com&#x2F;memcached&#x2F;memcached&#x2F;wiki&#x2F;Extstore">https:&#x2F;&#x2F;github.com&#x2F;memcached&#x2F;memcached&#x2F;wiki&#x2F;Extstore</a><p>we recently implemented this to grow our caches to &gt;50TB

Redisk... Sounds like a good April fools joke

<i>It is part of the drive to make Redis &quot;more like your classic database,&quot; he said. In the future, support for natural language queries and enhanced vector and feature store capabilities will be added.</i><p>Seems way off the mark for why people use Redis. Developers use it precisely because it&#x27;s not like their classic databases.

What I actually need is a better way to bootstrap a cluster using Docker containers …