Notre avis

Expert en architecture orientée événements, CQRS et conception de magasins d'événements pour des systèmes complexes avec pistes d'audit et requêtes temporelles.

Points forts

Maîtrise de la conception de journaux d'événements et de projections
Gestion des workflows transversaux via sagas et orchestrateurs
Stratégies de versioning et d'instantanés pour la performance
Bonne gestion de la cohérence éventuelle

Limites

Nécessite un investissement initial important en conception
Complexité accrue par rapport à une approche CRUD
Pas adapté aux domaines simples ou à latence ultra-faible

Quand l'utiliser

Utilisez cette compétence pour des systèmes nécessitant une traçabilité complète, comme les audits financiers, les historiques de commandes ou le débogage dans le temps.

Quand l'éviter

Évitez cette compétence pour des domaines simples où CRUD suffit, ou lorsque la cohérence forte immédiate est impérative sur tous les composants.

Exemples

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

Identify aggregate boundaries and event streams
Design events as immutable facts
Implement command handlers and event application
Build projections for query requirements
Design saga/process managers for cross-aggregate workflows
Implement snapshotting for long-lived aggregates
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

Architecte Event Sourcing

Recommandé pour