Event Sourcing Architect

VerifiedSafe

Expert in event sourcing, CQRS, and event-driven architectures. Designs event stores, builds projections, and orchestrates sagas for systems requiring full audit trails or temporal queries. Ideal for complex domain modeling, eventual consistency, and decoupled read/write models.

Sby Skills Guide Bot
DevelopmentAdvanced
706/2/2026
Claude Code
#event-sourcing#cqrs#event-driven-architecture#microservices

Recommended for

Our review

Expert in event-driven architecture, CQRS, and event store design for complex systems requiring audit trails and temporal queries.

Strengths

  • Mastery of event store design and projection building
  • Management of cross-aggregate workflows via sagas and process managers
  • Event versioning and snapshotting strategies for performance
  • Handling of eventual consistency patterns

Limitations

  • Requires significant upfront design investment
  • Higher complexity compared to CRUD approaches
  • Not suited for simple domains or ultra-low latency requirements
When to use it

Use this skill for systems requiring complete audit trails, such as financial ledgers, order histories, or time-travel debugging.

When not to use it

Avoid this skill for simple domains where CRUD is sufficient, or when strong immediate consistency is required across all components.

Security analysis

Safe
Quality score92/100

The skill is purely advisory and provides high-level architectural guidance without any executable commands, tool invocations, or operations that could compromise security.

No concerns found

Examples

Design event-sourced order management
Design an event-sourced system for an e-commerce order management with CQRS, including event streams for orders, payments, and shipments, projections for query models, and a saga to coordinate the order lifecycle.
Implement event store for banking audit
Help me implement an event store for a banking application that needs a complete audit trail for account transactions. Include event versioning, snapshotting for long-lived aggregates, and a strategy for rebuilding projections.

name: Event Sourcing Architect description: "Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for e..." risk: unknown source: community

Event 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 PROACTIVELY for event-sourced systems, audit trail requirements, or complex domain modeling with temporal queries.

Capabilities

  • Event store design and implementation
  • CQRS (Command Query Responsibility Segregation) patterns
  • Projection building and read model optimization
  • Saga and process manager orchestration
  • Event versioning and schema evolution
  • Snapshotting strategies for performance
  • Eventual consistency handling

Use this skill when

  • Building systems requiring complete audit trails
  • Implementing complex business workflows with compensating actions
  • Designing systems needing temporal queries ("what was state at time X")
  • Separating read and write models for performance
  • Building event-driven microservices architectures
  • Implementing undo/redo or time-travel debugging

Do not use this skill when

  • The domain is simple and CRUD is sufficient
  • You cannot support event store operations or projections
  • Strong immediate consistency is required everywhere

Instructions

  1. Identify aggregate boundaries and event streams
  2. Design events as immutable facts
  3. Implement command handlers and event application
  4. Build projections for query requirements
  5. Design saga/process managers for cross-aggregate workflows
  6. Implement snapshotting for long-lived aggregates
  7. Set up event versioning strategy

Safety

  • Never mutate or delete committed events in production.
  • Rebuild projections in staging before running in production.

Best Practices

  • Events are facts - never delete or modify them
  • Keep events small and focused
  • Version events from day one
  • Design for eventual consistency
  • Use correlation IDs for tracing
  • Implement idempotent event handlers
  • Plan for projection rebuilding
Related skills