She explains with more detail why MongoDB(I take it for many NoSQL) is not ideal once your app starts having relationships on its data. Which probably will always happen in any application.
The use case for NoSQL storages is for unorganized data but I think that specific use case firs better for features of a webapp rather than an app itself.
I don't think my post can hold up against Mei's article but I'm flattered it reminded you of it!
Honestly, based on my limited experience with both databases, I'd use MongoDB all the time if I could. If only because it's so much easier to pick up and understand than having to query and join tables. Raw mySQL queries can get really lengthy.
Sadly, the more complex my apps get as I learn I'm going to have to bite the bullet and embrace relational databases sooner or later.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is true:
And also this:
plus the cost of duplication of data.
Your article reminds me of Sarah Mei's Why You Should Never Use MongoDB
She explains with more detail why MongoDB(I take it for many NoSQL) is not ideal once your app starts having relationships on its data. Which probably will always happen in any application.
The use case for NoSQL storages is for unorganized data but I think that specific use case firs better for features of a webapp rather than an app itself.
I don't think my post can hold up against Mei's article but I'm flattered it reminded you of it!
Honestly, based on my limited experience with both databases, I'd use MongoDB all the time if I could. If only because it's so much easier to pick up and understand than having to query and join tables. Raw mySQL queries can get really lengthy.
Sadly, the more complex my apps get as I learn I'm going to have to bite the bullet and embrace relational databases sooner or later.