Goal
The path to "データベースリライアビリティエンジニアリング"
Here is the reading path leading up to this book, derived from its dependencies and ordered from the fundamentals.
The path so far (5 books)
Why read this first: 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.
Why read this first: 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.
Why read this first: After grasping RDBMS-agnostic index theory in 'SQL Performance Explained', verify how it is implemented in a concrete product via the Japanese PostgreSQL book (PostgreSQL徹底入門). Touching PostgreSQL-specific index types—B-Tree, GiST, GIN, BRIN—and transaction mechanisms lands the abstract theory onto a concrete implementation.
Why read this first: 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.
Why read this first: 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.