Hacker News Reader

Comment by neumino | Hacker News Reader

The way it handle failures? You may be interested in this (old-ish) article: http://hackingdistributed.com/2013/01/29/mongo-ft/

View on HN

Another worth read: https://aphyr.com/posts/284-call-me-maybe-mongodb

Although to be fair, it's not just MongoDB that is performing poorly.

How is that a design fault ? It was purely a poorly chosen configuration setting which reflects the fact that Mongo was originally not a general purpose database. And it was never even an issue for 99% of people because all the drivers at the time used the safer settings.

I always find it amusing when people bring these issues up because it's like a giant sticker on their forehead that says "I've never actually seriously spent time with MongoDB before". I always go through the configuration of the database I use to make sure it meets my needs. Only seems sensible.

I'm not sure we've read the same article.

MongoDB is advertised as general purpose database though and majority of people use it that way.

Sure. And that's why the configuration was changed years ago.

The article actually talks about the configuration change. The issues are still there.

>It was purely a poorly chosen configuration setting which reflects the fact that Mongo was originally not a general purpose database.

Thats dubious. 1.) When MongoDB was released, none of the drivers used the "safer" settings. 2.) 10gen, at the time, released benchmarks with the "unsafe" settings comparing it to MySQL and boasted that MongoDB was much faster (ignoring the fact that it wasn't acknowledging your writes).

Hmm, are you able to point us to any of these "benchmarks" with unsafe settings?

AFAIK, until recently (i.e. the last month), there weren't any such benchmarks released by MongoDB - and then, only for 3.x.

I'd be very surprised if any such benchmarks exist, as you claim.

Disclaimer - I work for MongoDB Inc.

Reply on news.ycombinator.com