My heuristics is far simpler:
1) In case you know how your data and access patterns -short: you know what you are doing- NoSQL might be a good idea*
2) Otherwise: SQL should work well for you.
*But having JSON and Array Types in traditional relational databases are limiting the need for NoSQL.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
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.
My heuristics is far simpler:
1) In case you know how your data and access patterns -short: you know what you are doing- NoSQL might be a good idea*
2) Otherwise: SQL should work well for you.
*But having JSON and Array Types in traditional relational databases are limiting the need for NoSQL.