| SO I think we're almost having two separate arguments here. On the one hand we're talking about Mongo working out of the box and on the other we're talking about developer skill. I'll agree with you that an unskilled developer is going to have a bad time running any Database, but I take issue with the idea that defaults aren't important. The default settings are the defaults for a reason. Whether that reason is ease of adoption or performance testing, there's a reason. Mongo's default behavior was not sensible and has since been corrected to be more sensible, and I think we both agree on this point. Mongo is a really cool database with a lot of neat features, but it doesn't get a pass just because it's cool. If the defaults on Mongo could cause data loss, they should change the defaults, right? I agree you should understand your backend, but I also see a lot of value in having sane default settings. To be honest, the majority of users may never pass beyond the default settings, which is a shame, but true. So the author's rant is just that, but he's not wrong. He might be mistaken about the potential of Mongo, but he's not really mistaken about Mongo "out-of-the-box". Does that clarify my position with respect to the author's opinions? |
I am not saying he is wrong, and i am not saying that mongo is wrong either. I feel, if you RTFM, that they are very very clear as to the state of things. They are not hiding anything and if anything they are providing and application state that is not ideal for said user too bad IMO. I am not going to setup a new linux box without changing the root password, or setup a wordpress site without altering the config and locking down apache. Did you know a linux system is not 100% secure out of the box, WHAT A SHOCKER.