Event Store Design
Unverified●30/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add event-store-designWho is stuck, and on what
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
The whole source
Frontmatter — 2 properties
| 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. |
| 1 | --- |
| 2 | name: event-store-design |
| 3 | 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. |
| 4 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 5 | |
| 6 | # Event Store Design |
| 7 | |
| 8 | Comprehensive guide to designing event stores for event-sourced applications. |
| 9 | |
| 10 | ## When to Use This Skill |
| 11 | |
| 12 | - Designing event sourcing infrastructure |
| 13 | - Choosing between event store technologies |
| 14 | - Implementing custom event stores |
| 15 | - Optimizing event storage and retrieval |
| 16 | - Setting up event store schemas |
| 17 | - Planning for event store scaling |
| 18 | |
| 19 | ## Core Concepts |
| 20 | |
| 21 | ### 1. Event Store Architecture |
| 22 | |
| 23 | ``` |
| 24 | ┌─────────────────────────────────────────────────────┐ |
| 25 | │ Event Store │ |
| 26 | ├─────────────────────────────────────────────────────┤ |
| 27 | │ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ |
| 28 | │ │ Stream 1 │ │ Stream 2 │ │ Stream 3 │ │ |
| 29 | │ │ (Aggregate) │ │ (Aggregate) │ │ (Aggregate) │ │ |
| 30 | │ ├─────────────┤ ├─────────────┤ ├─────────────┤ │ |
| 31 | │ │ Event 1 │ │ Event 1 │ │ Event 1 │ │ |
| 32 | │ │ Event 2 │ │ Event 2 │ │ Event 2 │ │ |
| 33 | │ │ Event 3 │ │ ... │ │ Event 3 │ │ |
| 34 | │ │ ... │ │ │ │ Event 4 │ │ |
| 35 | │ └─────────────┘ └─────────────┘ └─────────────┘ │ |
| 36 | ├─────────────────────────────────────────────────────┤ |
| 37 | │ Global Position: 1 → 2 → 3 → 4 → 5 → 6 → ... │ |
| 38 | └─────────────────────────────────────────────────────┘ |
| 39 | ``` |
| 40 | |
| 41 | ### 2. Event Store Requirements |
| 42 | |
| 43 | | Requirement | Description | |
| 44 | | ----------------- | ---------------------------------- | |
| 45 | | **Append-only** | Events are immutable, only appends | |
| 46 | | **Ordered** | Per-stream and global ordering | |
| 47 | | **Versioned** | Optimistic concurrency control | |
| 48 | | **Subscriptions** | Real-time event notifications | |
| 49 | | **Idempotent** | Handle duplicate writes safely | |
| 50 | |
| 51 | ## Technology Comparison |
| 52 | |
| 53 | | Technology | Best For | Limitations | |
| 54 | | ---------------- | ------------------------- | -------------------------------- | |
| 55 | | **EventStoreDB** | Pure event sourcing | Single-purpose | |
| 56 | | **PostgreSQL** | Existing Postgres stack | Manual implementation | |
| 57 | | **Kafka** | High-throughput streaming | Not ideal for per-stream queries | |
| 58 | | **DynamoDB** | Serverless, AWS-native | Query limitations | |
| 59 | | **Marten** | .NET ecosystems | .NET specific | |
| 60 | |
| 61 | ## Templates and detailed worked examples |
| 62 | |
| 63 | Full template library and detailed worked examples live in `references/details.md`. Read that file when you need the concrete templates. |
| 64 | |
| 65 | ## Best Practices |
| 66 | |
| 67 | ### Do's |
| 68 | |
| 69 | - **Use stream IDs that include aggregate type** - `Order-{uuid}` |
| 70 | - **Include correlation/causation IDs** - For tracing |
| 71 | - **Version events from day one** - Plan for schema evolution |
| 72 | - **Implement idempotency** - Use event IDs for deduplication |
| 73 | - **Index appropriately** - For your query patterns |
| 74 | |
| 75 | ### Don'ts |
| 76 | |
| 77 | - **Don't update or delete events** - They're immutable facts |
| 78 | - **Don't store large payloads** - Keep events small |
| 79 | - **Don't skip optimistic concurrency** - Prevents data corruption |
| 80 | - **Don't ignore backpressure** - Handle slow consumers |
| 81 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current session◐◐◐◐◐●36/40Python Code Style & DocumentationPython code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.◐····●35/40Competitor Price Analysis 💲Competitor pricing strategy analysis and market positioning. Price mapping, pricing gaps identification, elasticity signals evaluation, and strategic pricing optimization. Use when the user asks about competitor pricing, price analysis, pricing strategy, or co◐····●34/40Competitor Price Tracker 📊Set up competitor price tracking and monitoring workflows. Track price changes, detect promotions, analyze pricing patterns, and get alerts for competitive price movements.◐····●34/40