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:
Install
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://github.com/wshobson/agents/blob/main/plugins/backend-development/skills/event-store-design/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build 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 build before installing it.