Naming in tech is shit anyway. It's loaded with marketing mumbo jumbo. NoSQL should mean: No-SQL, No SQL query language, and therefore no required implementat

Naming in tech is shit anyway. It's loaded with marketing mumbo jumbo. NoSQL should mean: No-SQL, No SQL query language, and therefore no required implementations of the SQL standard (tables, relations, transactions etc). A lot of "NoSQL" databases actually include an SQL layer. Heck. CSV is NoSQL too. The transaction model is one of the things which would be nice to be able to select (eventual-consistent, non-consistent, consistent). In case you have different performance requirements. Similar to UDP vs TCP. But again, it has nothing to do with no-sql. There was a term - object database. But it was old, so it couldn't be used. Then it was document store / database. Caching and naming things are the most difficult parts. But instead of selecting a name that makes sense and reflects a system/architecture/we, we let some marketing people (read - advocates) promote a new, seo-clean, name.