Curated Tech Reading Map
DevBookPath

Find your next tech book to read

Domain

Database Design & Operations

A learning path that builds the ability to design and operate robust, scalable data foundations — covering SQL fundamentals, relational model theory, normalization, physical design, transactions, NoSQL/distributed databases, and operational schema evolution. Travel between logical (set theory, predicate logic) and physical (disk I/O, concurrency) spaces along the way.

The Terrain of This Field

The terrain of databases can be read as a continent you climb from the "plains of SQL" at the foot, across the plateau of theory, and up to the underground of physics and the mountains of distribution. On the first plains you shed procedural thinking and shift your footing to "thinking in sets" — the entrance everyone steps through first, the starting point of every route up.

Overlooking the plains spreads the plateau of "theory and design." On the bedrock of the relational model rest the continents of normalization, logical design, and business modeling. Only once theory truly lands do your design decisions gain a backbone; by learning the right way and the anti-patterns (the failures) as two sides of one coin, you grow the ability to capture real business domains.

Beneath the plateau run the tunnels of indexes and storage engines, and beyond them rise the mountains of distributed data systems. From B-Tree to LSM-Tree — only by understanding the internals of a single node do the highest peaks of distributed consistency become solid underfoot. The key to surveying this field is the constant travel between logical and physical space.

Follow the arrows to read in order / solid = required, dashed = recommended

Share this map

Difficulty

Beginner
Intermediate
Advanced

Dependencies

Prerequisite
Recommended
Related

Computing layout...

Books in this domain

Difficulty
Reading status
Tags

23 books

