There's also additional considerations that weren't touched in the article, and they're not functional but architectural.

Sometimes you have payloads that can't fit in a traditional RDBMS, and SQL/Relational don't cluster/shard well.

NoSQL bring convenient clustering/sharding to your data. Anecdote: an old team chose Cassandra solely for its admin-tools (which are really cool), even if we didn't actually need a NoSQL; I lost that battle, but I least we all learned something.