Chapter Eleven · Choosing
Choosing and What's Next
Ten chapters of tables, queries, guarantees, and families converge on one working skill: given a project, choose its database with reasons attached. This chapter hands you the four-question framework and drills it on real scenarios, gives honest portraits of the five engines you'll actually hear named, and explains the OLTP/OLAP split that accounts for a whole second industry. Then the last page tells you plainly what you can do now, what was left out on purpose, and where each missing piece lives.
Back in Chapter 1, Lora chose a database without knowing she was choosing: the Marquee's data was tables-shaped, the questions crossed those tables freely, and seat G7 could never be sold twice — so relational fit, and everything after followed from that fit. This chapter turns her accident into your method. The choice becomes four questions you can ask about any project, plus one prior that has quietly run the whole book: relational by default, something else when a specific answer says so.
Around the framework sit three pieces of context every working conversation assumes. The engine names — PostgreSQL, MySQL, SQLite, SQL Server, Oracle — get one honest paragraph each, because job postings speak in those names and the differences matter less than the folklore claims. The split between databases that run the business and databases that analyze it gets its own page, because "should this query run on the till?" is a question the reader can now answer. And the final page closes the book the way it opened: honestly, with a map.