Id say the point of nosql is rather "the right tool for the job". You can use an SQL db engine as a kv-store, but you can probably make a more efficient kv-sto

Id say the point of nosql is rather "the right tool for the job". You can use an SQL db engine as a kv-store, but you can probably make a more efficient kv-store if you do not have the SQL constraints. (Oth SQL engines are pretty efficient for lots of use cases these days) Another example where SQL may not be the right choice is time series or graph DBs.