Event Driven Architecture

Choosing facts, asynchronous commands or request/response across services; then designing choreography/orchestration, payload authority, evolution horizon and consumer runtime. Use when a broker masks synchronous outcome dependence, workflows are unreconstructable, consumers read back every event, or publish and database commit form a dual write. Delivery, idempotency, ordering, outbox mechanics and schema evolution remain in their owning skills.

robsonkades Updated 3 repo stars

File contents

robsonkades/agent-skills commit b8f0e6c144

Frequently asked questions

npx get-skill add robsonkades/event-driven-architecture