NOSQL DATA MODELLING
From the book I Am Datapedia!, published here free by the author.
Part of I Am Datapedia!
Questions 1–10 of 10
1. What primarily drives NoSQL data modelling, in contrast to relational modelling?
2. Which four database families does NoSQL data modelling cover?
3. Why are NoSQL models often intentionally denormalised or embedded?
4. Which questions guide NoSQL design decisions?
5. In a document database such as MongoDB, how might the loan approval domain be modelled?
6. In a key–value database such as Redis or DynamoDB, what would the loan example use as key and value?
7. Which NoSQL family is described as partitioning data by CustomerID to support high write throughput and distributed scalability?
8. Why does strict normalisation become a problem in massively distributed systems?
9. Which of the following is NOT a claim made about the relationship between NoSQL and relational systems?
10. In the example of a single organisation using several database types, which workload is matched with a graph database?