Google Chooses SQL{5}

The article I chose this week is “Google App Engine Goes Old School With SQL Database” by Caleb Garling. Article starts off by saying that Google was one of the leaders of the NoSQL movement. However, by choosing a typical SQL server they have reaffirmed SQL’s place in technology. They implemented this on top of their App Engine as well as their “BigTable” NoSQL database. The reason behind this was that developers did not want to have to develop on BigTable due to difficulties with translating their existing relational data models over to BigTable compliant models. The article goes on to talk briefly about the difference between NoSQL and SQL databases. Starting that NoSQL databases “are meant to “scale” across vast numbers of servers so they can accommodate the mountains of data facing companies in the internet age (Garling, 2011).” Whereas SQL databases “order data into neat rows and columns – give you more ways to slice and dice your data (Garling, 2011).”  The article finishes by saying that while Google moved back towards traditional SQL, Oracle moved towards the newer NoSQL system.

I thought that it was an interesting article because it shows that SQL is here to stay for a long time and that it will most likely remain a relevant technology for many years. This article relates nicely to another article I blogged about which talked about Amazon’s NoSQL services and Oracles sudden move away from their well entrenched SQL offerings. I thought that it tied in well and that it was relevant to our class because it offered a brief tidbit of information about the difference of NoSQL and SQL data structures and server implementations.

I found the article interesting because it shows that SQL is still very much a current technology. The more I read about NoSQL and SQL the more it makes me think that the real solution to the problem is to create a backbone with NoSQL so that you have significant amounts of flexibility when it comes to implementation and storage and then have a SQL front end that allows you to easily manipulate and view the data as you want and need it.

Garling, C. (2011, 10 07). Google App Engine Goes Old School With SQL Database. Retrieved from Wired: