The article is, IMO, total crap. There are advantages to NoSQL in some cases. I am even happy to write about them. However, they are not really the advantage

The article is, IMO, total crap. There are advantages to NoSQL in some cases. I am even happy to write about them. However, they are not really the advantages listed here. The first is that SQL databases can in fact be distributed in some cases. Look at Postgres-XC for an example of write-scalable distributed shards while maintaining a consistent, relational model. The second is the focus on analytics. NoSQL analytics is very much of a problematic area. Doing the analysis typically requires very intensive searches of the entire data, and NoSQL databases are not optimized for this. Consequently analytical data tends to be slow to build and then maintained on data input, rather than generated ad hoc from existing data (using the entered data as a single point of truth). This leads to a lack of flexibility even though prepared reports load quickly. It isn't clear to me how different this would be from summary tables maintained with triggers. Now NoSQL has some advantages: 1) Where you don't need ad hoc analytics, where you have highly defined functional requirements, and where you have well defined network protocols for interop, development is often faster, and performance is better. 2) I think it could be very interesting as a network transparent back-plane if you will for various kinds of network services.