Apache Kafka for Java & Spring Boot Developers: Curriculum Blueprint

Phase 1 (blueprint only). No article content is generated until you approve this blueprint. This document defines the full course shape: audience, design principles, the section-by-section table of contents with permalinks and per-module scope, the running scenario, the file layout, and the scaffolding changes. It is comprehensive but non-redundant: each concept lives on exactly one page and is cross-linked from everywhere else.

The companion documents are:


Design principles


Full Table of Contents (10 sections)

flowchart TD
    s0[0. Kafka and Messaging Foundations]
    s1[1. Architecture and Internals]
    s2[2. Local Lab and Setup]
    s3[3. Building with Spring for Apache Kafka]
    s4[4. Schema Management]
    s5[5. Reliability and Delivery Semantics]
    s6[6. Event-Driven Architecture and Advanced Patterns]
    s7[7. Production Readiness]
    s8[8. Operations and Troubleshooting]
    s9[9. Capstone and Assessment]
    s0 --> s1 --> s2 --> s3 --> s4 --> s5 --> s6 --> s7 --> s8 --> s9

Sections 0 to 6 build the developer skill set from beginner to advanced. Section 7 hardens for production. Section 8 is the standalone operations and troubleshooting reference. Section 9 ties everything together.


Section 0: Kafka and Messaging Foundations (beginner on-ramp)

Section 1: Architecture and Internals

Section 2: Local Lab and Setup

Section 3: Building with Spring for Apache Kafka

Section 4: Schema Management

Section 5: Reliability and Delivery Semantics

Section 6: Event-Driven Architecture and Advanced Patterns

Section 7: Production Readiness

Section 8: Operations and Troubleshooting (standalone section, PROD focus)

Section 9: Capstone and Assessment


Running scenario

A four-service event-driven system used consistently in examples, diagrams, and the capstone:

Topic keys are order id or customer id depending on the ordering requirement, which is used to teach partitioning and ordering concretely.


File-by-file layout

All content is new; nothing is migrated. Files live under _courses/kafka/:

Routing uses front-matter permalink, and cross-links use permalinks, so file prefixes are for ordering only and are safe to adjust.


Scaffolding changes


Phase 2 (await approval)

On approval, generate files sequentially, one module at a time, each with its Mermaid diagram(s), realistic Order/Payment/Inventory/Notification Spring Boot code, prerequisites, guided practical, cross-links, and checkpoint, updating the nav YAML and index as we go. Order of build is defined in release/kafka/implementation-plan.md, and every module is generated with release/kafka/generation-prompt.md to hold the quality bar constant.