Dependencies

  1. 01SQL, 2nd EditionTatsujin ni Manabu SQL Tettei Shinansho, 2nd Edition (A Thorough Guide to SQL, Learned from an Expert)Recommended / From SQL basics to applied set operations

    Reason: Once you have the basics of SELECT, the natural next step is set-oriented techniques—CASE expressions, window functions, set operations—that teach you to think in sets rather than procedurally. Both are Japanese SQL books by the same author (Mick), so the vocabulary carries over smoothly from introduction to application.

    Sources

  2. 02SQL, 2nd EditionSQL Jissen Nyumon (A Practical Introduction to SQL)Recommended / From SQL basics to execution-plan-based tuning

    Reason: After you can write correct SQL, the next lens is reading the execution plan (EXPLAIN) to understand why a query is slow. This book starts tuning from the execution plan, so reading it right after the basics grows you from 'can write SQL' to 'can write fast SQL'.

    Sources

  3. 03Tatsujin ni Manabu SQL Tettei Shinansho, 2nd Edition (A Thorough Guide to SQL, Learned from an Expert)Joe Celko's SQL for Smarties, 4th EditionRecommended / From applied SQL to advanced expressions and the nested set model

    Reason: After the applied set operations, advance to Joe Celko's set-theory-based advanced idioms and the nested-set model for hierarchical data. Including declarative hierarchical queries such as recursive CTEs, it is the capstone of the set-theoretic mindset—shedding procedural thinking entirely.

    Sources

  4. 04SQL Jissen Nyumon (A Practical Introduction to SQL)Joe Celko's SQL for Smarties, 4th EditionRelated / From tuning knowledge to advanced SQL expression

    Reason: With a tuning foundation grounded in execution plans, Celko's advanced idioms land more deeply—you grasp not just the syntax but why a given form performs well. A supplementary path for re-examining declarative complex queries such as recursive CTEs from both expressiveness and performance.

    Sources

  5. 05SQL Jissen Nyumon (A Practical Introduction to SQL)Shippai kara Manabu RDB no Tadashii Arukikata (The Right Way to Work with RDBs, Learned from Failure)Recommended / From query tuning to RDB operations overall

    Reason: Once you study query tuning and index design, you see that many performance problems trace back to early schema and operational decisions. This Japanese book on RDB pitfalls covers operational anti-patterns—soft deletes, caching, idempotency—lifting your view above optimizing individual SQL statements.

    Sources

  6. 06Tatsujin ni Manabu SQL Tettei Shinansho, 2nd Edition (A Thorough Guide to SQL, Learned from an Expert)Shippai kara Manabu RDB no Tadashii Arukikata (The Right Way to Work with RDBs, Learned from Failure)Related / From applied SQL to RDB operations knowledge

    Reason: Even when you can write applied SQL fluently, the RDB-specific pitfalls you meet in production are a separate body of knowledge. Adding the operational perspective from this Japanese book on RDB pitfalls balances the ability to write SQL with the ability to operate the database.

    Sources

  7. 07SQL, 2nd EditionRiron kara Manabu Database Jissen Nyumon (Learning Databases from Theory)Recommended / From SQL basics to internalizing relational theory

    Reason: After you can make SQL 'run', the next goal is to internalize why tables are split this way and why we normalize—grounded in relational theory. Okuno's book reconstructs Codd's relational model in practitioner's terms, giving your syntax knowledge a theoretical backbone.

    Sources

  8. 08SQL, 2nd EditionRelational Database Nyumon, 3rd Edition (An Introduction to Relational Databases)Related / From SQL basics to academic relational database theory

    Reason: A branch for those who want the relational model systematically and academically. Masunaga's textbook covers relational algebra, normal forms, and concurrency control in textbook fashion, tracing the academic lineage descending from Codd's original paper—complementing the more practice-oriented Okuno book.

    Sources

  9. 09Riron kara Manabu Database Jissen Nyumon (Learning Databases from Theory)Tatsujin ni Manabu SQL Tettei Shinansho, 2nd Edition (A Thorough Guide to SQL, Learned from an Expert)Recommended / From theoretical foundations to the logical necessity of applied SQL

    Reason: Grasping relational theory first makes the set operations and window functions in this advanced SQL guide land as the logical necessity of 'why think in sets'. Reading theory → implementation lets you derive each advanced SQL technique from first principles rather than memorizing it ad hoc.

    Sources

  10. 10Relational Database Nyumon, 3rd Edition (An Introduction to Relational Databases)Tatsujin ni Manabu SQL Tettei Shinansho, 2nd Edition (A Thorough Guide to SQL, Learned from an Expert)Related / From academic relational database theory to applied SQL

    Reason: After learning academic relational algebra and normalization theory, this path lets you verify how it is expressed in actual SQL via this advanced SQL guide. It grounds the abstractions you gained in theory into concrete query forms, converting knowledge into something usable in practice.

    Sources

  11. 11Riron kara Manabu Database Jissen Nyumon (Learning Databases from Theory)Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)Prerequisite / From theoretical foundations to practical DB design

    Reason: Once you have internalized relational and normalization theory, the next stage is translating it into real table design. This Japanese book concretizes theory—normalization, primary keys, foreign keys—into the practical steps of logical and physical design, bridging theory and practice. Hence it is placed as a required prerequisite.

    Sources

  12. 12Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)SQL Antipatterns, Volume 1Recommended / From DB design to failure cases and antipatterns

    Reason: After learning the correct design procedure, the next step is learning what not to do from cautionary examples. Bill Karwin's 'SQL Antipatterns' systematizes classic failures—missing foreign keys (Keyless Entry), EAV, comma-separated lists—reinforcing from the flip side why enforcing integrity with constraints matters.

    Sources

  13. 13Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)Jigyo Bunseki, Data Sekkei no Tame no Model Sakusei Gijutsu Nyumon (An Introduction to Modeling Techniques for Business Analysis and Data Design)Recommended / From practical DB design to advanced business modeling

    Reason: After mastering the basic DB design procedure, advance to the higher skill of mapping a real business domain into data structures. This Japanese book on business analysis and data modeling teaches techniques for extracting entities from business analysis, cultivating the judgment of 'what to model' that lies beyond technical normalization.

    Sources

  14. 14Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)System Kaihatsu, Sasshin no Tame no Data Model Taizen (The Complete Book of Data Models for System Development and Renewal)Recommended / From practical DB design to business-system-specific modeling

    Reason: After grasping general design guidelines, move to a catalog of modeling patterns specific to business systems. This Japanese data-model compendium covers proven patterns for standard domains—ordering, inventory, accounting—expanding your repertoire of reusable, battle-tested structures instead of designing from scratch each time.

    Sources

  15. 15SQL Antipatterns, Volume 1Shippai kara Manabu RDB no Tadashii Arukikata (The Right Way to Work with RDBs, Learned from Failure)Recommended / From logical anti-patterns to operational anti-patterns

    Reason: Where Karwin's 'SQL Antipatterns' addresses failures at the logical-design and SQL level, this Japanese book addresses RDB pitfalls that surface in production operation. Extending from design-time anti-patterns to operation-time ones gives a full panorama of failure patterns from design through operation.

    Sources

  16. 16Jigyo Bunseki, Data Sekkei no Tame no Model Sakusei Gijutsu Nyumon (An Introduction to Modeling Techniques for Business Analysis and Data Design)System Kaihatsu, Sasshin no Tame no Data Model Taizen (The Complete Book of Data Models for System Development and Renewal)Related / From business analysis models to business system implementation patterns

    Reason: After learning the 'how to think' of deriving entities from business analysis, you can consult many concrete model examples in the data-model compendium as its output. Moving back and forth between abstract modeling technique and concrete per-domain table structures makes your design repertoire three-dimensional—a parallel-reference relationship.

    Sources

  17. 17System Kaihatsu, Sasshin no Tame no Data Model Taizen (The Complete Book of Data Models for System Development and Renewal)Designing Data-Intensive ApplicationsRelated / From business modeling to distributed data systems

    Reason: Once you master business modeling on a single RDB, you hit the question of how design changes when data becomes distributed and large-scale. Kleppmann's 'Designing Data-Intensive Applications' covers replication, partitioning, and consistency models across the board, serving as the starting point for extending modeling knowledge into distributed environments.

    Sources

  18. 18Tatsujin ni Manabu SQL Tettei Shinansho, 2nd Edition (A Thorough Guide to SQL, Learned from an Expert)SQL Performance ExplainedRecommended / From applied SQL to the internal structure of indexes

    Reason: Once you can write applied SQL, you want to understand why a query is fast or slow from the internal structure of indexes. Markus Winand's 'SQL Performance Explained' builds index design up from how B-Trees work, connecting the way you write SQL with how fast it runs.

    Sources

  19. 19SQL Jissen Nyumon (A Practical Introduction to SQL)SQL Performance ExplainedRecommended / From execution plan basics to indexes in depth

    Reason: After learning to read execution plans in the practical intro, dig deeper into the internal structure of indexes themselves with Winand's 'SQL Performance Explained'. Understanding index structure clarifies why a plan chooses a given access path, raising the resolution of your tuning.

    Sources

  20. 20SQL Performance ExplainedPostgreSQL Tettei Nyumon, 4th Edition (A Thorough Introduction to PostgreSQL)Recommended / From abstract DB theory to concrete RDBMS implementation

    Reason: After grasping RDBMS-agnostic index theory in 'SQL Performance Explained', verify how it is implemented in a concrete product via the Japanese PostgreSQL book. Touching PostgreSQL-specific index types—B-Tree, GiST, GIN, BRIN—and transaction mechanisms lands the abstract theory onto a concrete implementation.

    Sources

  21. 21Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)SQL Performance ExplainedRelated / From logical design to understanding the impact of physical design

    Reason: After learning normalization-centric logical design, this is a supplementary path to understanding how that design rebounds on physical performance. Reading Winand's 'SQL Performance Explained' reveals how table design and key choices govern index efficiency, giving physical grounding to your logical-design decisions.

    Sources

  22. 22PostgreSQL Tettei Nyumon, 4th Edition (A Thorough Introduction to PostgreSQL)Designing Data-Intensive ApplicationsRelated / From PostgreSQL internals to distributed systems design

    Reason: Once you understand operating and transactions on a single RDBMS (PostgreSQL), step into the distributed world of what breaks when you scale to multiple nodes. Kleppmann's 'Designing Data-Intensive Applications' covers replication and consistency trade-offs, bridging single-node operational knowledge into distributed design.

    Sources

  23. 23SQL Performance ExplainedDatabase InternalsRecommended / From B-Trees to LSM-Trees and storage engines in depth

    Reason: After understanding the internals of B-Tree indexes in 'SQL Performance Explained', broaden your view with Alex Petrov's 'Database Internals' to the LSM-Trees and various storage engines beyond the B-Tree. Comparing data structures with different read/write characteristics cultivates judgment for choosing a database engine.

    Sources

  24. 24PostgreSQL Tettei Nyumon, 4th Edition (A Thorough Introduction to PostgreSQL)Database InternalsRecommended / From RDBMS implementation to general storage engine theory

    Reason: Once you understand one concrete RDBMS implementation (PostgreSQL), you want a map to put it in perspective. Petrov's 'Database Internals' systematizes storage engines and distributed implementations across products, letting you grasp where 'this PostgreSQL mechanism' sits in the general picture.

    Sources

  25. 25Database InternalsDesigning Data-Intensive ApplicationsPrerequisite / From storage internals to the principles of distributed data systems

    Reason: Only after understanding single-node storage-engine internals do discussions of consistency, replication, and partitioning across multiple nodes become grounded. Kleppmann's 'Designing Data-Intensive Applications' is the capstone that systematizes the principles of distributed data systems, placing internals knowledge as a required prerequisite.

    Sources

  26. 26Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)Data-Oriented ProgrammingRelated / From database design to immutable data-driven architecture

    Reason: Studying RDB table design naturally extends interest to how data is represented on the application side. Yehonathan Sharvit's 'Data-Oriented Programming' advocates treating data as immutable generic structures, offering a view that connects the database's normalization mindset with application-side data modeling.

    Sources

  27. 27Data-Oriented ProgrammingDesigning Data-Intensive ApplicationsRelated / From immutable data design to distributed data systems

    Reason: The mindset of treating data as immutable connects deeply with how distributed systems handle consistency and event history. Kleppmann's 'Designing Data-Intensive Applications' covers log-centric architectures and event sourcing, extending the immutable-data idea into the context of distributed infrastructure.

    Sources

  28. 28PostgreSQL Tettei Nyumon, 4th Edition (A Thorough Introduction to PostgreSQL)Database Reliability EngineeringRecommended / From RDBMS operations basics to DB operations with SRE principles

    Reason: After covering the operational basics of PostgreSQL—backups, monitoring, transactions—the next stage is elevating them into organized, systematic operational discipline. 'Database Reliability Engineering' (by Laine Campbell and Charity Majors) applies the SRE principles systematized by Google to database operations, moving you from ad-hoc operations to SLO-based reliability design.

    Sources

  29. 29Database InternalsDatabase Reliability EngineeringRecommended / From storage internals to production operations

    Reason: Understanding the internals of storage engines and replication lets you predict, from structure, what to monitor and what can break in production. 'Database Reliability Engineering' bridges that internal knowledge into operational design—capacity planning, incident response, data integrity.

    Sources

  30. 30Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)Refactoring DatabasesRecommended / From DB design to continuous schema evolution

    Reason: Database design is not build-once-and-done; it must evolve continuously as the application changes. Ambler & Sadalage's 'Refactoring Databases' systematizes techniques for safely changing schemas, connecting initial-design knowledge to evolutionary design that keeps fixing the schema while in operation.

    Sources

  31. 31SQL Antipatterns, Volume 1Refactoring DatabasesRelated / From avoiding antipatterns to evolutionary refactoring

    Reason: Once Karwin's 'SQL Antipatterns' lets you spot bad designs already baked in, you next need a safe way to fix them. 'Refactoring Databases' offers a catalog of patterns for incrementally improving a schema while preserving production data, joining the discovery of anti-patterns to their remediation end to end.

    Sources

  32. 32Database Reliability EngineeringRefactoring DatabasesRelated / From SRE principles to schema evolution techniques

    Reason: After learning the principles of 'don't break it' operations in 'Database Reliability Engineering', the question becomes how to uphold them when you actually change the schema. The zero-downtime migration techniques in 'Refactoring Databases' form a parallel reference that translates SRE-style reliability goals into concrete schema-change procedures.

    Sources

  33. 33Designing Data-Intensive ApplicationsDatabase Reliability EngineeringRelated / From distributed data system design to running it in production

    Reason: After understanding the theoretical trade-offs of distributed systems in Kleppmann's 'Designing Data-Intensive Applications', step into the reality of keeping them running. Based on Google's SRE principles, 'Database Reliability Engineering' (by Laine Campbell and Charity Majors) provides concrete practices for operating distributed data infrastructure reliably in production.

    Sources

  34. 34Riron kara Manabu Database Jissen Nyumon (Learning Databases from Theory)SQL Antipatterns, Volume 1Related / From theoretical grounding to avoiding anti-patterns

    Reason: Understanding the relational model and normalization theory lets you read each failure in Karwin's 'SQL Antipatterns' through the lens of 'which theoretical principle it violates'. Knowing the theory lets you judge why an anti-pattern is bad from first principles, turning it into transferable knowledge rather than memorization.

    Sources

  35. 35Joe Celko's SQL for Smarties, 4th EditionDatabase InternalsRelated / From advanced SQL expressions to physical storage internals

    Reason: Pushing Celko's set-theoretic advanced SQL to its limits sparks interest in how those declarative queries are executed and stored internally. Learning storage engines and index implementations in Petrov's 'Database Internals' bridges the gap between SQL's declarations and their physical execution.

    Sources

  36. 36Relational Database Nyumon, 3rd Edition (An Introduction to Relational Databases)Riron kara Manabu Database Jissen Nyumon (Learning Databases from Theory)Related / From academic relational database theory to a practice-oriented theory book

    Reason: After grasping relational algebra and normal forms academically in Masunaga's textbook, verify in Okuno's more practice-oriented book how that theory informs real SQL and design decisions. It connects academic rigor with field practicality, turning theory into 'usable knowledge'.

    Sources

  37. 37SQL, 2nd EditionYasashii Database Sekkei (A Gentle Guide to Database Design)Recommended / From SQL basics to DB design with requirements definition built in

    Reason: After learning basic SQL operations such as SELECT and JOIN, the natural next step is the upstream question of how to design the tables themselves. This book walks through requirements definition, logical design, physical design, and operations in one pass, giving concrete guidance at each stage where a reader new to DB design tends to stumble.

    Sources

  38. 38Yasashii Database Sekkei (A Gentle Guide to Database Design)Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)Recommended / From design process basics to criteria for normalization trade-offs

    Reason: After going through the design process from requirements to operations once, you will want to dig into the judgment criteria for choosing between normalization and denormalization. 'DB Design Mastery Guide' covers the conversion process from logical to physical design along with its trade-offs, letting you relearn each stage touched on in the beginner book with concrete decision criteria.

    Sources

  39. 39PostgreSQL Tettei Nyumon, 4th Edition (A Thorough Introduction to PostgreSQL)PostgreSQL Jissen Nyumon (A Practical Introduction to PostgreSQL)Recommended / From understanding internals to production operations in practice

    Reason: After understanding PostgreSQL's internal implementation—MVCC, shared buffers—the next step is putting that knowledge to work in actual production operations. This book covers replication, backup/restore, permission management, authentication and encryption, monitoring, and performance tuning, connecting internals knowledge to concrete operational procedures.

    Sources

  40. 40PostgreSQL Jissen Nyumon (A Practical Introduction to PostgreSQL)Database Reliability EngineeringRecommended / From PostgreSQL operations to reliability design with SRE principles

    Reason: After acquiring hands-on operational procedures for a single product—replication, backup/restore, monitoring, performance tuning—you will want to place them within an organizational reliability framework. 'Database Reliability Engineering' covers SLO-based risk management and zero-downtime migration, offering a lens to re-situate individual operational techniques within SRE principles.

    Sources

  41. 41Tatsujin ni Manabu SQL Tettei Shinansho, 2nd Edition (A Thorough Guide to SQL, Learned from an Expert)Jissen dbt Nyumon (A Practical Introduction to dbt)Recommended / From applied SQL to operating transformation pipelines with dbt

    Reason: Once you can wield SQL as a set-oriented language—CASE expressions, window functions, self-joins—the next step is learning how to assemble that SQL into a production data-transformation pipeline. This book covers running models in dbt, structuring a project, and generating tests and documentation, connecting applied SQL knowledge to the practical operation of an analytics platform.

    Sources

  42. 42Tatsujin ni Manabu DB Sekkei Tettei Shinansho, 2nd Edition (A Thorough Guide to DB Design, Learned from an Expert)Jissen dbt Nyumon (A Practical Introduction to dbt)Related / From table design criteria to model structure for analytics platforms

    Reason: After learning the normalization/denormalization trade-offs from a table-design perspective, you may want to try applying that same judgment to how you structure models on the analytics side. This book covers project structuring and model execution in dbt, offering a supplementary path for carrying the structuring mindset gained from DB design over into building analytics data models.

    Sources

  43. 43Database Design for Mere Mortals, 4th EditionSQL Queries for Mere Mortals, 4th EditionRecommended / From designing tables to querying them

    Reason: SQL Queries for Mere Mortals begins by checking that the database structure is sound, in its second chapter, before any query is written. Having worked through tables, keys and relationships as a design process first, you can read the join and subquery chapters knowing why the tables connect the way they do. Both books belong to the For Mere Mortals series and neither depends on a particular database product.

    Sources

  44. 44Database Design for Mere Mortals, 4th EditionSQL Antipatterns, Volume 1Recommended / From a design method to the designs that go wrong

    Reason: Database Design for Mere Mortals teaches a sequence for settling keys, field specifications, relationships and business rules, and spends one late chapter on bad design. With that sequence in hand, many of the schema-design antipatterns in SQL Antipatterns can be read as what happens when one of those steps is skipped or misapplied.

    Sources

  45. 45SQL Queries for Mere Mortals, 4th EditionSQL Performance ExplainedRecommended / From writing correct queries to making them fast

    Reason: SQL Queries for Mere Mortals concentrates on how to express SELECT, joins, subqueries and grouping in standard SQL. Once writing a WHERE clause or a join no longer takes thought, SQL Performance Explained picks up the next question about those same clauses: how they use an index.

    Sources

  46. 46SQL Queries for Mere Mortals, 4th EditionJoe Celko's SQL for Smarties, 4th EditionRelated / From standard SQL basics to advanced SQL programming

    Reason: SQL Queries for Mere Mortals introduces thinking in sets in its seventh chapter and ends with harder problems built on CASE and unlinked tables; the fourth edition also adds a chapter on window functions. For a reader who can work through all of that and wants to push set-oriented SQL further, Joe Celko's SQL for Smarties is the next book.

    Sources

Explore next

View the full mapBrowse all fields