event-driven-architecture

Installation
SKILL.md

Event-Driven Architecture

When to Use

  • Design event-driven integration between bounded contexts or microservices
  • Choose pub/sub vs point-to-point, topics vs queues, and broker capabilities
  • Model domain events, integration events, and command vs event semantics
  • Apply event sourcing or CQRS at architecture level (not framework tutorials only)
  • Define schemas, compatibility rules, and event schema versioning strategy
  • Specify ordering, partition keys, and delivery guarantees (at-least-once, etc.)
  • Design idempotent consumers, deduplication, and exactly-once tradeoffs
  • Implement transactional outbox or inbox for reliable publish/consume
  • Decide choreography vs orchestration and saga compensation at pattern level
  • Operate dead-letter queues, replay, and stream reprocessing safely
  • Distinguish stream processing (Kafka Streams, Flink) from discrete business events

When NOT to Use

Installs
19
GitHub Stars
2
First Seen
May 20, 2026
event-driven-architecture — daemon-blockint-tech/agentic-enteprises-skill