Event Sourcing Architect

• 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
• Use durable execution for process managers and sagas — frameworks like DBOS persist workflow state automatically, making cross-aggregate orchestration resilient to crashes

Related Skills

Works well with: saga-orchestration, architecture-patterns, dbos-*

Limitations

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.