by Hieu H
NoSQL is definitely the buzz in the database world. With such open source packages such as MongoDB and FoundationDB, it makes us NoSQL as accessible as it can get. There are still benefits to using relational databases, such as the ability to use normalization, shared data, and maturity. Some instances in which using a relational database over NoSQL are advantageous include when you’re building smaller databases that are still going to change over time, when there is so much duplicate data that you have to normalize, and when there is no cost advantage to moving away from already proven technology.
As much as I am an early adapter of new technology, the author makes some good points in favor of relational databases. Using normal SQL after a while, it becomes second nature and you normally don’t have to think about your queries. Therefore, it makes sense to use a relational database such as MySQL for smaller projects instead of having to deal with newer syntax and use cases with NoSQL. I guess the argument can be made that once you get used to NoSQL, you’d be as comfortable.
After going through the lecture and learning about the benefits of denormalization, I started to think about some of the benefits of NoSQL. Since NoSQL does not “normalize” data, it inherently reaps the benefits of denormalization. After some more thought about this, I started to wonder what would happen once the database gets enormously huge. Would the benefits of not having normalization out weight the increased database size with all that duplicate data? So then, I realized that normalization does have its place somewhere.
Finley, K., (June 9, 2011) When You Should Still Use a Relational Database Instead of NoSQL. Retrieved October 27, 2012 from http://readwrite.com/2011/06/09/when-you-should-still-use-a-re