Comments on: One size does not fit all: “document stores”, “nosql databases” , ODBMSs. http://www.odbms.org/blog/2010/02/document-stores-nosql-databases-odbmss/ Trends and Information on Big Data, New Data Management Technologies, Data Science and Innovation. Mon, 03 Nov 2014 17:39:20 +0000 hourly 1 http://wordpress.org/?v=4.2.4 By: Aeomer http://www.odbms.org/blog/2010/02/document-stores-nosql-databases-odbmss/#comment-101 Tue, 02 Apr 2013 12:31:52 +0000 http://www.odbms.org/odbmsblog/2010/02/08/document-stores-nosql-databases-odbmss/#comment-101 PostgreSQL supported key/value stores whiles most NoSQL devs were in diapers. (See hstore) The problems of data stores that do not need SQL like interrogation or consistency is well understood *and* already solved – NoSQL is not new, but certain storage requirements (web distributed storage) makes them more relevant now.
The primary reason given for the whole array of NoSQL solutions (speed and no need for query languages) is secondary to the better reason – simple scaling of data storage that does not require immediate consistency. The nature of consistency means RDBMS are more complex when scaled, not that they don’t scale. Saying RDBMS don’t scale is just drinking the NoSQL CoolAid. NoSQL is easier to scale because it has no interest in immediate consistency. Add ACID requirements into the mix and NoSQL can’t cope – but remember it does not need to as the problems it solves are different.

One size certainly does not fit all, but always remember that an ACID compliant RDBMS can do all things NoSQL can do, but the opposite it not true. Your choice is all about overhead.

On another point, let’s stop using the term NoSQL and call it what it is – NoQL.
Using the term NoSQL is marketing bias, not technical reality.

]]>