A brief background on NoSQL and Relational Databases{2}


The article that I chose to blog about this week is “Amazon goes back to the future with ‘NoSQL’ Database” by Caleb Garling. The article starts by saying that Amazon was one of the first companies to back the NoSQL movement. It says that NoSQL was started as a way to improve storage of unstructured data. They talk about Amazon’s web services and database offerings such as DynamoDB. The article states that “NoSQL databases are a response to traditional relational database such as Oracle and MySQL. (Garling, 2012)” It then goes on to talk about how relational databases are setup. They say that “relational databases store information in neat rows and columns, typically, on a single server.  NoSQL databases are designed to store data across a wide array of machines. (Garling, 2012)”  The authors then go on to talk about how there have been a number of open source NoSQL projects to take shape in the success of projects such as DynamoDB. The article even talks about Oracle releasing their own version of a NoSQL database. They go on to talk about how Amazon has built their NoSQL database and how they have made it scale up or down as required by their customers. However, the article ends by saying that “NoSQL isn’t for everyone.” It talks very briefly about some downsides such as skill requirements or having to rely on another company to provide the database service for you.

I picked this article because it was talking about both relational databases and NoSQL databases. It seemed like a good topic to talk about even though a lot of other people have blogged about NoSQL because it provides a little bit of comparison between the two systems without actually saying that one is better than the other. I thought it was related to this week’s topic because it talked about the ways both database systems are setup and their differences with each other.

I liked the article, however I wish that it had gone a more in depth about in its comparison with traditional relational databases and NoSQL databases instead of the brief paragraph that it had. I think that it is interesting to see the change in technology and the need for different forms of databases. Especially since it depends on what you are doing with the data your company is collecting and the type of data that it is.

Garling, C. (2012, 01 19). Amazon Goes Back to the Future With ‘NoSQL’ Database. Retrieved from Wired: http://www.wired.com/wiredenterprise/2012/01/amazon-dynamodb/