Re:Hive: A Globally-Distributed Key/Value Store [pdf]
by avereveard on Friday January 28, 2022 @01:19PM
(#30118394)
Redis is more of a datastore than a database. Sure it will persist data if you coherce it forcefully to, but works best as a transient store, with data residing somewhere else.
Re:Hive: A Globally-Distributed Key/Value Store [pdf]
by avinassh on Saturday January 29, 2022 @12:16AM
(#30123993)
How do you differentiate between a datastore and database?
Re:Hive: A Globally-Distributed Key/Value Store [pdf]
by aaomidi on Friday January 28, 2022 @02:42PM
(#30119381)
Not really? This is exactly what the comment before you is calling out.
Using the word "forcefully" to mean "configure it to", is weird, and is just setting the tone of the discussion without adding anything meaningful to it.
> but works best as a transient store
"best". It's odd to see such a strong determination of what a tool should be used for. It works fine as a "transient store", and it also works fine as a database.
Re:Hive: A Globally-Distributed Key/Value Store [pdf]
by avereveard on Friday January 28, 2022 @04:23PM
(#30120549)
sure, as you can use a monkey wrench for all your nuts. it's not going to be as pleasant, and it's going to ruin the nuts eventually.
Re:Hive: A Globally-Distributed Key/Value Store [pdf]
by aaomidi on Friday January 28, 2022 @04:35PM
(#30120679)
If you say so. This way of thinking about redis holds so many organizations back.
Seriously, go try it again as a database.
Re:Hive: A Globally-Distributed Key/Value Store [pdf]
by avereveard on Friday January 28, 2022 @06:35PM
(#30122005)
you're missing the point. it's not the capability to handle data. it's the pain to backup a rotating dump file and a full datalog. one could try to backup using a replica, but the rdb gets sent over the wire ayway, and that's a load of bandwidth and disk and everything being thrown at the problem. it's madness.
and that's before considering partitioning. good luck synchronizing snapshots of each shard at the same point in time - your restore will have all kind of inconsistencies for crossreferenced data.
None of those other examples are key-value stores. Mongo is the most similar, but really has more in common with MySQL and Postgres than Redis/Hive. Key value stores view their values as opaque, modulo things like providing embedded hash maps. Queries in key-value stores are pretty simple, and are focused on the _keys_. Eg, iterate over these keys in sorted order and give me the values.
All of these other databases provide advanced querying capabilities by having type systems and the ability to introspect their objects and make decisions based on their values.