Event store design for event-sourced systems
Design event stores — architecture, technology choice, schemas, scaling and best practices
- What
- Design event stores — architecture, technology choice, schemas, scaling and best practices
- Cost
- Free
- Needs
- an event-sourced or event-driven project to apply it to; nothing else — the skill is guidance plus templates, no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @wshobson's design guide for event stores in event-sourced applications: the five core requirements (append-only, ordered per-stream and globally, versioned for optimistic concurrency, subscriptions for real-time notifications, idempotent writes), a technology comparison (EventStoreDB for pure event sourcing, PostgreSQL for existing stacks, Kafka for high-throughput streaming, DynamoDB for serverless, Marten for .NET) with each one's best-fit and limitations, and best practices — stream IDs that include the aggregate type, correlation/causation IDs, versioning events from day one, plus the don'ts: never update or delete events, keep payloads small, don't skip optimistic concurrency, don't ignore backpressure. Detailed templates live in the skill's `references/details.md`. By @wshobson, listed here with credit to its creator. Honest caveats: the comparison is a starting point, not a benchmark — re-verify technology limits against current docs for your stack; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Event store design is a guide for event stores in event-sourced applications, built on five requirements: append-only, ordered per-stream and globally, versioned for optimistic concurrency, subscriptions for real-time notifications, and idempotent writes. It compares technologies, EventStoreDB for event sourcing, PostgreSQL for stacks, Kafka for streaming, DynamoDB for serverless, and Marten for .NET, with each one's fit and limitations, plus practices.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 46891e7Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an event-sourced or event-driven project to apply it to; nothing else — the skill is guidance plus templates, no accounts or keys required Install "Event store design for event-sourced systems" for me. Give my agent @wshobson's event-store design guide: core requirements (append-only, ordered, versioned, subscriptions, idempotent), technology comparison (EventStoreDB, PostgreSQL, Kafka, DynamoDB, Marten), schemas, scaling considerations and best practices — with the full template library in references/details.md. Repository: https://raw.githubusercontent.com/wshobson/agents/46891e7e60da0e52baf1050b7b6391b64e84c6d9/plugins/backend-development/skills/event-store-design/SKILL.md Pinned version: install the code at commit 46891e7e60da0e52baf1050b7b6391b64e84c6d9 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "event-store-design". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing — it is a design guide; pick the technology that fits your stack). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 46891e7 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: files.pythonhosted.org, pypi.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.