event-driven
/event-driven
Event Sourcing, CQRS, Saga patterns, event bus (Kafka, RabbitMQ, AWS EventBridge). Use when implementing event-driven architecture, distributed transactions, or event sourcing.
- Author
- TheBeardedBearSAS ↗
- Repository
- claude-craft ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Event Sourcing, CQRS, Saga patterns, event bus (Kafka, RabbitMQ, AWS EventBridge). Use when implementing event-driven architecture, distributed transactions, or event sourcing.
Original author description
Event Sourcing, CQRS, Saga patterns, event bus (Kafka, RabbitMQ, AWS EventBridge). Use when implementing event-driven architecture, distributed transactions, or event sourcing.
How it works
- Patterns
- Event Sourcing
- Saga — Choreography vs Orchestration
- Kafka Event Bus
- Domain Events (Symfony)
SKILL.md preview
---
name: event-driven
description: Event Sourcing, CQRS, Saga patterns, event bus (Kafka, RabbitMQ, AWS EventBridge). Use when implementing event-driven architecture, distributed transactions, or event sourcing.
context: fork
files: ["**/events/**", "**/sagas/**", "**/event-store/**"]
---
# Event-Driven — Event Sourcing, Saga, CQRS
Architecture événementielle pour découplage et scalabilité.
## Patterns
**Event Sourcing** — Stocker events, pas état (audit, replay)
**CQRS** — Séparer Read/Write models (projections)
**Saga** — Transaction distribuée (microservices)
**Event Bus** — Pub/Sub découplé (Kafka, RabbitMQ)
## Event Sourcing
```python
events = [OrderCreated(...), OrderPaid(...), OrderShipped(...)]
def rebuild(events):
state = {}
for e in events: state = apply(state, e)
return state
```
## Saga — Choreography vs Orchestration
**Choreography** — Events chain services (découplé, debug dur)
**Orchestration** — Central coordinator (visible, couplé)
```
Choreo: OrderCreated → Payment → Shipping
Orchestrator: ProcessPayment() → ShipOrder()
```
## Kafka Event Bus
```javascript
// Producer
producer.send({ topic: 'orders', messages: [{ ... }] });
// Consumer
consumer.run({
eachMessage: async ({ message }) => {
handleEvent(JSON.parse(message.value));
}
});
```
## Domain Events (Symfony)
```php
class OrderCreatedEvent {
public function __construct(public Order $order) {}
}
class SendEmail {
public function __invoke(OrderCreatedEvent $e) {
$this->mailer->send($e->order->email, 'Confirmation');
}
}
```
---
Voir `@.claude/rules/21-cqrs.md`, `@.claude/skills/async/SKILL.md`
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · TheBeardedBearSAS/claude-craft | 95 | MIT |
| claude-dev-suite/claude-dev-suite | 100 | MIT |
| G1Joshi/Agent-Skills | 100 | MIT |
| MARUCIE/openclaw-foundry | 100 | MIT |
| Tyler-R-Kendrick/agent-skills | 100 | MIT |
| Tyler-R-Kendrick/agent-skills | 100 | MIT |
| kid-sid/codex-spellbook | 100 | MIT |
Database snapshot: 13.11.2026 · package version a1383d007eeb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines. - 90agent-event-driven-architect
Specialist subagent: Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, and message-driven architecture specialist. Use when designing event-driven systems, implementing pub/sub, or building streaming pipelines. Trigger phrases: Kafka, RabbitMQ, event sourcing, CQRS, message queue,… - 90backend-event-driven
Use this skill when the user says 'event-driven', 'message queue', 'Kafka', 'RabbitMQ', 'pub/sub', 'domain event', 'event sourcing', 'CQRS', 'async messaging', 'event bus', or when designing asynchronous communication between services. This skill enforces: domain vs integration… - 90event-sourcing-architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use for event-sourced systems, audit trails, or temporal queries. - 95microservice-design-patterns
Use this skill when the user says 'saga pattern', 'distributed transaction', 'compensating transaction', 'choreography vs orchestration', 'CQRS with event sourcing', 'cross-service consistency', 'two-phase commit microservices'. Explains and designs the data-consistency patterns… - 90event-driven-architecture
Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.