skills.rest
OpenDCAI
OpenDCAIOFFICIAL
Explore all skills by this author →
GitHub

event-store-design

Design event stores with append-only storage and per-stream versioning.

114|12|Updated Jan 22, 2026
Search Tags:#architecture#scalability#concurrency#patterns#event-sourcing#event-store
One-click install
npx skills add https://github.com/OpenDCAI/leonai --skill event-store-design-opendcai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: event-store-design
Source: https://github.com/OpenDCAI/leonai/tree/main/.claude/skills/event-store-design
Command: npx skills add https://github.com/OpenDCAI/leonai --skill event-store-design-opendcai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Event-store design provides robust persistence for event-sourced systems, enabling reliable storage and playback of domain events.

Core Features & Use Cases

  • Per-stream versioning and append-only storage for correctness and auditability
  • Schema design templates for events, snapshots, and projections
  • Scalable patterns for subscriptions and real-time event delivery across services

Quick Start

Design and implement robust event stores for event-sourced systems to enable scalable persistence and reliable playback of domain events.

Frequently Asked Questions about event-store-design

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

FAQPage Schema
How do I design an event store for an event-sourced application?▼

Designing an event store requires enforcing append-only semantics and per-stream versioning. This skill provides schema templates for events and snapshots, enabling reliable domain event storage and playback across scalable architectures.

What is the best way to ensure per-stream ordering in an event store?▼

Per-stream ordering in an event store is maintained through strict per-stream versioning and append-only storage. This enforces event correctness and auditability, preventing concurrent updates from breaking the sequence of domain events.

How do I scale real-time event delivery and subscriptions across services?▼

Scalable event delivery and subscriptions across services require robust persistence patterns. This skill implements subscription patterns that enable real-time event playback and reliable distribution across different architectural setups.

Can I use event store schema design for multi-tenant architectures?▼

Yes, event store schema design supports multi-tenant setups. It includes technology selection and schema templates for events and snapshots, ensuring per-stream versioning and append-only storage scale correctly across multi-tenant architectures.

When do I need event snapshots in an event-sourced system?▼

Event snapshots are needed in an event-sourced system to optimize playback performance. This skill provides schema design templates for snapshots, reducing the overhead of replaying entire event streams during domain state reconstruction.

Related Skills

Explore More Software Engineering Skills→
MovchanetsMovchanets

ddd-tactical-patterns

Model DDD tactical patterns for aggregate design, value objects, repositories, and domain events.

Community
Intermediate
Sumeet138Sumeet138
1

projection-patterns

Transform event streams into queryable read models with projection patterns.

Community
Advanced
RomualdPRomualdP

CQRS Command Query Generator

Generate CQRS commands, queries, handlers, and read models with class-validator DTOs.

Community
Advanced
ccfccf

event-store-design

Design event stores with schemas, versioning, and append-only streams.

Community
Intermediate