architecture-paradigm-cqrs-es

Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.

Aller à l'installation

Dépôt: athola/claude-night-market
Dernière activité de la source: 22 juin 2026 à 15:41
Langue détectée de SKILL.md: anglais
Étoiles: 327
Forks: 35

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/athola/claude-night-market --skill architecture-paradigm-cqrs-es

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

Retour à la recherche Retour à l’installation

night-market-research-methodology

Turn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.

2026-07-28

validate-pr

Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.

2026-07-28

palace-index-curator

Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.

2026-07-28

Tout voir dans ce dépôt

The CQRS and Event Sourcing Paradigm

When To Use

Designing event-sourced systems with complex domain logic

Systems requiring full audit trails of state changes

When NOT To Use

Simple CRUD applications without complex domain logic

Small projects where event sourcing adds unnecessary complexity

When to Employ This Paradigm

When read and write workloads have vastly different performance characteristics or scaling requirements.

When all business events must be captured in a durable, immutable history or audit trail.

When a business needs to rebuild projections of data or support temporal queries (e.g., "What did the state of this entity look like yesterday?").

Adoption Steps

Identify Aggregates: Following Domain-Driven Design principles, specify the bounded contexts and the business invariants that each command must enforce on an aggregate.

Model Commands and Events: Define the schemas and validation rules for all commands and the events they produce. Document a clear strategy for versioning and schema evolution.

Implement the Write Side (Command Side): Command handlers are responsible for loading an aggregate's event stream, executing business logic, and atomically appending new events to the stream.

Build Projections to the Read Side: Create separate read models (projections) that are fed by subscriptions to the event stream. Implement back-pressure and retry policies for these subscriptions.

validate Full Observability: Implement detailed logging that includes event IDs, sequence numbers, and metrics for tracking the lag time of each projection.

Key Deliverables

An Architecture Decision Record (ADR) detailing the aggregates, the chosen event store technology, the projection strategy, and the expected data consistency model (e.g., eventual consistency SLAs).

A suite of tests for command handlers that use in-memory event streams, complemented by integration tests for the projections.

Operational tooling for replaying events, taking state snapshots for performance, and managing schema migrations.

Risks & Mitigations

High Operational Overhead:

Mitigation: Bugs related to event ordering and replays can be difficult to diagnose. Invest heavily in automation, Dead-Letter Queues (DLQs) for failed events, and regular "chaos engineering" drills to test resilience.

Challenges of Eventual Consistency:

Mitigation: Users may be confused by delays between performing an action and seeing the result. Clearly document the SLAs for read model updates and manage user-facing expectations accordingly, for example, by providing immediate feedback on the command side.

Schema Drift:

Mitigation: An unplanned change to an event schema can break consumers. Enforce the use of a formal schema registry and implement version gates in the CI/CD pipeline to prevent the emission of unvalidated event versions.

Concrete Components

These vocabulary items name the concrete tools and abstractions that show up when the paradigm is implemented. They are not required dependencies and they are not part of the skill's tools: frontmatter (which is reserved for Claude Code tool restrictions). Use this list to disambiguate during architecture discussions.

event-store: append-only log of domain events; the system of record from which projections are built

message-broker: carries commands and integration events between bounded contexts

projection-builder: rebuilds read-side views by replaying the event store

Exit Criteria

An ADR is produced naming the aggregates, the chosen event store technology, the projection strategy, and the eventual-consistency SLA for each read model.

Command handler tests use in-memory event streams and pass before any persistence adapter is wired.

A schema registry or versioning policy for event schemas is documented, and a CI gate prevents emission of event versions not registered in that policy.

Operational tooling for event replay and state snapshots is identified (not just mentioned) before the write-side is declared production-ready.

name	architecture-paradigm-cqrs-es
description	Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
alwaysApply	false
category	architectural-pattern
tags	["architecture","CQRS","Event-Sourcing","distributed-systems","audit-trail","scalability"]
dependencies	[]
tools	[]
usage_patterns	["paradigm-implementation","distributed-system-design","auditability","scalability-optimization"]

name	architecture-paradigm-cqrs-es
description	Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
alwaysApply	false
category	architectural-pattern
tags	["architecture","CQRS","Event-Sourcing","distributed-systems","audit-trail","scalability"]
dependencies	[]
tools	[]
usage_patterns	["paradigm-implementation","distributed-system-design","auditability","scalability-optimization"]

architecture-paradigm-cqrs-es

Informations de source

Options d'installation

Vérifiez les fichiers source

Plus depuis ce dépôt

Plus depuis ce dépôt

The CQRS and Event Sourcing Paradigm

When To Use

When NOT To Use

When to Employ This Paradigm

Adoption Steps

Key Deliverables

Risks & Mitigations

Concrete Components

Exit Criteria