There's been a few of these posts recently and in every case it's the fault of the author either because they chose the wrong product for their use, because it'

There's been a few of these posts recently and in every case it's the fault of the author either because they chose the wrong product for their use, because it's not being used as directed or because the unstable versions are being used. - There are no transactions in databases like MongoDB. That's clear. - Reported "corruption" and data loss but no reproduce steps. What version? Did the server crash? Have you reported to the developers? We've been using MongoDB for over a year in production having started at v0.9 and now using only stable releases and have never lost any data when we do 5-8k inserts per second. - No joins. It's a non relational database, what were you expecting? - Schemaless. Yes - don't make typos / QA your code. - Unstable replication. We've had a few issues with replication but nothing that can be described as "unstable". Again, a general statement "nothing but problems" without going into specifics. - Not stable. I refer above with our long usage history. It's unstable if you use the dev versions, as expected. I don't claim MongoDB is perfect, indeed I've written about several issues we've had[1], but nothing critical or show stopping. It seems it just isn't a right fit for what the author wants. [1] http://blog.boxedice.com/2010/02/28/notes-from-a-production-mongodb-deployment/ http://blog.boxedice.com/2010/02/28/notes-from-a-production-...