News for hackers. Stuff that matters.
Re:MongoDB Rules Single Node Deployments, Fails to Scale by towelguy on Wednesday April 01, 2015 @11:00AM (#9304141)
Does this still applies to MongoDB 3.0? since it seems to be a rewrite with a new storage engine [1].

[1] http://www.mongodb.com/blog/post/announcing-mongodb-30

Re:MongoDB Rules Single Node Deployments, Fails to Scale by nemo44x on Wednesday April 01, 2015 @11:59AM (#9304584)
That is based on a pre-2.0 version of MongoDB. The changes and vast improvements from that time to now are huge.

MongoDB probably got a bit ahead of itself too fast - it wasn't mature and took a lot of development shortcuts to get features out fast and people started using it like a mature datastore too fast - and the company behind it didn't help either. But, without a doubt there have been vast improvements across the board and I give them credit for spending the last year and a half not adding many new features but rebuilding the codebase, making it extendable (pluggable storage engines is a cool thing) and addressing numerous issues.

It still has some issues (b-trees aren't the best implementation imo) but the codebase is in a state where I expect over the next few years it will be quite reliable. The tooling around MongoDB has gotten better too. There's still a ton of ways to shoot yourself in the foot too but the defaults are more sensible I think now than then.

What they got right is the clients are awesome and the query language is powerful - especially updates. This matters for a lot of people - it isn't just a drag race always in terms of performance. Now, with increased reliability it's becoming something usable for some use cases.