Yeah Mongo was "The Flavor Du Jour" just a couple years ago, with MongoDB articles hitting frontage like every week. Now we don't ever hear about it and people don't really use it much either.
People don't use it because it is terrible. I had to manage a 5-node Mongo cluster as recently as 2 years ago, and I still drink heavily because of it. It was a data roach-motel - your documents check in, but they never check out!!!
Everything ran fine, until it was time to fail over - and the company had a 'full failover every quarter' commitment. Every single time we went from the 2-node primary site to the 3-node secondary, all he would break loose. Bad writes, lost partitions, it was a new 'thing' every quarter. Mongo, in my limited experience, was a terrible platform and I recommend everyone who is thinking of implementing it to run screaming. It accepts data SUPER fast, but so does /dev/null.
I haven't personally used it but I believe there is (was) enough factual technical information to reach this conclusion, including this linked blog post of Kyle's. I was shocked when I read that. Data loss is generally not okay and expected. I'd say most were not aware that the potential for data loss was actually in the design of these products before the Jepsen posts. I believe these flaws impacted most of what people were using it for, so its continued use, particularly on new projects, in the presence of other databases such as Cassandra and Riak is surprising.
And this is not even factoring reports of slow progress, in your face bugs, and PITA manageability.
While it us true substantial progress may have occurred in the less than two years since that test, I would need to see some solid evidence of substantial improvement to consider mongoDB.
This is where the MongoDB guys are very sly. MongoDB works brilliantly if you are one developer on one desktop working on one app - you don't need a DBA or any other ops guys, you can just develop away to your little heart's content!
So they write their app and chuck it over the wall to ops, and by then it's a fait accompli, the ops guys know they will look very bad to management if they say "WTF is this?". So they try to make it more-or-less work, then come on HN to share war stories.
Not advocating MongoDB, but I think if we base our opinions solely on how things were 2 years ago, we would end up still basing our opinions on how things were 10 years ago.
Software breaks, 'poor' design decisions are made, etc, but at the same time, 2 years is a lot of time for improvements to be made.
My HTML5 app failed me 3 years ago, I've now been recommending that everyone stay away from HTML5. /s
Maybe it's just me, but I don't know if I could ever trust an engineering culture that thought succeed-without-acknowledgement was a good default. At least not as a primary source of truth system. There are plenty of databases that take data seriously and have from the beginning. I'd probably just use one of those.
You realize that was resolved 1.5 years ago, right? Also, it was a driver-level implementation. Comments like this make you sound more troll and less informative.
People still use it. Hell, some people love it. I was using it about a year ago as a primary caching layer at the company I worked for then. Given a choice I would have gladly picked something else. Damn near anything else actually. Hope its improved since then.
