I do, though I don't use it for certain types of things for which it's ill-suited--it's a document store, it's non-relational, it's not really as fault-tolerant

I do, though I don't use it for certain types of things for which it's ill-suited--it's a document store, it's non-relational, it's not really as fault-tolerant as I'd like for certain types of applications. That said, it's got a really nice query API and is quite simple to get up and running for hackathons or simple home projects. It's got a decent map/reduce story for simple tasks, and overall I don't really see anything wrong with it. There's just a lot of backlash because some earlier versions did dumb things by default (which were fixable if you consulted the docs), because Postgres can do almost all of the storage things Mongo does and faster (once finally setup and tuned, and if you don't mind losing that nice API [unless you want to set things up with Mongres or similar hacks]), and lastly that all of the cool kids on HN were congratulating each other on how awesome Mongo was and just in general being annoying. That's it, really. EDIT: To misquote Tyler Durden: "You're not your fucking tech stack." Especially when you are working on something that is more of a business problem than anything else.