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

CouchDB Case Study: SkinnyBoard

From another CouchDB usage story:

One of the things that attracted the SkinnyBoard team to CouchDB is the document-based store with its inherent flexibility. It allows them to store entities and their relationships in a single document without the need for complex lookups and joins required by traditional relational databases. CouchDB’s support for map/reduce also means that they can construct complex queries and store them as design documents externally without the need for having this business logic in their main application.

While using the document model sounds like the right choice from the scenario, I’m confused by the map/reduce related comment which sounds more like stored procedures than normal app queries.

Original title and link: CouchDB Case Study: SkinnyBoard (NoSQL databases © myNoSQL)

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