Building TweetReach with Sinatra, Tokyo Cabinet and Grackle
I’m starting to forget how many Twitter NoSQL-enabled apps I’ve mentioned on the NoSQL blog — fortunately the consistent tagging helps, so you can find them all under the tag Twitter — but every time I’m finding a new one I feel like posting about it.
This time it is a presentation about building a Twitter utility using Tokyo Cabinet and ☞ Sinatra (a Ruby web framework).
The author concludes with some Tokyo Cabinet lessons learned:
Lack of auto-expiration when using as mostly a key-value cache is annoying
Would definitely use it again for this type of task
I think it is interesting to note that from the key-value stores covered here, only Redis comes with support for key expiration.
