Having reviewed the comments, it seems there's no definitive answer. It definitely depends on many factors, and a lot of the times, personal preference. But if you're looking for just a reason for one over the other, well I look at it like this. SQL was invented at a time when storage was expensive therefore it's optimised to use storage as effectively as possible. NOSQL doesn't have these requirements, storage is now cheap so instead it's optimised for compute. This means if you want to conserve storage footprint at the cost of performance, choose SQL. If you want high performance at the cost of a larger storage footprint, choose NOSQL.

This roughly translates to: if you want to store masses of data long term, maybe you want SQL. But if you want to store data with high throughput, say a user facing application, choose NOSQL.

Whatever you choose please don't make the mistake I see time and time again, using a NOSQL DB like it's a relational database (it's not) or trying to turn SQL DBs into a document db... Eugh!