Skip to main content
Databaseschapter 1 of 5 · 4 lessons

SQL vs NoSQL

Choose based on access patterns, consistency needs, and query complexity, not hype.

A team picks a database on a Tuesday afternoon, in about twenty minutes, mostly by asking which one people liked at their last job. Two years later that twenty minutes is the reason a reporting feature takes a quarter.

The choice deserves better, and it is not actually hard. It comes down to three questions with boring answers: what are the queries you will run most, how many writes per second do they add up to, and what should happen when two of them touch the same row at the same moment. Answer those and the database picks itself.

Lessons

4 in this chapter
  1. What Relational Buys YouSchemas, transactions, and joins are features you miss most the day after you give them up.3 min
  2. The NoSQL FamiliesNoSQL is not one thing. It is six different tools sharing a marketing label.3 min
  3. How to Actually ChooseWrite down your top five queries first. The database falls out of the list.2 min
  4. Polyglot PersistenceMost real systems run two or three stores, with exactly one of them holding the truth.3 min