Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added NoSQL callout (#343) #369

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions episodes/00-sql-introduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -178,6 +178,16 @@ To summarize:
- Split into separate tables with one table per class of information
- Needs an identifier in common between tables – shared column - to
reconnect (known as a *foreign key*).

::::::::::::::::::::::::::::::::::::::::: callout

### SQL vs. NoSQL

SQL is not the only tool for managing and analyzing large amounts of data. As described above, SQL databases store data in tables using a rigid schema. This works well for many applications, but larger, more complex projects may benefit from the more flexible approach provided by NoSQL databases.

NoSQL databases are diverse, employing a variety of data structures tailored to specific use cases, but in general provide a scalable way to store, search, and establish relationships within large datasets that cannot easily be represented by a rigid, tabular schema. A more thorough discussion of the differences between SQL and NoSQL is beyond the scope of this lesson, but curious readers can start with [this comparison](https://www.mongodb.com/nosql-explained/nosql-vs-sql) by MongoDB, a NoSQL database vendor.

::::::::::::::::::::::::::::::::::::::::::::::::::

### Import

Expand Down