Events vs Commands vs Requests

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-01-events-as-a-mental-model/02-events-vs-commands-vs-requests-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 Events vs Commands vs Requests in terms of events, temporal coupling, and consistency tradeoffs instead of diagram-first messaging vocabulary.
• Use Events vs Commands vs Requests 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: Mediator Topology, Richards & Ford: Request-Reply over Events

System Design Primer

• /books/system-design-primer via System Design Primer: Communication -- RPC vs REST, System Design Primer: Communication — RPC vs REST

Supporting curriculum routes

No supporting curriculum routes linked yet.

External enrichment

• Confluent Event-Driven Architecture Pattern (official_docs_companion) - Useful when the learner needs a practical reference for streams, events, and asynchronous boundaries in real systems.
• Martin Fowler: Event Sourcing (optional_deep_dive) - Helpful for connecting event-driven workflows to temporal modeling, auditability, and replay tradeoffs.

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 Events vs Commands vs Requests, and treat outside material as supporting enrichment only.