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



MongoDB: 10 Things You Might Not Know About It

I only missed the 7th and 9th:

  1. MongoDB uses 1 BFGL (big f***ing global lock) for separating reads and writes.
  2. MongoDB does not have a statistical query plan optimizer
  3. The Mongos (pronounced “mongo”-”ess”) process is only needed when you do sharding
  4. MongoDB supports Master-Slave replication as well as Replica-Sets
  5. MongoDB supports “slave-delay” in secondary replicas
  6. MongoDB should likely not be run in a 32-bit environment
  7. MongoDB automatically tells you in the log about any query that takes longer than 100ms to run
  8. MongoDB can be setup to do profiling if a query starts taking longer than a certain amount of time
  9. MongoDB doesn’t support multi-master replication. They think this is good because it keeps things logically simple. Also, the system is far simpler as it doesn’t have to worry about write-collisions across multiple masters.
  10. In a replicated setup, MongoDB supports something called an Arbiter whose job is to break ties

The Hacker News threads adds a couple of other less known things. And there’s also the 11 buddy disappointments in MongoDB.

Original title and link: MongoDB: 10 Things You Might Not Know About It (NoSQL databases © myNoSQL)