Log-Based Brokers: Kafka's Design and Retention

This generated surface maps a learner-facing curriculum unit to its canonical source routes.

Curriculum surface

• Open learner-facing unit
• Curriculum path: content/curriculum/production/semester-08-system-design-leadership/module-03-event-driven-architecture/concepts/cluster-03-brokers-and-log-based-systems/08-log-based-brokers-kafkas-design-and-retention-primary.md
• App: production
• Semester: semester-08-system-design-leadership
• Module: module-03-event-driven-architecture
• Unit kind: concept
• Curation level: module_curated

Learning objectives

• Explain Log-Based Brokers: Kafka's Design and Retention in terms of events, temporal coupling, and consistency tradeoffs instead of diagram-first messaging vocabulary.
• Use Log-Based Brokers: Kafka's Design and Retention to predict how data, retries, ordering, and observability will behave when workflows are split across asynchronous boundaries.
• Use fundamentals-of-software-architecture, system-design-primer to connect the learner explanation to streams, event contracts, choreography, and coordination failure modes.

Prerequisites

• Comfort with service decomposition, distributed communication, and consistency tradeoffs from the earlier modules.

Source books

• fundamentals-of-software-architecture
• system-design-primer

Source routes

Fundamentals Of Software Architecture

• /books/fundamentals-of-software-architecture via Richards & Ford: Event-Driven Architecture Style, Richards & Ford: Event-Driven Ratings, Richards & Ford: Preventing Data Loss

System Design Primer

• /books/system-design-primer via System Design Primer: Asynchronism, System Design Primer: Database -- sharding and federation, System Design Primer: Database — sharding and federation

Supporting curriculum routes

No supporting curriculum routes linked yet.

External enrichment

• Confluent Event-Driven Architecture Pattern (official_docs_companion) - Anchors event-driven concepts in a concrete implementation-oriented reference instead of abstract messaging diagrams.
• Martin Fowler: Event Sourcing (optional_deep_dive) - Provides a deeper model for reasoning about event histories, replay, and asynchronous consistency.

AI companion modes

• Explain simply
• Socratic tutor
• Challenge my understanding
• Diagnose my confusion
• Connect forward / backward

Source-of-truth note

This teaching unit is learner-facing guidance assembled from multiple canonical book routes. Use the listed source books as the primary conceptual spine for Log-Based Brokers: Kafka's Design and Retention, and treat outside material as supporting enrichment only.