Presentation: Tokyo Cabinet / Tyrant @ Nosql Paris

Embedded below are the slides of Florent Solt (@florentsolt) Tokyo Cabinet / Tyrant presented at Nosql Paris.

Florent seems to be working at Netvibes and his slides are presenting briefly how and what kind of Tokyo Cabinet setup is in use there.

I also liked the Tokyo Cabinet / Tyrant strength and weaknesses slides:

Tokyo Cabinet / Tyrant Weaknesses

• No bug tracker, no public code repository

  Note: not so long ago, I’ve posted about these concerns in the Tokyo Cabinet community

• The documentation is not good enough

  Note: I’m might have some good news here. Stay tuned!

• Under heavy load, master-master replication can fail
• Databases can be corrupted

  Note: you might find Tokyo Cabinet database recovery useful for such unwanted situations

• With big tables, queries need a lot of RAM and time
• Tables seem slow & their configuration is not so clear

  Note: you can learn more about the different Tokyo Cabinet database types and their configuration options

• No live backup, the copy function locks the database

Tokyo Cabinet / Tyrant Strenghts

• Easy to deploy and setup
• Easy to use
• It’s not a black box
• Good to very good performance for most of the time
• Small memory footprint
• A single Tokyo Tyrant process can handle thousands of connections
• Many command line tools
• Lua extensions

I’d definitely be interested to hear much more about how Netvibes is using Tokyo Cabinet / Tyrant, so ping me if you are ready to share more with the Tokyo Cabinet community.