News for hackers. Stuff that matters.
Re:Why you should never use MongoDB (2013) by nurettin on Monday August 15, 2016 @11:49AM (#12291206)
If you excuse the buzzword, data warehouses are built for this very reason. So you are right in the sense that cache invalidation and denormalization are problems in sql based large scale systems, but they are largely solved problems whereas in mongodb you would need to do this work manually.
Re:Why you should never use MongoDB (2013) by dozzie on Monday August 15, 2016 @12:42PM (#12291562)
> [...] data warehouses are built for this very reason. [...] [cache invalidation and denormalization] are largely solved problems [...]

Uhm, no. Data warehouse is not a database with operational (i.e. current) data, it's a database with historical data. If it is out of sync with production for a day or a week, it's totally OK, depending on its design.

So no, cache invalidation is not a solved problem there.

Re:Why you should never use MongoDB (2013) by nurettin on Tuesday August 16, 2016 @04:58AM (#12296274)
I've worked with data warehouses which were replicated like a multimaster, YMMV.
Re:Why you should never use MongoDB (2013) by herdrick on Monday August 15, 2016 @02:39PM (#12292474)
dozzie, could you remove the "Uhm, no." from that? It only adds snark to an otherwise good comment.