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

Memcached on top of Redis?

I read a couple of posts[1] talking about Gear6 Memcached native query support and Redis integration. Anyways, based on the details I’ve found so far[2], what I understand is:

  1. Gear6 memcached provides an enhanced API that allows querying the key/value space
  2. Gear6 memcached is looking to support more data types by using Redis support for types like lists, sets, ordered sets, hashes[3]
  3. or Gear6 is looking to provide commercial support for Redis

These left me with the question: why would you use memcached on top of Redis?

Possible answers:

  1. if the integration would preserve the same memcached API (nb I am not sure though this would be possible) then
  2. such a product might be useful for projects needing both RDBMS and Redis (note: but in the end the project would still need to be aware of both storage APIs)
  3. such a product might be useful for transitioning towards Redis alone

  4. the integration would just add features missing from the current version of Redis (f.e. elastic scaling, sharding, etc.)

Do you see any other reasons for using memcahed on top of Redis?

References