Live data from Hacker News

In-memory database Redis wants to dabble in disk

theregister.com

31–40 of 63 posts

Re: In-memory database Redis wants to dabble in disk

#31
post #19

Earlier quoted context omitted.

>You’d be surprised what people want! If what you want is persistent k/v, then there are already tons databases that can do that. Redis has a different use case, so what are you trying to say? That you want to misuse tools?

> If what you want is persistent k/v, then there are already tons databases that can do that. Are there? What's a good, mainstream, persistent k/v for cheap single-node instances? PostgreSQL's KV support isn't good enough, Cassandra and MongoDB expect to be set up as a cluster and have all the overhead of that, BikeshedDB is alpha and I won't touch their upstream for obvious reasons, CouchDB is pretty much unmaintain…

RocksDB?

Re: In-memory database Redis wants to dabble in disk

#32
post #31
post #19

Earlier quoted context omitted.

> If what you want is persistent k/v, then there are already tons databases that can do that. Are there? What's a good, mainstream, persistent k/v for cheap single-node instances? PostgreSQL's KV support isn't good enough, Cassandra and MongoDB expect to be set up as a cluster and have all the overhead of that, BikeshedDB is alpha and I won't touch their upstream for obvious reasons, CouchDB is pretty much unmaintain…

RocksDB?

RocksDB is cool but it seems to be more of a toolkit for building your own K/V store than a standalone product like Redis?

Re: In-memory database Redis wants to dabble in disk

#33
post #23

Earlier quoted context omitted.

How about LMDB ? It’s single writer/multiple reader, very fast and reliable.

This thread is my first time hearing of it, it doesn't seem particularly established/mature (e.g. I can't find cloud services offering managed instances, whereas there are plenty of those for Redis)

You didn't read enough what it actually is. Its embedded db like rocksdb.

Re: In-memory database Redis wants to dabble in disk

#34

> 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/

Pay $7/month for the license for each index/db after the first 3. I bet oracle ends up being cheaper.

Re: In-memory database Redis wants to dabble in disk

#35
post #23

Earlier quoted context omitted.

This thread is my first time hearing of it, it doesn't seem particularly established/mature (e.g. I can't find cloud services offering managed instances, whereas there are plenty of those for Redis)

You didn't read enough what it actually is. Its embedded db like rocksdb.

Then it's hardly a substitute for Redis.

Re: In-memory database Redis wants to dabble in disk

#37
> 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 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.

Re: In-memory database Redis wants to dabble in disk

#39
post #35

Earlier quoted context omitted.

Then it's hardly a substitute for Redis.

You put redis on top of it.

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?

Re: In-memory database Redis wants to dabble in disk

#40
post #39

Earlier quoted context omitted.

You put redis on top of it.

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".
Post reply on HN