event-sourcing-architect

Guide event-sourced system architecture, projections, and saga orchestration.

Updated Feb 24, 2026

Search Tags:#architecture #event-driven #saga #cqrs #projection #event-sourcing #read-model

Ready to run

npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill event-sourcing-architect-chicanoandres702

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: event-sourcing-architect
Source: https://github.com/chicanoandres702/SentientAIBrowser/tree/main/.agents/workflows/event-sourcing-architect
Command: npx skills add https://github.com/chicanoandres702/SentientAIBrowser --skill event-sourcing-architect-chicanoandres702

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Event sourcing and CQRS patterns enable scalable, auditable, and flexible systems. This skill guides teams in designing robust event stores, projections, saga orchestration, and eventual consistency for complex domains and temporal queries.

Core Features & Use Cases

Event store design and implementation for reliable state history
CQRS patterns to separate reads and writes with optimized projections
Projection building and read-model optimization for fast queries
Saga and process-manager orchestration across multiple aggregates
Event versioning, schema evolution, and snapshotting strategies
Temporal queries and audit-trail requirements support

Quick Start

Model a small domain and outline an event store, read-model projections, and a saga to manage cross-aggregate workflows.

Frequently Asked Questions about event-sourcing-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is event sourcing and when do I need it for my architecture?▼

CQRS separates read and write operations, allowing you to build optimized read-model projections from your event store. This pattern enables fast queries and scalable reads by materializing events into specialized projections tailored for specific query needs.

How do I orchestrate sagas across multiple aggregates in an event-driven system?▼

Saga orchestration coordinates long-running transactions across multiple aggregates using process-manager patterns. You implement sagas by designing compensating actions for each step, ensuring eventual consistency when cross-aggregate workflows fail partially.

What's the best way to handle event versioning and schema evolution in an event store?▼

Event versioning strategies include upcasting, schema versioning within event metadata, and snapshotting to optimize aggregate hydration. These approaches handle schema evolution by transforming older events to newer formats during replay without breaking existing projections.

Does event sourcing work for microservices requiring eventual consistency?▼

Event sourcing fits event-driven microservices by providing eventual consistency through asynchronous projection updates. Microservices subscribe to event streams, building independent read-models while maintaining reliable cross-service workflows via saga orchestration.