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

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 ;).

B+ seems fair ;) We'll try to improve the docs especially adding examples of real-world patterns for every command.

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.

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.

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.

~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!

Elephant now has its own native storage? (When I used it last it still relied on BerkeleyDB or a SQL store for data persistence).

Elephant has various backends, a Redis backend looks inevitable, imo ;-)

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.

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?

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.

Any key value store can be described as scalable because they are so easy to shard.

It does real master to master replication.

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

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