Goal
The path to "失敗から学ぶRDBの正しい歩き方"
Here is the reading path leading up to this book, derived from its dependencies and ordered from the fundamentals.
The path so far (9 books)
Why read this first: With Java fundamentals in place, you move on to the Spring Framework, the de facto standard for server-side development in practice. Concepts like DI, AOP, and MVC assume a grasp of plain Java, so you layer the framework's abstractions onto your language understanding step by step.
Sources
Why read this first: After grasping how networks work, you descend to the OS layer that actually handles that communication. Linux system programming introduces the APIs—sockets, processes, file descriptors—on which servers run, bridging protocol and implementation.
Why read this first: Knowing the OS-level mechanisms for processes, I/O, and memory lets you see what Spring abstracts away under the hood. This low-level understanding keeps the framework from being a black box and pays off when diagnosing performance issues and failures.
Why read this first: Once you handle databases with Spring, the quality of the SQL and table design running behind the ORM starts to govern performance and maintainability. This book teaches the principles of relational design from a practitioner's angle, framed around the antipatterns people commonly fall into.
Sources
Why read this first: 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'.
Why read this first: 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 (失敗から学ぶRDBの正しい歩き方) covers operational anti-patterns—soft deletes, caching, idempotency—lifting your view above optimizing individual SQL statements.
Sources
Why read this first: Once you have internalized relational and normalization theory, the next stage is translating it into real table design. This Japanese book (達人に学ぶDB設計徹底指南書) 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
Why read this first: 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.
Why read this first: Where Karwin's 'SQL Antipatterns' addresses failures at the logical-design and SQL level, the Japanese book '失敗から学ぶRDBの正しい歩き方' 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