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



3 Reasons to Use MongoDB

Ryan Angilly:

MongoDB is teh awesome because of a simple query syntax, the ability to shard data across machines easily, and the ability to store files in GridFS while taking advantage of replication & sharding.

Indeed, I think the combination of query syntax and GridFS makes MongoDB unique.

Sharding is supported by many other NoSQL databases and for many of these things are even simpler than having mongod, mongos, etc. Between document databases, CouchDB has recently got BigCouch to address the scaling issue[1].

As regards querying, one could say that having MapReduce around would get you similar functionality to MongoDB queries. But starting with users’ familiarity with using queries vs programmatic querying and up to execution behavior MongoDB queries and MapReduce are quite different.

  1. Even before BigCouch, there were different solutions for scaling CouchDB  ()

Original title and link for this post: 3 Reasons to Use MongoDB (published on the NoSQL blog: myNoSQL)