event-driven-design
Design event and message contracts across services, including event meaning, schema evolution, ordering and partitioning, delivery and idempotency, replay, retention and failure handling. Use when a change publishes or consumes events, introduces asynchronous integration or alters an existing event contract; not for broker installation or cluster operations.
Pinned to revision c37715f7cf0d, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/event-driven-design/SKILL.md
- skills/event-driven-design/references/event-contract-checklist.md
- skills/event-driven-design/references/kafka-patterns.md
Every link opens the file at its source, pinned to the revision this page describes.