Sql Vs. Relational Databases

956 Words4 Pages
To SQL or Not to SQL
Relational databases play a major role in making many apps and programs work. They provide an easy way to store large amounts of data in a consistent, non duplicating, and maintainable way to be used by developers for analytical or software use ("Advantages of a relational database", n.d.). However, more and more applications and companies with a tremendous amount of data such as search engines, social networks, and e-commerce sites have been requiring a level of speed and scalability that relational databases can not provide ("Why NoSQL?", n.d.). NoSQL is a name given to a quickly growing type of database known as non-relational databases, which are being used to store and manage huge amounts of structured, semi-structured, and non-structured data known as "Big Data" ("Why NoSQL?" n.d.). With the advent of social networks and apps with millions of users, the rate of growth of non-structured and semi-structured data is exponential, and the value in being able to quickly traverse it, analyze it, and use it for development is also growing quickly (McGuire, Manyika, & Chui, 2012).
Fundamentally, relational and non relational databases are very different. Relational databases generally follow the "ACID" transaction principles, while non-relational databases generally follow "BASIC" principles (Sasaki, 2015). ACID stands for atomic, consistent, isolated, durable; and prioritizes data consistency, stability, and accuracy over speed and scalability (Sasaki,
Get Access