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

Concerns in the Tokyo Cabinet Community

The Tokyo Cabinet community is starting to express its concerns related to the future of the project. Back when I covered Kyoto Cabinet, the successor of Tokyo Cabinet I have expressed the same concerns. Unfortunately even if I tried to contact the creator of these projects to shed some light on their future, I got no response back.

I really hope this will not be an issue for the Tokyo Cabinet users/community and they will find a solution that will work well for everyone.

@jedisct1

via: http://groups.google.com/group/tokyocabinet-users/browse_thread/thread/f7807cf31c26b878