aurora-cqrs

CQRS architecture in NestJS separates read and write operations into distinct components: Commands for mutations, Queries for data retrieval, Events for asynchronous actions, and Sagas for complex process orchestration. This Skill details how these handlers interact across application, domain, and infrastructure layers.

API handlers in Aurora CQRS act as entry points that route incoming requests to specific Commands or Queries. They interface with the application layer to dispatch operations to appropriate handlers, ensuring clean separation between request orchestration and business logic execution.

To onboard a new developer to an Aurora NestJS codebase, use this Skill to explain the CQRS pattern and project structure. It clarifies component relationships, data flow across layers, and identifies editable zones in generated files to prevent accidental overwrites.

Editable zones in Aurora generated files are clearly marked sections where developers can safely add custom logic without risking overwrites during regeneration. This Skill identifies these boundaries to help you understand where to implement commands, queries, events, and sagas.

Sagas in the CQRS pattern manage long-running transactions and coordinate multiple events. Within Aurora/NestJS, sagas listen to domain events and trigger subsequent commands, making them essential for complex business processes that require multi-step orchestration.

Yes, you can modify generated CQRS files in an Aurora project safely by editing within designated editable zones. This Skill clarifies these boundaries, ensuring your custom command, query, and event implementations remain intact during code generation cycles.