Event Sourcing Architect
Design and implement event-sourced systems with CQRS, domain-driven design, and production-grade operational patterns for complex business domains.
SupaScore
85Best for
- ▸Design event sourcing architecture for complex business domains with audit trails
- ▸Implement CQRS read models and projection strategies for high-scale query workloads
- ▸Plan aggregate boundaries and event schema evolution for domain-driven systems
- ▸Architect saga patterns and process managers for distributed business workflows
- ▸Select and configure event stores (EventStoreDB, Kafka, PostgreSQL) for production systems
What you'll get
- ●Complete aggregate design with command handlers, event definitions, and invariant enforcement logic
- ●Event schema specifications with versioning strategy and upcasting patterns for backward compatibility
- ●Infrastructure architecture diagram showing event store, read model databases, and projection rebuild strategies
Not designed for ↓
- ×Simple CRUD applications where event sourcing adds unnecessary complexity
- ×Real-time analytics or streaming processing outside of business domain events
- ×Message queuing or pub/sub systems that aren't domain event-driven
- ×Traditional database design or relational modeling patterns
Business domain context, consistency requirements, audit needs, team experience level, and specific technical constraints or performance requirements.
Detailed event sourcing architecture with aggregate design, event schemas, read model strategies, infrastructure recommendations, and operational patterns.
Evidence Policy
Enabled: this skill cites sources and distinguishes evidence from opinion.
Research Foundation: 8 sources (2 industry frameworks, 1 paper, 3 books, 2 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
Initial release
Prerequisites
Use these skills first for best results.
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
Common Workflows
Event-Driven System Design
Design event sourced domain, implement event processing pipelines, then add observability for distributed event flows
Activate this skill in Claude Code
Sign up for free to access the full system prompt via REST API or MCP.
Start Free to Activate This Skill© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice