AsyncAPI and Event-Driven Contracts
This generated surface maps a learner-facing curriculum unit to its canonical source routes.
Curriculum surface
- Open learner-facing unit
- Curriculum path:
content/curriculum/architecture/semester-07-architecture-ddd/module-04-api-design-contract-evolution/concepts/cluster-04-rpc-graphql-event-driven/12-asyncapi-event-driven-contracts-supporting.md - App:
architecture - Semester:
semester-07-architecture-ddd - Module:
module-04-api-design-contract-evolution - Unit kind:
concept - Curation level:
module_curated
Learning objectives
- Explain AsyncAPI and Event-Driven Contracts as a contract and evolution problem, not just an endpoint-shape or schema-format decision.
- Use AsyncAPI and Event-Driven Contracts to reason about compatibility, versioning, lifecycle cost, and the blast radius of public interfaces.
- Use
api-design-patterns,fundamentals-of-software-architecture,learning-domain-driven-designto connect the learner page to contract design, compatibility strategy, and API governance decisions.
Prerequisites
- Comfort with modular boundaries and bounded contexts, because APIs are where those boundaries become explicit contracts.
Source books
api-design-patternsfundamentals-of-software-architecturelearning-domain-driven-design
Source routes
Api Design Patterns
- /books/api-design-patterns via
Geewax: Request deduplication (idempotency - relevant to event dedupe),Geewax: Response caching and request ID collisions
Fundamentals Of Software Architecture
- /books/fundamentals-of-software-architecture via
Fundamentals of Software Architecture: Event-driven architecture style
Learning Domain Driven Design
- /books/learning-domain-driven-design via
Learning DDD: Event-driven architecture,Learning DDD: Types of events and distributed ball of mud
Supporting curriculum routes
No supporting curriculum routes linked yet.
External enrichment
- Microsoft REST API Guidelines (
official_docs_companion) - Anchors API contract thinking in a real, widely used design standard rather than intuition. - Zalando RESTful API Guidelines (
optional_deep_dive) - Useful for comparing how different organizations encode compatibility and lifecycle 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 AsyncAPI and Event-Driven Contracts, and treat outside material as supporting enrichment only.