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



Redis Ecosystem Updates

The Redis 1.2.0 release (shortly followed by a small bugfix release[1]) has introduced a new persistence option: Append Only File.

On the mailing list [2], Salvatore Sanfilippo (@antirez) has detailed the process of migrating an existing Redis store to the “Append Only File”:

  1. Create the initial append only file from your dataset just issuing: redis-cli bgrewriteaof
  2. When the rewrite is done (you can see it from the INFO command output) stop the server
  3. Edit redis.conf in order to enable append only
  4. Restart the server
  5. Profit!

Just a few days after Redis 1.2.0 was released, Rediska, a PHP client for Redis that provides full integration with Zend, the popular PHP framework that is also looking to integrate with CouchDB and MongoDB, has announced the 0.3.0 release [3] featuring :

  • Full support Redis 1.2.0 API
  • Pipelining
  • Operate with keys on specified (by alias) server
  • Specify DB index in server config
  • Easy extending Rediska by adding you own or overwrite standart commands
  • Lazy loading
  • Full documentation

Last, but not least, Chris Streeter has published a server throughput benchmark [4] when using Redis with another PHP Redis driver PRedis:

Credit Chris Streeter