The marketing term NoSQL, which was the hippest buzzword just a few years back, is slowly becoming a synonym for a defect.' They tweeted this from their latest AWS re:Invent conference: SQL on the relational schema is orders of magnitude faster than JSON processing. Moreover Amazon is not afraid to point out a few advantages when it comes to using SQL and the relational model. Why you should pick strong consistency, whenever possible. This time a new article by Google further forwards an argument that Google initiated years ago: in the original Spanner paper (2012) Google said that strong consistency-like that offered by SQL databases-causes fewer problems than the eventual consistency model that is often employed by NoSQL systems. Google’s shift towards SQL was already mentioned in my previous newsletter. Perhaps an SQL datapoint from today's Reddit programming news: See this discussion about Google's TensorFlow language evaluation: Towards what is probably still being worked out.Īre 20 languages viable? Don't see why not. The shift away from MS/desktop dominance should be good for language diversity, since that means a shift away from MS's languages (C#, VB.NET, C++). See the differences yourself, particularly as you get up in the multi-core range:

(Source: )Īlthough Amazon is agnostic about what you run on your AWS instances, pricing considerations mean that in practice people tend to run Linux. AWS represents more than 3 times the cloud business of the next 3 competitors (MS, IBM, Google). I would suggest it has more to do with the decline in desktop app development (Windows) and the shift to cloud-based development (Linux, AWS).

Easysql detect safe browsing