4 ms·

At this point I have yet to work on something that absolutely needs a NoSQL database so I may be a bit biased, but my general impression is they're a solution l

At this point I have yet to work on something that absolutely needs a NoSQL database so I may be a bit biased, but my general impression is they're a solution looking for a problem- or rather, the wrong solution to the wrong problem. I have used things like key-value stores such as memcached but it's also the kind of tools you don't use liberally unless you absolutely must. Perhaps a bit of obscurity isn't that bad of a thing after all. Doesn't help that people have been talking about the issues with NoSQL for quite a few years now [0] [0] http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-never-ever-ever-use-mongodb/ http://cryto.net/~joepie91/blog/2015/07/19/why-you-should-ne... (although I do wonder how much of these points still apply)

ohazi 7y ago
As far as i can tell, NoSQL is a reasonable way to store data that would otherwise go in a directory of files. If the lookup is anything more complicated than "I know exactly which file I want because I saved the relevant key in a real SQL database," then you're probably doing something wrong. Too many people start with NoSQL because "we gotta be cloud scale" without actually thinking about their data model, don't want to redo everything the first time they realize they need to do a join, and end up bolting on a slow, broken, inconsistent query system on top that ends up being orders of magnitude slower and more expensive than postgres running on a laptop.