MySQL Discovers A Need For A Defense{3}


I read an interesting article about what was better for a business that has a high volume of data; MySQL or NoSQL. In order to really understand it I looked up what NoSQL is. Essentially, NoSQL is a type of database management system that is not built on tables and does not use a structured query language. This article specifically talked about the advantages of MySQL verses the new NoSQL. In the typical ER model, the architectural structure is limited. This causes concerns with large inflow of data. It isn’t unmanageable, just an apprehension. NoSQL was designed to manage these large inflows of data better and faster. PayPal uses MySQL because of the architectural benefits. They had to think about how to build the system to accommodate for large amounts of users. “The approach they used, called architectural tiling, was designed to ‘build a system that scales to an arbitrary number of users. And [they] did that with SQL,'”(Jackson, 2012). MySQL is used in many businesses because of familiarity and data security. It is also used as a “building block — use it as a really strong core of features that we understand, and build solutions on top of that core”(Jackson, 2012).

I found this article to be related to our class discussions because it shows that the entity relationship model is very important. Even though it may have some restraints, it has undeniable in what it offers for large companies and handling big data. The Enhanced ER Model is a backbone for PayPal, as mentioned in the article. It gives the data security that NoSQL does not.

I believe that the enhanced ER model will be around for quite some time. Although it may become dated  there will always be updates and people who understand the core. I found this article to be very interesting. People are trying new things and some may find it an advantage. Others are still using the same old technology, but improving it as the business grows.

 

Jackson, J. (2012, September 30). http://www.computerworld.com/s/article/9231884/MySQL_users_caution_against_NoSQL_fad?taxonomyId=173&pageNumber=1. Retrieved October 13, 2012