News for hackers. Stuff that matters.
Re:Why you should never use MongoDB (2013) by throwanem on Monday August 15, 2016 @01:27PM (#12291882)
Not only that, they're projections which you don't have to spend effort on keeping up to date, and which the engine automatically uses to optimize your queries. While there's an argument to be made that the same can be accomplished in a non-relational database with suitable application code or a translation layer, all else equal it's better not to need those things in the first place.
Re:Why you should never use MongoDB (2013) by phamilton on Monday August 15, 2016 @02:46PM (#12292525)
And as we saw from a recent Uber post about Postgresql, that automatic updating is not actually free.
Re:Why you should never use MongoDB (2013) by throwanem on Monday August 15, 2016 @04:04PM (#12292995)
Of course it's not, but if you're not Uber, that almost certainly isn't a problem for you. When you use MongoDB, you get to roll your own indexes no matter who you are.
Re:Why you should never use MongoDB (2013) by hobs on Monday August 15, 2016 @03:55PM (#12292938)
Was going to say the same, but I realized the OP was talking about in your code, not so much as overhead.