Re:MongoDB queries don’t always return all matching documents
by badthingfactory on Wednesday June 08, 2016 @08:29AM
(#11861737)
It's pretty easy to use... until you have to normalize data and query across one or two joins. I've been forced to build with mongo for the past few months (still not sure why) and I can't think of a single valid use-case for this rubbish.
If you need denormalized/distributed caching, Redis does a good job.
If you need to store some unstructured json blobs, postgres and now sql server 2016 can do that.
If you need reliable syncing for offline capable apps, you probably want CouchDB.
If you need real time, use Rethink
Obviously, relational data belongs in a relational database.
I think the problem is that all of these databases do one or two things really well. Mongo tries to do all of these things, and does so very poorly.
If you need denormalized/distributed caching, Redis does a good job. If you need to store some unstructured json blobs, postgres and now sql server 2016 can do that. If you need reliable syncing for offline capable apps, you probably want CouchDB. If you need real time, use Rethink Obviously, relational data belongs in a relational database.
I think the problem is that all of these databases do one or two things really well. Mongo tries to do all of these things, and does so very poorly.