Encryptor's comments

Picture this: an 11 ton tank of gas falls into your house and burns it to the ground, and all you're told is: "There are too many factors, you have to remember we're basically talking [about] the air resistance of a possibly tumbling abstract shape that [was] tumbling rather chaotically [when] any appreciable atmospheric effects [were taking] place. And that's just the start".

Why the hell is "falling stuff from the sky" the new "terror"? Can we please not launch shit into space without knowing where it'll fall? I know it's hard, but it's not impossibru!

in 14 lines of ... python?? really? Ok, I can do better. A Regular Expression Engine in 1 line of Javascript: string.match();

This is textbook projecting. The team deployed an immature database and tried to push its limits, and now they're saying: "it sucks!". Sure, a 2 year-old database is the problem, not your ability to make architectural decisions. Sounds like someone is looking for a scapegoat. They took a risk and failed and this is just a poor way of coping with it. It's OK to publish your experiences on your blog (which they did a few days ago). It's NOT OK to go around the Internets publishing "anonymous" articles about how MongoDB sucked for you, as if no one will see what you did there. That's just defamation, folks.

On a side note, we also looked at MongoDB and, after running a few tests, we concluded that it is a glorified key-value pair storage. That said, we did use it in a few small-scale projects and it works great.

The bottom line: choose the right tool for the job and don't bitch about the tools when you fail.