proskillv1.0.0
event-driven-architecture
Design event-driven systems that stay consistent — queues vs streams, pub/sub topology, idempotent consumers, the transactional outbox, sagas for multi-service workflows, dead-letter queues, ordering guarantees, and event schema evolution without breaking consumers.
$npx vanara install event-driven-architecture
Included with Vanara Pro ($10/mo) — unlocks all 206 items. See pricing →
Overview
Events decouple services in space and time — and replace one shared-database consistency model with a dozen smaller contracts you must now design explicitly: delivery (at-least-once, always), ordering (per-key at best), atomicity (the outbox), and failure routing (DLQs). This skill is the working reference for those contracts. Deep detail in references/; the outbox and saga in runnable form in exa
What it covers
- Queues vs streams (pick per workload, not per fashion)
- The two invariants every consumer must hold
- The outbox pattern (atomicity across DB + broker)
- Sagas: multi-service workflows without distributed transactions
- Ordering: cheaper to not need it
- Dead-Letter Queues and Replay
- Sagas in Practice
- Event Schema Evolution