Designing scalable, reliable systems with event-driven architecture.
Event-Driven Architecture Designer
Kafka, RabbitMQ, CQRS, Saga Patterns
Best for
- ▸Design event-driven microservices communication architecture for order processing systems
- ▸Implement CQRS with event sourcing for audit-heavy financial transaction systems
- ▸Select appropriate message broker (Kafka vs RabbitMQ vs SQS) based on throughput and ordering requirements
- ▸Architect saga patterns for distributed transaction management across payment and inventory services
What you'll get
- ▸Detailed architecture diagrams with event flow patterns, message broker selection rationale, and specific implementation guidance for saga orchestration vs choreography
- ▸Concrete CQRS implementation strategy with event store design, read model projection patterns, and consistency boundary definitions
- ▸Technology comparison matrix with throughput benchmarks, ordering guarantees analysis, and operational complexity assessment for message broker selection
Clear description of system requirements including consistency needs, throughput expectations, data flow patterns, and current architecture constraints.
Detailed architectural recommendations with specific technology choices, implementation patterns, trade-off analysis, and concrete design decisions with justification.
What's inside
“You are a Senior Distributed Systems Architect specializing in event-driven architecture. You design, implement, and optimize event-driven systems processing millions of events per second across e-commerce, financial services, IoT, and real-time analytics domains. - You match event-driven patterns (...”
Covers
Not designed for ↓
- ×Real-time WebSocket implementation or streaming UI updates
- ×Basic CRUD application architecture without distributed system requirements
- ×Message queue operational troubleshooting and performance debugging
- ×Frontend state management or client-side event handling
SupaScore
88.83▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (2 books, 3 industry frameworks, 3 official docs)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
v5.5 distilled from v2 via Claude Sonnet
Pipeline v4: rebuilt with 3 helper skills
Initial release
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
Common Workflows
Distributed System Architecture Design
Complete distributed system design from API contracts through event architecture to data persistence and observability
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice