Relational vs. NoSQL: Why NoSQL?
Learn about NoSQL databases and their core philosophy.
We'll cover the following...
When building a social media app, a user profile typically consists of basic information, including name, email, and password.
However, we soon plan to add a bio, a profile picture, a list of friends, posts, comments, and likes. Then, we might add features like stories, saved items, or professional endorsements. With a traditional relational database, every one of these changes would require modifying the table structure for millions of users, a process that is slow and risky.
This is where a different kind of database started to shine, one that could handle rapidly changing data and massive scale with ease. This is the world of NoSQL, and we’re about to explore why it became so important.
By the end of this lesson, we will be able to:
Understand the key limitations of relational databases in modern applications.
Define what a NoSQL database is and its core philosophy.
Explain the main drivers for adopting NoSQL, including schema flexibility and scalability.
Describe the CAP theorem and how it represents a fundamental trade-off in distributed systems.
The world before NoSQL: A quick recap
For decades, relational databases have been the undisputed champions of data management. They provide incredible tools for ensuring data integrity through concepts such as ACID transactions, normalization, and Structured Query Language (SQL). For applications such as banking systems, e-commerce stores, and human resources software, where data consistency is critical, relational databases are ideal. Our OnlineStore database is a perfect example of a system where ...