ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

Goodbye Tokyo Cabinet

A while ago I started to sound like a broken record when saying that even if data modeling in NoSQL seems too simple to be true, in fact it is once again an art we need to master as otherwise sooner or later will start complaining about it. Well it looks like that time is starting to be now.

Brian on why he stopped using Tokyo Cabinet:

I have no idea how to use a key/value store database properly. TC will take anything you dump into it, which is both a strength and a weakness.

[…] Some kinds of queries were still awkward in TC.

So if you still think schema-less means not data modeling, then you are doing it wrong!

via: http://briancarper.net/blog/545/goodbye-tokyo-cabinet-hello-postgresql