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



Choosing MongoDB


  • it’s super fast (it depends on the case – but for ours it is about 5 times faster than a SQL database)
  • it’s extremely scalable – up to petabytes with little effort (we don’t need the space for a petabyte, but 10 terrabytes)
  • it has got a very good replication mechanism (replica sets)
  • it has got a easy to use Java API
  • the storage format is JSON, which is very easy to handle in Java as well as in Java Script
  • it’s easy in operations – you don’t have to sit an admin next to it
  • is has got a very active community (I had bug fixes in less than 20 minutes!!! Thanks Elliot! :)
  • they have a clear release cycle
  • the company behind MongoDB (10gen) got fresh money for the next years


  • none of us has ever used a NoSQL database
  • the project is relatively young
  • you don’t have the relational integrity

Not much to object to, but I’m wondering about two of the pros: scalability and easy operations. How have they reached those conclusions?

Original title and link: Choosing MongoDB (NoSQL databases © myNoSQL)