In-memory database Redis wants to dabble in disk
theregister.com
In-memory database Redis wants to dabble in disk
1–10 of 63 posts
Re: In-memory database Redis wants to dabble in disk
#2It is part of the drive to make Redis "more like your classic database," he said. In the future, support for natural language queries and enhanced vector and feature store capabilities will be added.
Seems way off the mark for why people use Redis. Developers use it precisely because it's not like their classic databases.
Re: In-memory database Redis wants to dabble in disk
#3They 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.
> "We can take the lesser-used data that hasn'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's very easy for us to seamlessly move it from flash back into memory. And that allows the company to save costs," he said.
> Redis is now planning to extend the concept to disk-based memory to offer support for a three-tiered architecture.
Re: In-memory database Redis wants to dabble in disk
#4For 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.
Re: In-memory database Redis wants to dabble in disk
#5It is part of the drive to make Redis "more like your classic database," he said. In the future, support for natural language queries and enhanced vector and feature store capabilities will be added. Seems way off the mark for why people use Redis. Developers use it precisely because it's not like their classic databases.
[deleted]
Re: In-memory database Redis wants to dabble in disk
#6It is part of the drive to make Redis "more like your classic database," he said. In the future, support for natural language queries and enhanced vector and feature store capabilities will be added. Seems way off the mark for why people use Redis. Developers use it precisely because it's not like their classic databases.
I don’t think that’s necessarily always true. I was recently looking into using Redis as a regular database. Unfortunately data is still kept in memory even if it’s persisted on disk, so it was a no-go. You’d be surprised what people want!
Re: In-memory database Redis wants to dabble in disk
#7What I actually need is a better way to bootstrap a cluster using Docker containers …
Re: In-memory database Redis wants to dabble in disk
#8It is part of the drive to make Redis "more like your classic database," he said. In the future, support for natural language queries and enhanced vector and feature store capabilities will be added. Seems way off the mark for why people use Redis. Developers use it precisely because it's not like their classic databases.
I don’t think that’s necessarily always true. I was recently looking into using Redis as a regular database. Unfortunately data is still kept in memory even if it’s persisted on disk, so it was a no-go. You’d be surprised what people want!
Perhaps you are looking for LMDB?
Re: In-memory database Redis wants to dabble in disk
#9What I actually need is a better way to bootstrap a cluster using Docker containers …
Re: In-memory database Redis wants to dabble in disk
#10I was confused because I know Redis already offers persistence. https://redis.io/docs/management/persistence/
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.