4 ms·

We made a start on this at the NoSQL meetup, the spreadsheet is here: http://spreadsheets.google.com/ccc?key=0Ale_YaCwKEUVclVFVFlrUWt5aWhQaGQ0OXVCMUl4Vmc&hl=en

by russss 17y ago

We made a start on this at the NoSQL meetup, the spreadsheet is here: http://spreadsheets.google.com/ccc?key=0Ale_YaCwKEUVclVFVFlrUWt5aWhQaGQ0OXVCMUl4Vmc&hl=en http://spreadsheets.google.com/ccc?key=0Ale_YaCwKEUVclVFVFlr... It covers a bit more than KV stores - it's basically all of the non-relational data stores. If anyone wants access to update it, let me know.

nico 17y ago
Thanks! nice work. Would love to see some kind of benchmark on that table though. I know it's hard to compare, but maybe add some comments to the results?
antirez 17y ago
Hello, it seems unfair for me to update the doc, but I can give you some info. Language: C License: BSD (new version) Partitioning: Client Expansion: not sure about the meainig SLOC: 9262 including all the libs, no external dependence Persistence: snapshotting on disk Client protocol: custom ASCII Data model: data structures (Strings, Lists, Sets) Docs: can't rate it myself Community: It's more known inside the Ruby community AFAIK
- russss 17y ago
  Thanks, I updated that. I gave the docs a B+, but I haven't used Redis myself so it was only based on a quick look ;).
  - antirez 17y ago
    B+ seems fair ;) We'll try to improve the docs especially adding examples of real-world patterns for every command.
aolnerd 17y ago
Nice work. It would be nice to know which projects have production sites that store the primary copy of data in these projects, as opposed to a secondary copy that is used for fast reads.
mahmud 17y ago
Who do I contact about reviewing Lisp K/V stores? I would double the content of your list and give exposure to some Lisp gems you haven't heard of :-) Yes, Lisp stores with C API :-D AllegroCache, Elephant and ManarDB.
- russss 17y ago
  Never heard of any of them, but then I don't code Lisp ;). I have to say that I'm only considering free, open source solutions in that spreadsheet.
  - mahmud 17y ago
    ~3 are MIT licensed. I have brewed up my own thing as well. Shoot me an email will ya? or I can get yours off of the .uk site in your profile. Cheers!
- joubert 17y ago
  Elephant now has its own native storage? (When I used it last it still relied on BerkeleyDB or a SQL store for data persistence).
  - mahmud 17y ago
    Elephant has various backends, a Redis backend looks inevitable, imo ;-)
- holygoat 17y ago
  I'd call AllegroCache and Elephant object persistence frameworks, not KV stores. AllegroCache can store persistent maps and sets, so you could use it as a KV store, but that's hardly taking advantage of its power.
yummyfajitas 17y ago
Side note: how does Tokyo Tyrant get listed as a "highly scalable data store"? The only way you can scale with TT is by buying a bigger machine.
- simonw 17y ago
  Any key value store can be described as scalable because they are so easy to shard.
- jokull 17y ago
  It does real master to master replication.
wmf 17y ago
You're missing eXist, MonetDB, Sedna, etc.
mumrah 17y ago
Is there some reason why Amazon SimpleDB not included these type lists? It always seems to be excluded from NoSQL discussions

by russss 17y ago

nico 17y ago

Thanks! nice work. Would love to see some kind of benchmark on that table though. I know it's hard to compare, but maybe add some comments to the results?

antirez 17y ago

Hello, it seems unfair for me to update the doc, but I can give you some info. Language: C License: BSD (new version) Partitioning: Client Expansion: not sure about the meainig SLOC: 9262 including all the libs, no external dependence Persistence: snapshotting on disk Client protocol: custom ASCII Data model: data structures (Strings, Lists, Sets) Docs: can't rate it myself Community: It's more known inside the Ruby community AFAIK

russss 17y ago
Thanks, I updated that. I gave the docs a B+, but I haven't used Redis myself so it was only based on a quick look ;).
- antirez 17y ago
  B+ seems fair ;) We'll try to improve the docs especially adding examples of real-world patterns for every command.

aolnerd 17y ago

Nice work. It would be nice to know which projects have production sites that store the primary copy of data in these projects, as opposed to a secondary copy that is used for fast reads.

mahmud 17y ago

Who do I contact about reviewing Lisp K/V stores? I would double the content of your list and give exposure to some Lisp gems you haven't heard of :-) Yes, Lisp stores with C API :-D AllegroCache, Elephant and ManarDB.

russss 17y ago
Never heard of any of them, but then I don't code Lisp ;). I have to say that I'm only considering free, open source solutions in that spreadsheet.
- mahmud 17y ago
  ~3 are MIT licensed. I have brewed up my own thing as well. Shoot me an email will ya? or I can get yours off of the .uk site in your profile. Cheers!
joubert 17y ago
Elephant now has its own native storage? (When I used it last it still relied on BerkeleyDB or a SQL store for data persistence).
- mahmud 17y ago
  Elephant has various backends, a Redis backend looks inevitable, imo ;-)
holygoat 17y ago
I'd call AllegroCache and Elephant object persistence frameworks, not KV stores. AllegroCache can store persistent maps and sets, so you could use it as a KV store, but that's hardly taking advantage of its power.

yummyfajitas 17y ago

Side note: how does Tokyo Tyrant get listed as a "highly scalable data store"? The only way you can scale with TT is by buying a bigger machine.

simonw 17y ago
Any key value store can be described as scalable because they are so easy to shard.
jokull 17y ago
It does real master to master replication.

wmf 17y ago

You're missing eXist, MonetDB, Sedna, etc.

mumrah 17y ago

Is there some reason why Amazon SimpleDB not included these type lists? It always seems to be excluded from NoSQL discussions