3 ms·
Tokyo Cabinet: http://www.igvita.com/2009/02/13/tokyo-cabinet-beyond-key-value-store/ http://www.igvita.com/2009/02/13/tokyo-cabinet-beyond-key-va... http://sou
by _sh 18y ago
Tokyo Cabinet:
http://www.igvita.com/2009/02/13/tokyo-cabinet-beyond-key-value-store/ http://www.igvita.com/2009/02/13/tokyo-cabinet-beyond-key-va...
http://sourceforge.net/projects/tokyocabinet/ http://sourceforge.net/projects/tokyocabinet/
- antirez 18y agoNice project, I already read about it. Still note that one of the major points of Redis is to support more complex types as values. Tokyo Cabinet is basically an on-disk hash table library, with an optional networking server using this lib to export the functionality. For example if you want to use Redis in order to store logs from a lot of different computers, and you want to only take the last 1000 entries for every computer, all you need to do is for every computer something like this: RPUSH computer_5 "... your log line ..." LTRIM computer_5 0 999 Redis offers atomic LPOP/RPOP too, this makes pretty easy to create queues where different computers can pop/push values with the guarantee the operation is atomic. Another trivial example: think about implementing something like YC with a key-value DB. Support for lists and sets will make your life much easier :)