Earlier quoted context omitted.
Are you suggesting that there's no need for Redis to integrate persistent-storage support because every user should download some library and patch the Redis source themselves? And that would somehow be better?
I'm suggesting you haven't read enough before replying, just like I did on my first comment. See "Myrocks" as an example of what the first user meant with lmdb. Replace "mysql -> redis" and "rocksdb -> lmdb".
In-memory database Redis wants to dabble in disk
41–50 of 63 posts
Re: In-memory database Redis wants to dabble in disk
#42Earlier quoted context omitted.
I'm suggesting you haven't read enough before replying, just like I did on my first comment. See "Myrocks" as an example of what the first user meant with lmdb. Replace "mysql -> redis" and "rocksdb -> lmdb".
I'm looking for a standard, well-known, drop-in product - that's what Redis is, that's why persistent storage support in Redis is interesting. If I have to search up some combination thing then it's already a non-starter.
Re: In-memory database Redis wants to dabble in disk
#43Re: In-memory database Redis wants to dabble in disk
#44> It 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. This initiative aligns with Redis's ambition to be seen as more than just a fast, albeit expensive, cache This sounds to me like not understanding your place in the market or why people use your product. I can name hal…
Re: In-memory database Redis wants to dabble in disk
#45> It 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. This initiative aligns with Redis's ambition to be seen as more than just a fast, albeit expensive, cache This sounds to me like not understanding your place in the market or why people use your product. I can name hal…
Presumably because there are a lot of things that straddles the two, and where you risk losing people to databases or hybrid setups where the Redis use will be simple enough that people won't want to pay for support.
E.g. cases where you can't afford to keep it all in memory where you today might end up resorting to using Redis as just a dumb-ish in front of a database, or even avoiding Redis entirely in favour of in-memory tables or aggressive cache settings for your database even in cases where you might prefer Redis if it could intelligently handle a larger working set more cheaply.
And also to create a buffer given that the level of oversaturation in the classic database market may make their niche a tempting target to try to expand into for some of those to set themselves apart.
Re: In-memory database Redis wants to dabble in disk
#46> It 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. This initiative aligns with Redis's ambition to be seen as more than just a fast, albeit expensive, cache This sounds to me like not understanding your place in the market or why people use your product. I can name hal…
Recently DHH of Rails fame gave a talk about Redis and how at their company it's being replaced in favor of long term storage on the now much faster and cheaper SSDs.
The takeaway was that the long caching it enables yields far better real world results in their products. He even had some charts.
Re: In-memory database Redis wants to dabble in disk
#47> It 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. This initiative aligns with Redis's ambition to be seen as more than just a fast, albeit expensive, cache This sounds to me like not understanding your place in the market or why people use your product. I can name hal…
Assumedly, because they do know their place in the market and decided it's not great and that the outlook is worse. Recently DHH of Rails fame gave a talk about Redis and how at their company it's being replaced in favor of long term storage on the now much faster and cheaper SSDs. The takeaway was that the long caching it enables yields far better real world results in their products. He even had some charts.
Re: In-memory database Redis wants to dabble in disk
#48> 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. I think redisql has been supplanted by zeesql - https://zeesql.com/
Author of zeesql/redisql here!
Unfortunately I was not able to figure out a clear business model for the module.
If any of you guys need it also the PRO version, just write me.
Re: In-memory database Redis wants to dabble in disk
#49Earlier quoted context omitted.
Assumedly, because they do know their place in the market and decided it's not great and that the outlook is worse. Recently DHH of Rails fame gave a talk about Redis and how at their company it's being replaced in favor of long term storage on the now much faster and cheaper SSDs. The takeaway was that the long caching it enables yields far better real world results in their products. He even had some charts.
URL to talk?
Re: In-memory database Redis wants to dabble in disk
#50I 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.