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

Redis Over HTTP

Dor Kalev’s idea of exposing Redis functionality over HTTP is extremely interesting. I’d like to suggest a couple of things:

  • make it RESTful

    For example:

    • /set/KEY/VALUE: should be a PUT request to /KEY/
    • /get/KEY: should be a GET to /KEY
  • I don’t really see the benefit of having Comet used as a way to get notifications for updated values (as suggested in the article).

    Some Redis users are already discussing about a need for push notifications[^1]. I liked the way CouchDB is dealing with this requirement and suggested a similar solution for Redis. And I think Comet would play quite nicely with something like CouchDB’s _changes.

  • I think Comet would make more sense with the Redis list read operations

What else would you like to see?

via: http://www.dorkalev.com/2010/02/sikwamic-simple-key-value-with-comet.html