# Event Driven Architecture

> Design messaging across service and process boundaries - when to go async, how events propagate b…

Design messaging across service and process boundaries - when to go async, how events propagate between contexts, reliable publication (outbox/inbox, dual-write), delivery semantics (at-least-once, idempotent consumers, DLQ, ordering), and event/schema versioning. Use when work crosses a service boundary with queues, brokers, or streams (Kafka/RabbitMQ/SQS), integration events, or an evolving event schema.

- Page: https://ss33.ai/skills/connorads/event-driven-architecture-36010163287
- Publisher: connorads
- Category: [Software Development](https://ss33.ai/skills/category/software-development-t44z8z) › [APIs & backend](https://ss33.ai/skills/category/software-development-t44z8z/apis-and-backend-t0x840)
- Source: https://github.com/connorads/dotfiles/blob/a99bce6ffc926729f81191a8f8ff6c9ab5697881/skills/event-driven-architecture/SKILL.md

## Skill

This skill's licence does not allow redistribution, so the store does not serve its text. Get it from the author: https://github.com/connorads/dotfiles/blob/a99bce6ffc926729f81191a8f8ff6c9ab5697881/skills/event-driven-architecture/SKILL.md