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

Notes on Redis: Data Modeling, Hashes, and Namespaces

A good post showing the benefits of having data structures (like lists, sets, sorted sets, hashes[1]) and using “smart keys” (in the sense of using a namespace-like approach):

My first pass at the problem took advantage Redis’s sets. […] As I continued work on this feature, I realized that I wanted to link to the specific tweet where a Twitter user mentioned a fail. […] Thanks to Redis’s new hash data structure, there was a cleaner way.

As a side note, there still seems to be some confusion about the new Redis command: MULTI/EXEC/DISCARD which is confused for transactional support.

References

  • [1] You can read more about Redis data types ☞ here. Hashes do not seem to be documented yet, but hopefully this will change soon. ()

via: http://akahn.net/2010/03/30/notes-on-redis.html