tags:

views:

163

answers:

1
+1  Q: 

What does "Document-oriented" vs. Key-Value mean when talking about MongoDB vs Cassandra?

What does going with a document based NoSQL option buy you over a KV store, and vice-versa?

A: 

The biggest difference is that a document-oriented database supports secondary indexes, K/V does not. In general, document-oriented dbs tend to allow richer queries, allowing things like range queries, sorting, and other types of "advanced" operations.

mdirolf  2010-06-15 16:23:06
Cassandra will support secondary indices in the next release (0.7)
Schildmeijer  2010-06-16 06:44:10

related questions

MongoDB dbref in perl
I need an advice about NoSQL/MongoDb and data/models structure
Middleware for MongoDB or CouchDB with jQuery Ajax/JSON frontend
Grouping by Nested Object Keys in MongoDB
Using Sinatra and MongoDB - what's the recommended way to "keep alive" the mongodb connection between http requests?
MongoMapper and migrations
MongoDB takes long for indexing
Two questions about mongodb and indexing
mongodb, pymongo querying
MongoDB: How to update multiple documents with a single command?
How to run this query in mongodb?
using sphinx search with mongodb as datasource
Storing Directory Hierarchy in a Key-Value Data store?
Document based database for .NET
Bittorrent tracker
Which is the most suitable Key-Value Store for a RDBMS background person?
When to use MongoDB or other document oriented database systems?
[Django] Custom storage system for GridFS (MongoDB)?
Symfony (PHP framework) and MongoDB ( or any json-based database)
Unique IDs with mongodb
What are the required functionnalities of ETL frameworks ?
MongoDB and visual C++ 2008 linker errors
Updating nested documents in mongodb
MongoDB or CouchDB - fit for production?
Databases using JSON as storage/transport format