We've been disappointed, in some way or another, with almost every one we've tried as well. Interestingly, one of our uses of Tokyo cabinet completely choked a

We've been disappointed, in some way or another, with almost every one we've tried as well. Interestingly, one of our uses of Tokyo cabinet completely choked at somewhere between 60-70gb of data. At the same time, these articles can be very valuable for us right now. Yes, this particular piece is a bit fluffy, but they invite skepticism and many of the feedback people give. We've never used Voldemort in production, but in heavy load testing we were able to stuff in a few hundred million records with only three instances. Retrieval remained acceptably quick, even while the inserts where going on. However, when we looked it didn't support repartitioning/rebalancing of the data set. This may have changed. Cassandra and MongoDB offer a great deal more functionality than, say, Voldemort or Tokyo. Cassandra seems like a really awesome choice, but is currently under heavy development.