Chapter 1 — Further Reading

Optional, but rewarding. You don't need any of this to continue — Chapter 2 stands on its own. These pointers are for when you want history, depth, or a second voice. Items are tagged by learning path where one benefits most.

The foundational paper (🔬 CS Student)

  • E. F. Codd, "A Relational Model of Data for Large Shared Data Banks" (1970). The paper that started it all — astonishingly readable for a 50-year-old research paper, and a short one. Read at least the opening pages to see how radical "ask for data by what, not how" was at the time. Freely available online (ACM and many mirrors).
  • C. J. Date, An Introduction to Database Systems. The classic, rigorous treatment of relational theory. Heavy, but the gold standard if you want the mathematics done properly.

Modern, practical perspective (💻 Developer · 🏗️ DBA)

  • Martin Kleppmann, Designing Data-Intensive Applications (O'Reilly). The single best modern book on how data systems work — relational, NoSQL, distributed, and everything between. We'll reference it again in Parts IV and VI. If you buy one supplementary book for your whole career, make it this one. (Chapter 1 of Kleppmann pairs beautifully with this chapter.)
  • The PostgreSQL official documentation — Preface and "Part I: Tutorial." Genuinely excellent, free, and authoritative. Start at https://www.postgresql.org/docs/current/. Bookmark it; you'll return constantly.

The big-picture / academic standards (🔬 CS Student)

  • Ramakrishnan & Gehrke, Database Management Systems. A standard university textbook; rigorous coverage of theory and internals. A good library reference.
  • Silberschatz, Korth & Sudarshan, Database System Concepts. Another well-regarded course text, often the assigned book for university database courses.

On SQL as a language (📊 Analyst · 💻 Developer)

  • Alan Beaulieu, Learning SQL (O'Reilly). A focused, friendly introduction to SQL the language. A nice companion to Part II of this book.
  • Markus Winand, Use the Index, Luke! (https://use-the-index-luke.com/). Free online; the clearest explanation anywhere of how indexes make queries fast. Save it for Chapter 23, but know it exists.

History and culture (everyone)

  • "The History of Databases" overviews — search out a reputable timeline of hierarchical → network → relational → NoSQL → NewSQL. Understanding the lineage makes the present landscape far less confusing.
  • The annual Stack Overflow Developer Survey (database section) — a quick read on what practitioners actually use and admire. PostgreSQL's consistent showing is the data behind this book's tool choice.

To do, not just read

  • Skim, don't study, the PostgreSQL docs' table of contents. Seeing the shape of what a database can do — types, functions, indexes, replication — gives you a map for the journey ahead.
  • Keep your project-notes.md open. The best "further reading" for this chapter is your own thinking about the system you chose to build. Add to your list of questions whenever one occurs to you.

Next: Chapter 2 — Setting Up PostgreSQL, where the reading stops and the doing begins.