Event Store Design

---
version: 4.1.0-fractal
name: event-store-design
description: Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
---

# Event Store Design

Comprehensive guide to designing event stores for event-sourced applications.

## Do not use this skill when

- The task is unrelated to event store design
- You need a different domain or tool outside this scope

## Instructions

- Clarify goals, constraints, and required inputs.
- Apply relevant best practices and validate outcomes.
- Provide actionable steps and verification.
- If detailed examples are required, open `resources/implementation-playbook.md`.

## Use this skill when

- Designing event sourcing infrastructure
- Choosing between event store technologies
- Implementing custom event stores
- Optimizing event storage and retrieval
- Setting up event store schemas
- Planning for event store scaling

## Core Concepts

## 🧠 Knowledge Modules (Fractal Skills)

### 1. [1. Event Store Architecture](./sub-skills/1-event-store-architecture.md)
### 2. [2. Event Store Requirements](./sub-skills/2-event-store-requirements.md)
### 3. [Template 1: PostgreSQL Event Store Schema](./sub-skills/template-1-postgresql-event-store-schema.md)
### 4. [Template 2: Python Event Store Implementation](./sub-skills/template-2-python-event-store-implementation.md)
### 5. [Template 3: EventStoreDB Usage](./sub-skills/template-3-eventstoredb-usage.md)
### 6. [Template 4: DynamoDB Event Store](./sub-skills/template-4-dynamodb-event-store.md)
### 7. [Do's](./sub-skills/dos.md)
### 8. [Don'ts](./sub-skills/donts.md)