@@ -181,9 +181,28 @@ To summarize:
181181 containing parts we might want to work with separately.
182182- One field per type of information
183183- No redundant information
184- - Split into separate tables with one table per class of information
185- - Needs an identifier in common between tables – a shared column - to
186- reconnect the information (known as a * foreign key* constraint).
184+ - Split into separate tables with one table per class of information
185+ - Needs an identifier in common between tables – a shared column - to
186+ reconnect data (known as a * foreign key* ).
187+
188+ ::::::::::::::::::::::::::::::::::::::::: callout
189+
190+ ### SQL vs. NoSQL
191+
192+ SQL is not the only tool for managing and analyzing large amounts of data.
193+ As described above, SQL databases store data in tables using a rigid schema.
194+ This works well for many applications, but larger, more complex projects may
195+ benefit from the more flexible approach provided by NoSQL databases. A common application for NoSQL databases is storing documents and files.
196+
197+ NoSQL databases are diverse, employing a variety of data structures tailored
198+ to specific use cases, but in general provide a scalable way to store, search,
199+ and establish relationships within large datasets that cannot easily be
200+ represented by a rigid, tabular schema.
201+ A more thorough discussion of the differences between SQL and NoSQL
202+ is beyond the scope of this lesson, but curious readers can start with
203+ [ this comparison] ( https://www.mongodb.com/nosql-explained/nosql-vs-sql ) by MongoDB, a NoSQL database vendor.
204+
205+ ::::::::::::::::::::::::::::::::::::::::::::::::::
187206
188207### Import
189208
0 commit comments