Part 1 of 8 · 1 min read
Why this page comes first after data models
In this module you will
- Explain what "NoSQL" does and does not mean, and why the question "SQL or NoSQL?" is too coarse.
- List the access patterns of a feature, and use them to choose between a relational store and a NoSQL store.
- Say what is lost when joins and multi-row rules are lost, with a worked example of a money transfer.
- Estimate whether one relational node is enough for a load, and name the first steps when it is not.
- Choose a database for common interview systems and defend the choice in two sentences.
The previous page described the shapes. This page turns the shapes into a decision. In almost every interview the interviewer asks "which database, and why?". A weak answer names a product. A strong answer names the access pattern, the rules the data needs and the scale, and then picks. The numbers on this page are made up to show the idea, unless the text names a book.