Guide to designing event stores for event-sourced applications — covering event schemas, projections, snapshotting, and CQRS integration.
- Event Store Architecture — streams, global position, requirements
- Technology Comparison — EventStoreDB, PostgreSQL, Kafka, DynamoDB
- Event Schema Design — envelope structure, schema evolution rules
- PostgreSQL Event Store Schema — events, snapshots, subscription checkpoints
- Event Store Implementation — append with optimistic concurrency, read stream, read all (Python)
- Projections — lifecycle, idempotent handlers, design rules, projection example
- Snapshotting — snapshot flow, aggregate rehydration optimization
- CQRS Integration — write/read separation, command handler pattern
- EventStoreDB Integration example (Python)
- DynamoDB Event Store Implementation with single-table design
- Designing event sourcing infrastructure
- Choosing between event store technologies
- Implementing custom event stores
- Building projections from event streams
- Adding snapshotting for aggregate performance
- Integrating CQRS with event sourcing
npx add https://github.com/wpank/ai/tree/main/skills/backend/event-storenpx clawhub@latest install event-storeFrom your project root:
mkdir -p .cursor/skills
cp -r ~/.ai-skills/skills/backend/event-store .cursor/skills/event-storemkdir -p ~/.cursor/skills
cp -r ~/.ai-skills/skills/backend/event-store ~/.cursor/skills/event-storeFrom your project root:
mkdir -p .claude/skills
cp -r ~/.ai-skills/skills/backend/event-store .claude/skills/event-storemkdir -p ~/.claude/skills
cp -r ~/.ai-skills/skills/backend/event-store ~/.claude/skills/event-storearchitecture-patterns— Clean Architecture and DDD foundations for event sourcingmicroservices-patterns— Saga pattern and distributed transactions with events
Part of the Backend skill category.