nw-sd-patterns-advanced

Coordinate event sourcing, CQRS, and saga patterns for resilient event-driven architectures.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/StudentCristian/nWave-github --skill nw-sd-patterns-advanced
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-sd-patterns-advanced
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-sd-patterns-advanced
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-sd-patterns-advanced

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and apply advanced distributed patterns to design resilient event-driven architectures. This section can explain how event sourcing, CQRS, sagas, and stream processing address auditability, scalability, and fault tolerance in complex systems.

Core Features & Use Cases

  • Event Sourcing for complete audit trails and deterministic replay of state
  • CQRS for separating read and write models to optimize performance
  • Saga coordination for distributed transactions with compensating actions
  • Stream processing with reliable guarantees and fault tolerance
  • Exactly-once delivery and idempotent processing to ensure data integrity
  • Guidance on recovery, snapshots, and reconciliation in complex architectures

Quick Start

Describe how to implement event sourcing with CQRS and sagas for an e-commerce workflow.

Frequently Asked Questions about nw-sd-patterns-advanced

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

FAQPage Schema
How do I coordinate distributed transactions using the saga pattern with compensating actions?

Saga coordination manages distributed transactions by orchestrating a sequence of local transactions, executing compensating actions to rollback previous steps if a failure occurs, ensuring data consistency across services without two-phase commits.

What is event sourcing and when do I need it for audit trails?

Event sourcing persists state changes as a sequence of immutable events, providing a complete audit trail and enabling deterministic state replay. You need it when systems require strict auditability, historical debugging, or temporal queries.

How do I implement CQRS to separate read and write models for high scalability?

CQRS separates write models handling commands from read models optimized for queries, scaling them independently to maximize performance and distribute workloads in complex event-driven architectures.

Can I achieve exactly-once delivery and idempotent processing in stream processing workflows?

Exactly-once delivery and idempotent processing are achievable in stream processing workflows by tracking event identifiers and applying transactional guarantees, ensuring data integrity and preventing duplicate processing during fault recovery.

What are the trade-offs of using event-driven distributed patterns for payments and trading platforms?

Trade-offs of event-driven distributed patterns include increased architectural complexity and eventual consistency, offset by high scalability, reliable transaction processing, and fault tolerance required for payments and trading platforms.