"Don't Use MongoDB" --> Hmmm
You had to be hiding under a rock to not have seen the (anonymous) Don't Use MongoDB post that has been making the rounds. I've replicated it below, just in case it vanishes. The author is (as of this writing) unknown, but he/she brings up a lot of points. For what its worth, I completely agree with the final recommendations, viz. 1. Don't lose data, be very deterministic with data 2. Employ practices to stay available 3. Multi-node scalability 4. Minimize latency at 99% and 95% 5. Raw req/s per resource Obligatory caveat here - I'm a big fan of BigCouch , and have been using it for a while now. That said, to defend Mongo (just a little bit. and yes, it hurts), when we started going down the CouchDB path, I knew what I was doing. I'd read everything, I'd tested the bejeebers out of Couch (especially in the 0.9.0 days), and already had a pretty thorough grounding in NoSQL tech for a variety of unrelated reasons which I won...