The shape of every section#
Every main teaching section uses the same six blocks. The labels describe ways to approach an idea, not different classes of reader.
| Block | What it is for |
|---|---|
| PLAIN — in simple words | The problem and central idea in ordinary language. |
| PLAIN — a picture in your head | An everyday comparison, followed by its explicit limits. |
| PLAIN — a worked example | Concrete records, quantities or steps that can be checked. |
| PLAIN — what is really happening inside | The actual mechanism, explained without a jump in assumed knowledge. |
| TECHNICAL — the engineer’s version | Precise vocabulary, implementation details, assumptions and source references. |
| WORDS — remember these | Each term connected to both an everyday and a technical meaning. |
Two ways to read it#
- One continuous pass. Start at Chapter 1 and read every block. The later engineering treatment grows out of the example already introduced.
- Two passes. Read the PLAIN and WORDS blocks first, then return for the TECHNICAL blocks. The browser reader provides modes for both routes. Practice and chapter summaries remain visible in either mode.
- Question-led reference. Use the contents, chapter search or glossary to locate a subject. Read the nearby assumptions before borrowing a formula, query or design pattern.
Conventions used throughout#
- Main sections have stable identifiers such as 26.4. Their six learning blocks extend that identifier, for example 26.4.5 for the engineering treatment. Chapter and section numbers stay constant across the complete edition, individual volumes and website.
- Numbered paragraphs separate ideas. An analogy includes a statement of where it breaks. The technical treatment should deepen the simple explanation rather than silently contradict it.
- A product-specific behavior is not presented as a universal database rule. PostgreSQL examples refer to the documented version; SQLite examples identify their separate implementation and tested runtime.
- A source marker such as [S25] points to the source register. Consultation dates belong to those records. Unversioned documentation can change; the included test report identifies the environment actually exercised.
- Worked shop examples are synthetic. A table of amounts is not evidence of payment settlement, real customer activity or a production incident.
- Every chapter ends with practice and worked answers, common wrong ideas, and a summary of twenty numbered entries. A summary entry may wrap onto more than one printed line.
- Code blocks may be complete executable fragments, queries requiring the stated fixture, or explicitly labeled conceptual traces. The companion-lab guide identifies the implemented exercises and their boundaries.
- A successful local test establishes only its asserted property. It is not independent review, complete security assurance or certification of a production service.
One shop, growing demands#
Mira’s Corner is a fictional stationery shop. Mira owns it and Dev helps at the counter. The canonical four agreed order lines comprise six items and 28,650 paise: O-1042 totals 17,100 and O-1043 totals 11,550. Taxes, discounts, delivery fees and settlement records are deliberately outside that initial fixture.
The later catalogue-price example does not rewrite historical agreements. The earlier expected-stock-10/observed-stock-9 discrepancy remains unexplained. Later race conditions and capstone transactions are separate demonstrations, not invented explanations of that discrepancy.
The capstone adds synthetic tenant identifiers T-A and T-B. These represent separate organizational scopes; a branch identifier is not a substitute for tenant authorization. CAP-001 is a separate order whose two notebooks and one pen happen to total the same 17,100 paise as the opening example.
Where to find things#
- Chapters 1–6 establish meaning, records, representations, measurements, identity and history.
- Chapters 7–13 develop files, databases, schemas, constraints, SQL and relationships.
- Chapters 14–20 follow queries through scans, indexes, plans, reports and performance measurements.
- Chapters 21–26 examine transactions, overlapping work, isolation, locks, versions and idempotency.
- Chapters 27–32 trace physical storage, logs, compaction, durability, backup and repair.
- Chapters 33–39 explain replication, failover, partitioning, consistency, consensus, distributed transactions, caches and queues.
- Chapters 40–46 develop pipelines, streams, analytical storage, text and vector search, and careful interpretation of results.
- Chapters 47–52 cover permissions, retention, migrations, operation, the integrated case study and the reference desk.
- The A–Z glossary, companion-lab guide and source register follow the chapters. The browser edition also offers keyword and full chapter-text search.
Edition and evidence#
This first edition contains all 52 chapters and was prepared with AI assistance for Shikhar Singh and KedByte Press. The quality report records local checks, not independent certification. The PDF fixes the layout; Word and browser pages reflow. Use stable chapter and section identifiers across formats.