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

thingler: All content tagged as thingler in NoSQL databases and polyglot persistence

CouchDB Case Study: Thingler, Collaborative Todo Lists

The data-model of Thingler was really simple: there was only one type of object: the Room (essentially a passworded list mapped to a url). The document-store aspect of CouchDB worked well, the application could store all the information in the room, such as the items in the todo (and associated tags), the password, the name and url of the room — in a single document, that was one GET away. The nice thing about this was that the document _id was also the URL of the room. To generate the URLs, the application just used Couch’s _uuids API.

Question to the experts: why using node.js and not CouchApp?

Original title and link: CouchDB Case Study: Thingler, Collaborative Todo Lists (NoSQL databases © myNoSQL)

via: http://www.couchone.com/case-study-thingler